Functional Specifications

These are normative references: what Saivage must do and how the operator UI must present it. They are not startup instructions or evidence that a particular installation conforms. Begin with the overview for the autonomous work and completion model, the runbook for an operator task, or the architecture for implementation ownership.

Choose the authority

Question	Owning reference
What is the product/trust boundary?	System: product and trust
Who delegates, corrects and assesses completion?	Planning and assessment, shipped completion graphs
Which caller may mutate which work?	Caller-aware operation admission
How do card identity, lifecycle and records work?	Cards, authored records, history and selections
What runs an agent or an action?	Workflow engine, actions and execution evidence, shipped policy
What does retained conversation/instruction evidence prove?	Conversations and instruction evidence
What do Run, Pause, Stop and restart mean?	Runtime controls, startup recovery
Which MCP direction am I using?	External client to Analyst, Saivage to configured servers
How do provider context, compaction and recovery differ?	Context preparation, construction and exact admission
What survives interruption, and what adoption is allowed?	Persistence, repair/reset/adoption; historical evidence in the format reference
What does the operator need to understand or do?	UI needs: requirement register, resolved owner decisions
Which exact routes, labels and evidence disclosures apply?	UI contracts: navigation, records, conversations, Analyst modes, Files

Reading the contracts

Stable F identifiers and priorities belong to the needs register; exact UI behavior belongs to its paired contracts register. A failed or unverified implementation does not retire a requirement. Exact marked source-derived value blocks remain in their system/UI owners and are checked mechanically; passing those checks is not a prose, usability, delivery or model-perception guarantee.

Policy remains in repository AGENTS.md. Procedure/source-format links do not authorize deployment, repair, reset, migration or project Run.