Social Annotations in the Atmosphere
update agents
+66
-1
+66
-1
AGENTS.md
+66
-1
AGENTS.md
···
1
-
# AGENTS.md - synthes.is
1
+
# AGENTS.md - seams.so
2
2
3
3
## Project Overview
4
4
**Hypothesis clone built on AT Protocol** - Web annotation system similar to Hypothesis but using ATProto/Bluesky infrastructure.
5
+
6
+
## Issue Tracking with bd (beads)
7
+
8
+
**IMPORTANT**: This project uses **bd (beads)** for ALL issue tracking. Do NOT use markdown TODOs, task lists, or other tracking methods.
9
+
10
+
### Why bd?
11
+
12
+
- Dependency-aware: Track blockers and relationships between issues
13
+
- Git-friendly: Auto-syncs to JSONL for version control
14
+
- Agent-optimized: JSON output, ready work detection, discovered-from links
15
+
- Prevents duplicate tracking systems and confusion
16
+
17
+
### Quick Start
18
+
19
+
**Check for ready work:**
20
+
```bash
21
+
bd ready --json
22
+
```
23
+
24
+
**Create new issues:**
25
+
```bash
26
+
bd create "Issue title" -t bug|feature|task -p 0-4 --json
27
+
bd create "Issue title" -p 1 --deps discovered-from:bd-123 --json
28
+
```
29
+
30
+
**Claim and update:**
31
+
```bash
32
+
bd update bd-42 --status in_progress --json
33
+
bd update bd-42 --priority 1 --json
34
+
```
35
+
36
+
**Complete work:**
37
+
```bash
38
+
bd close bd-42 --reason "Completed" --json
39
+
```
40
+
41
+
### Issue Types
42
+
43
+
- `bug` - Something broken
44
+
- `feature` - New functionality
45
+
- `task` - Work item (tests, docs, refactoring)
46
+
- `epic` - Large feature with subtasks
47
+
- `chore` - Maintenance (dependencies, tooling)
48
+
49
+
### Priorities
50
+
51
+
- `0` - Critical (security, data loss, broken builds)
52
+
- `1` - High (major features, important bugs)
53
+
- `2` - Medium (default, nice-to-have)
54
+
- `3` - Low (polish, optimization)
55
+
- `4` - Backlog (future ideas)
56
+
57
+
### Important Rules
58
+
59
+
- ✅ Use bd for ALL task tracking
60
+
- ✅ Always use `--json` flag for programmatic use
61
+
- ✅ Link discovered work with `discovered-from` dependencies
62
+
- ✅ Check `bd ready` before asking "what should I work on?"
63
+
- ✅ Store AI planning docs in `history/` directory
64
+
- ❌ Do NOT create markdown TODO lists
65
+
- ❌ Do NOT use external issue trackers
66
+
- ❌ Do NOT duplicate tracking systems
67
+
- ❌ Do NOT clutter repo root with planning documents
68
+
69
+
For more details, see README.md and QUICKSTART.md.
5
70
6
71
## Future Architecture Plans
7
72
- **via.seams.so proxy**: Need to build a proxy service (like Hypothesis's via.hypothes.is) for annotation injection