Skip to content

chore(workspace): add NTM and Beads coordination guidance #422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
christso merged 2 commits into from
Jun 8, 2026
Merged

chore(workspace): add NTM and Beads coordination guidance #422

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
99ce10d
chore(workspace): add NTM and Beads coordination guidance
christso Jun 8, 2026
4696a07
chore(workspace): clean NTM guidance wording
christso Jun 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 46 additions & 0 deletions .beads/.gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
# Database
*.db
*.db-journal
*.db-shm
*.db-wal

# Lock files
*.lock

# Temporary
last-touched
*.tmp

# Local history backups
.br_history/

# DB-family recovery artifacts (truncated WAL/SHM, quarantined sidecars)
# - same lifecycle as .br_history/, written by recovery paths and
# `br doctor --repair`. Filename suffix `.truncated-wal` slips past the
# generic `*.db-wal` glob above, so it needs an explicit entry (#271).
.br_recovery/

# Sync state (local-only, per-machine)
.sync.lock
sync_base.jsonl

# Merge artifacts (temporary files from 3-way merge)
beads.base.jsonl
beads.base.meta.json
beads.left.jsonl
beads.left.meta.json
beads.right.jsonl
beads.right.meta.json

# Daemon runtime files
daemon.lock
daemon.log
daemon.pid
bd.sock
sync-state.json

# Worktree redirect file
redirect

# bv (beads viewer) lock file
.bv.lock
1 change: 1 addition & 0 deletions .beads/config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
issue_prefix: allagents
2 changes: 2 additions & 0 deletions .beads/issues.jsonl
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
{"id":"allagents-ntm-beads-ao-cleanup-s4v","title":"Set up NTM and Beads guidance and remove AO artifacts","description":"Set up Beads for EntityProcess/allagents, add minimal repo guidance for future NTM sessions/workers and Beads coordination, and remove/supersede Composio AO / agent-orchestrator artifacts in favor of NTM. Track search evidence and validation before PR.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-06-08T20:45:18.446045720Z","created_by":"entity","updated_at":"2026-06-08T20:52:21.560446826Z","closed_at":"2026-06-08T20:51:19.931912943Z","close_reason":"Guidance, Beads setup, AO evidence, and focused validation complete for PR.","source_repo":"allagents","source_repo_path":"/home/entity/projects/EntityProcess/allagents","compaction_level":0,"original_size":0,"labels":["beads","cleanup","ntm"],"comments":[{"id":1,"issue_id":"allagents-ntm-beads-ao-cleanup-s4v","author":"entity","text":"AO/Composio search evidence: origin/main (14d555d18a3dbf89375518a88193c4db5c8087ed) has no filename or content matches for composio, agent-orchestrator, agent orchestrator, AO config, agentConfig, or permissionless except ordinary GitHub Actions permissions keys. The primary checkout branch chore/ao-agent-orchestrator-config adds only agent-orchestrator.yaml with agentConfig.permissions: permissionless. This PR branch is based on origin/main, so there is no AO file to delete here; the branch supersedes that AO config by documenting NTM/Beads as the repo coordination path and forbidding AO artifacts.","created_at":"2026-06-08T20:49:17Z"},{"id":2,"issue_id":"allagents-ntm-beads-ao-cleanup-s4v","author":"entity","text":"Implementation/validation: initialized Beads with issue_prefix=allagents, added a concise AGENTS.md NTM & Beads Coordination section naming /home/entity/ntm_Dev/allagents as the stable NTM project root, and verified no AO artifacts are present on origin/main. Checks run: git status -sb, br status, br show allagents-ntm-beads-ao-cleanup-s4v --wrap, bun run lint, bun run typecheck.","created_at":"2026-06-08T20:51:19Z"}]}
{"id":"allagents-remove-legacy-orchestration-wording-r2z","title":"Clean AGENTS.md coordination wording","description":"Update AGENTS.md to keep positive NTM sessions/workers guidance and Beads tracking via br.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-06-08T21:06:14.269026977Z","created_by":"entity","updated_at":"2026-06-08T21:08:00.898412860Z","closed_at":"2026-06-08T21:08:00.898261719Z","close_reason":"AGENTS.md coordination wording cleaned and verified.","source_repo":"allagents","source_repo_path":"/home/entity/projects/EntityProcess/allagents","compaction_level":0,"original_size":0,"labels":["beads","cleanup","ntm"]}
4 changes: 4 additions & 0 deletions .beads/metadata.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
{
"database": "beads.db",
"jsonl_export": "issues.jsonl"
}
5 changes: 5 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,11 @@ bun install
```
- If you discover you are not on a fresh worktree from the latest `origin/main`, stop and fix that first before changing code.

### NTM & Beads Coordination
- Use NTM sessions/workers for multi-agent orchestration. The stable NTM project root is `/home/entity/ntm_Dev/allagents`; use task labels/workers from that project for coordinated work.
- Track durable task state with Beads using `br`. Keep Bead statuses current, run `br sync --flush-only` before commits that change Beads state, and commit only intentional `.beads` JSONL/config files.
- Do not commit Beads runtime files such as local DB/WAL files, locks, sync state, or history backups.

### Planning
- Use plan mode for any non-trivial task (5+ steps or architectural decisions).
- If something goes sideways, STOP and re-plan immediately instead of pushing through a broken approach.
Expand Down