Architecture: find the owner

Read the product overview for the autonomous work loop, then trace dispatch, execution and acceptance through their owners below. Architecture explains implementation responsibilities; the specifications own requirements and the runbook owns operating procedures.

What you need to understand or extend	Start here	Main source boundary
Autonomous delegation, implementation and acceptance	Activation and node execution, shared acceptance	SupervisorRuntimeApi, CardProcessActor, NodeExecution, AgentExecutor; bundled root assessment in classic-shared.ts.
Where a change belongs	Ownership and dependencies	Owner-published package roots/ports; scripts/check-import-boundaries.cjs.
Configuration, workflow or action	Startup compilation, then node execution	schemas/saivage-config.ts, runtime/card-process/card-process-config.ts, operation-contract.ts, NodeExecution.
Dispatch, Pause/Stop or cancellation	Control and recovery	SupervisorRuntimeApi, exact owner/lease and process-scope joins.
Tool permission or external Analyst client	Caller-specific tools	Bound tool catalog and application Analyst operation surface; not agent names.
Prompt selection, composition or customization	Prompt handling	Compiler/registry, preparation suppliers, context projector and declaration retention.
Provider request/admission/compaction	Provider context	Runtime source selection → agents request plan/attempts → direct conversation publication.
Outbound MCP or image dataflow	MCP owners, image pipeline	Manager/runtime/transports, producer-neutral result and exact source-session selection.
Cards, records or durable state	Canonical graph and persistence	Direct card/record/conversation owners, current selector versus reached history.
An API or browser feature	Projection and browser state	Shared operation contract → source-adjacent projector → exact resource/request owner.
Exact route/tool/config field inventory	Source-derived reference	Checked tables at the canonical architecture owner.
Release/state compatibility evidence	Current durable baseline, then named historical entries	Owning schemas and semantic consumers; source evidence is not deployment permission.

For a practical change, trace the contract, effect owner, public projection and consumer together, then choose focused checks from validation. Do not introduce another store, scheduler, generic dispatcher or compatibility path to avoid the existing owner. Documentation examples and static composition are not proof of live delivery, model compliance, installed adoption or historical fidelity.