Start here. For current package status and verified local test results, see current-state.md.
Historical naming note: some architecture docs in
docs/architecture/still contain references to@relay-assistant/*andRelayAssistant. Those are historical records from before the rename to@agent-assistant/*/ Agent Assistant SDK. Active code and packages use@agent-assistant/*.
Development follows a spec → implement → review flow:
- a spec is written and marked implementation-ready
- an implementation workflow produces code and tests
- a review verdict is written and the package/package-area becomes reconciled in code
A package being “specified” does not mean it is unimplemented forever; several parts of this repo have now progressed beyond older historical planning docs. When docs conflict, use the precedence rule below.
When documents conflict:
source code > specs > package READMEs > index/status docs > plans > verdicts
That means:
docs/specs/contains canonical contracts where specs exist- package READMEs usually describe the current intended public surface better than older architecture plans
- plans and review verdicts in
docs/architecture/are often historical records, not current status pages
As of the latest verified local run:
- 566 tests passing
- 23 test files passing
- memory, turn-context, continuation, inbox, coordination, and integration coverage are all present in the current repo state
See current-state.md for the authoritative snapshot.
Harness is not the umbrella runtime concept.
Read the runtime stack like this:
@agent-assistant/core= runtime shell@agent-assistant/sessions= continuity@agent-assistant/surfaces= assistant-facing surface mediation@agent-assistant/harness= bounded turn executor@agent-assistant/turn-context= turn-scoped context assembly@agent-assistant/traits= stable identity floor@agent-assistant/policy= governance seam@agent-assistant/memory= memory supply@agent-assistant/continuation= unfinished-turn resume runtime@agent-assistant/inbox= trusted outsider ingestion boundary@agent-assistant/routing,connectivity,coordination= execution-envelope and backstage collaboration primitives- product intelligence remains product-owned
Primary architecture anchors:
- Runtime primitive map
- Runtime primitives vs. product intelligence
- Turn-context enrichment boundary
- Package boundary map
- Sage v2 substrate extraction map
- Top-level SDK adoption guide
- How to build an assistant
- How products should adopt agent-assistant-sdk
- Runtime primitive map
- Runtime primitives vs. product intelligence
- Package boundary map
- Sage v2 substrate extraction map
- Top-level SDK facade spec
- Assistant cloud interface
- Top-level SDK adoption guide
- How to build an assistant
- How products should adopt agent-assistant-sdk
- Connectivity adoption guide
A number of older documents still reflect intermediate states from before:
- the public rename settled
- turn-context was fully implemented
- memory/inbox/continuation landed in current form
- package-local counts reached the current local totals
Those docs are still useful as design history, but they should not override current code and current package READMEs.
Last reconciled: 2026-04-16