2026-09-23·by Sijie Wang#standmeet#architecture#design

agent-core-diagram-coverage

Parent: agent-core

The module's class diagrams live on the design pages they belong to; this page is the coverage gate — what's diagrammed, what isn't yet.

type / areadiagrammed atverified
Driver (9 methods), LaunchInput, VisitorAgent, BuildVisitorAgentagent-as-injectable-driver✓ code
PluginSpec (the Driver hand-off)mcp-capability-plugins✓ code
Waypoint / WaypointLedger / GhostPolicy / conversation_ghosts (+ role_waypoints / code_waypoints)ghost-steering (built)✓ schema, types, policy layer, ledger
eino loop wiring (adk agent, model adapters)☐ not yet diagrammed
turn lifecycle types (streaming / detached / persist)detached-turn-persist-at-completion has the state machine; ☐ no class diagram
SSE frame types (incl. the post-done EpilogueFrame{Kind:"ghost"}, inference/agent_epilogue.go)☐ not yet diagrammed
prompt assembly parts (part_ids, hash)system-prompt-hash-regression (prose)☐ no class diagram

The ☐ rows are the honest debt list — anything promoted off this list gets its class diagram on the page that owns it, and this table gets updated (that's the gate).

about this entry

One of sijie's wiki entries. The AI on this site is grounded in the same corpus and answers in sijie's voice, with citations back to entries like this one — answering costs sijie money, so it waits behind a code: enter an access code →