Agents work from hq's definitions and start from the knowledge base; every prepare and record gets the seams review #507

Merged
mesh-tools merged 6 commits from docs/agents-from-hq into main 2026-11-03 11:48:55 +00:00
Member

The operator, 2026-11-03: agents never start from a prompt written by hand, only a handover; knowledge is discovered in the session, eagerly; instructions and playbooks name no record; every interaction between modules is a mesh path; subagents work inside hq.

  • Four agent definitions in .claude/agents/: mesh-preparer, mesh-developer (smaller model unless the lead says why), mesh-code-reviewer, mesh-watcher; each starts from the knowledge base and treats an interaction that is not a mesh path as a finding.
  • The four reviewers by architectural domain start from the knowledge base too.
  • Playbook 07 step 0: agents from hq's definitions, the lead writes only the handover; a subagent runs in the session that started it, from hq, a coding one in a worktree under hq's .work/ also reading its repository's conventions (hq wins); every prepare starts from the knowledge base and gets the seams review before code. Playbook 02: a record's draft gets the seams review before it is proposed. AGENTS.md and the playbooks overview follow.
  • No record is named by number in the added text.

Kept for later (reviewer's notes): .work/ is not in .gitignore; the subagent sentence's own check.

Reviewed-by: mesh-code-reviewer@shanks at 4315bb6307

The operator, 2026-11-03: agents never start from a prompt written by hand, only a handover; knowledge is discovered in the session, eagerly; instructions and playbooks name no record; every interaction between modules is a mesh path; subagents work inside hq. - Four agent definitions in .claude/agents/: mesh-preparer, mesh-developer (smaller model unless the lead says why), mesh-code-reviewer, mesh-watcher; each starts from the knowledge base and treats an interaction that is not a mesh path as a finding. - The four reviewers by architectural domain start from the knowledge base too. - Playbook 07 step 0: agents from hq's definitions, the lead writes only the handover; a subagent runs in the session that started it, from hq, a coding one in a worktree under hq's .work/ also reading its repository's conventions (hq wins); every prepare starts from the knowledge base and gets the seams review before code. Playbook 02: a record's draft gets the seams review before it is proposed. AGENTS.md and the playbooks overview follow. - No record is named by number in the added text. Kept for later (reviewer's notes): .work/ is not in .gitignore; the subagent sentence's own check. Reviewed-by: mesh-code-reviewer@shanks at 4315bb6307c12d3aef41ce5507eb025bc6aa356a
mesh-tools added 5 commits 2026-11-03 11:16:28 +00:00
Author
Member

Delivery novox/hq@4315bb6307c1 — merged since 2026-11-03T11:48:58Z

Source — source.main moved to novox/hq@b5347d0294. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

  • 2026-11-03 11:47 (new) → proposed (announced): novox/hq#507's head announced
  • 2026-11-03 11:47 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
  • 2026-11-03 11:48 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/hq@4315bb6307c1` — **merged** since 2026-11-03T11:48:58Z **Source** — source.main moved to novox/hq@b5347d029453. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-03 11:47 (new) → proposed (announced): novox/hq#507's head announced - 2026-11-03 11:47 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-03 11:48 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-11-03 11:47:01 +00:00
A subagent works from hq; a coding one in a worktree under hq's .work, also reading its repository's conventions (the operator, 2026-11-03)
mesh/delivery merged: source.main moved to novox/hq@b5347d029453
mesh/check pass 4315bb6307c1 on f6bd4246b0d7 | carried from 979bf3f19cce | unit 39 run, 0 kept, 1 skipped | integration 39 run, 0 kept, 1 skipped | co…
4315bb6307
Author
Member

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head e8c154c3a0 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.

mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head e8c154c3a0ba is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-tools merged commit b5347d0294 into main 2026-11-03 11:48:55 +00:00
mesh-tools deleted branch docs/agents-from-hq 2026-11-03 11:48:56 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#507