Start with the quickstart. It covers installation, a first single-repository setup, federation, and basic troubleshooting.
- User manual: day-to-day operation and troubleshooting
- Cookbook: deployment recipes
- Federation: multi-repository operation
repos.yamlreference: configuration fields and examples- Command Center: the browser interface
- Hot reload: config reload behavior
- Multiplayer: agent presence, claims, and coordination
- Pre-edit hooks: hook installation and behavior
- Tool guide: MCP tools and request examples
- Skill bundle: agent-loadable skills and role recipes
- Query tutorial: a short introduction to
query_graph - Query language reference: the full ops-array format
tool-schema.json: generated wire-format schema- Dynamic dispatch mitigation: the three-tier plan that closes the static-graph blind spot for message buses, DI containers, and schema-driven routers. Includes the
explain_dispatchtool, thedynamic-boundaries.mdtemplate, and the backfill CLI.
-
Architecture: system boundaries and design choices
-
Protocol coverage: per-
ContractKeykind sensors, joiner resolvers, binding grammar, and dashboard visibility — plus the bus/system detection backlog -
Technical reference: modules, data structures, and internals
-
CI: checks run in continuous integration
-
Branching: integration, release, and protection policy
-
Distribution: pre-release and published-package checks
-
Release verification: how to verify a release artifact
-
Supply-chain security: release and dependency controls
-
SafeSkill scoring: scope and interpretation of the score
-
Contributing as an agent: code-structure rules and automated guardrails
-
Agent UX design record: stable milestone vocabulary referenced by code and tool descriptions
-
Vulnerability triage: current OSV findings and remediation
-
OpenSSF Scorecard: current external score and process gaps
-
Graph data-source decision: why the Command Center graph uses
get_workspace_graph
METADATA.toml belongs to the release workflow rather than the reading path.
Completed plans, audits, review notes, and the academic SRS package live in Git history. Keeping them out of the current tree prevents old implementation notes from competing with maintained documentation.
MIT, Copyright (c) 2026 spuentesp