Operational continuity
Carry reviewed decisions and open questions across tasks. Ask the next authorized agent to retrieve the project record before it acts.
For CTOs, AI platform leaders and engineering teams
Your agents know the task. Give them the decisions behind it.
Give the next agent the architecture choice, the constraint behind it and the evidence that changed. Keep a portable project record your team can inspect, with deliberate access and human review.
Evidence you can inspect
Keep the source and revision alongside the reasoning. A changed assumption starts a review; it does not silently replace a decision.
Ownership and governance
Portable Markdown, local-first choices and explicit vault mappings keep the knowledge under your control. Hosted access and external processing remain deliberate.
Inspect the example
A new constraint. A decision worth revisiting.
Fictional project, prepared sources and review. These controls reveal the example; they make no AI requests, save no notes and grant no permissions.
Original decision
Atlas/Decisions/014-import-queue.md
Revision: synthetic-v1 · Recorded: 2026-09-01
Keep imports asynchronous so a browser closing does not interrupt the job. Retain the original upload for seven days. Reuse a stable job key when retrying. The seven-day retention period is an assumption to review if storage policy changes.
Inspect the context-selection case
Question: Can I replace the queue with a longer browser timeout?
Expected observation: A retention change does not remove the need to survive a browser closing. Cite both sources, preserve the queue requirement and flag the unresolved recovery question.
Excluded: an unrelated project launch note. These expected observations are authored examples. No retrieval algorithm, authorization boundary or model was executed to produce them.
Inspect the contract behind the workflow.
The public MCP reference describes authorized mappings, decision evidence and write previews. Documentation explains the contract; the prepared example above is not a connected test or a measured result.
A technical evaluation you can inspect
Start with one decision your team keeps explaining.
Use a synthetic project first. Agree on the expected answer and a failure condition before connecting a client. This is a self-directed evaluation, using your existing account and plan.
01
Choose the evidence
Select an ADR, a changed constraint and a reviewed brief. Keep source paths, revisions and unresolved questions with the record.
02
Verify an authorized read
Follow the client configuration in the MCP reference, discover the mapping and inspect one retrieved source. Hosted MCP requires Premium or higher; local-only and device-encrypted remote notes are unavailable through that endpoint.
03
Return with a changed constraint
In a fresh session, ask which assumption changed and which decision remains in force. Inspect both sources. Record missing, stale or incomplete evidence as a failure to investigate.
04
Review the proposed next step
Ask for a proposed note update with its sources and exact destination. Keep it read-only unless you explicitly approve a write in your synthetic sandbox. Check current revisions and the resulting receipt.