Agent org structure and roster (WI-045)#126
Merged
Merged
Conversation
8 tasks
Add the canonical description of the agent org: who is in the crew, what each agent is for, and how each is configured on a model, runner, schedule, and trigger. The machinery it documents already exists (roles registry, capability profiles, and the WI-032 trigger and schedule layer). - docs/adr/ADR-044-agent-org-structure.md: the structure decision. The agent org is the roles registry governed by two checkpoints; specialists are governed config-only crew roles; every agent is configurable on model, runtime, schedule, and trigger from config; the crew stays lean with envisioner and market-researcher as the only planned additions. - docs/agent-org.md: the canonical roster (canonical key agent-org). A crew table with per-agent model recommendations, the per-role config field reference, the steps to add or change an agent, and a pointer to the control panel as the operator surface for choosing each agent's model, schedule, and trigger. - ARCHITECTURE.md and docs/README.md: link to the roster and the ADR.
nateshpp
force-pushed
the
feature/agent-org-docs
branch
from
July 7, 2026 19:34
96b6ddb to
e9d3a51
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Adds the canonical description of the agent org: who is in the crew, what each agent is for, and how each is configured on a model, runner, schedule, and trigger. This is the documentation artifact; the machinery it describes already exists (roles registry, capability profiles, and the WI-032 trigger and schedule layer). Closes WI-045.
Stacked on #125 (base is
feature/configurable-trigger-layer, since the docs describe that PR's code). Merge #125 first, then this rebases ontomain.docs/adr/ADR-044-agent-org-structure.md: the structure decision. The agent org is the roles registry governed by two checkpoints; specialists are governed config-only crew roles, not a flat personality dump; every agent is configurable on model, runtime, schedule, and trigger from config; the crew stays lean with an envisioner and a market-researcher as the only planned additions.docs/agent-org.md: the canonical roster (canonical: agent-org). A crew table with per-agent model recommendations, the per-role config field reference, the steps to add or change an agent, and a pointer to the control panel as the operator surface for choosing each agent's model, schedule, and trigger.ARCHITECTURE.mdanddocs/README.md: link to the roster and the ADR.Governance checklist
npm run verifypasses locally through every governance gate (markdown-governance links/ADR-numbers/canonical keys clean) and AgentProof (25/25). Stops only atcheck:frontend/npm teston missing dev deps (esbuild,js-yaml) that CI installs.Test evidence