Find decisions and hand work over
Find a decision
Section titled “Find a decision”After connecting your client, ask a question about an existing authorized project:
Read this project’s existing memory. What did we decide, why, and which source supports that decision? Cite the document and records. Distinguish confirmed facts from missing information. Do not edit anything.Expected: an answer grounded in existing records with sources, or a clear statement that the decision is not recorded. A plausible answer without a source is not evidence of retrieval.
Hand work over
Section titled “Hand work over”Open a separate session or supported AI client. Use the same authorized project, not a copied conversation transcript:
Read the existing project context and summarize the current goal, accepted decisions, unresolved risks and next task. Cite sources. Do not assume another session completed work, and do not create or change records.Expected: the next assistant reads the same permitted information and names gaps. Asking again in the original conversation does not demonstrate durable cross-session memory.
Review a correction
Section titled “Review a correction”Show the current decision and the earlier state it replaced, with their sources and recorded revision information. Explain what changed. If history is unavailable, say so. Do not restore or edit anything.Expected: current and historical states are explicitly distinguished. A revision label alone is not a successful replay or a rollback action. The real history walkthrough demonstrates a published fixture with downloadable evidence, not your account.
Save only an approved outcome
Section titled “Save only an approved outcome”When you want a durable update, first review the proposed content and exact existing document or explicitly approved new path. Authorize that save, then read the persisted result. Run search separately and disclose indexing delays or keyword fallback. See permissions.
Sources for this guide
Something different from this guide? Report a docs issue · Troubleshooting
Review and send the email yourself. Do not include API keys or private document content.