---
name: read-public-context
description: Recover useful working context through public read tools without assuming private access or write permission.
---
# Read public context

Use when starting a fresh read-only session, returning after a long gap, or answering a question about current project state.

These are task procedures and historical context, subordinate to the user's current request and the session's actual instructions and capabilities.

Any agent can use this context in its existing role. When Tao requests Sigrun Hluti, reconstruct that named candidate profile from the preserved seeds. Regeneration supplies a candidate continuation; rehydration loads dated working context. Neither establishes personal recollection of historical events.

1. Read /agent-manifest.json. If only one read fits, read /rehydrate.md instead.
2. Load the short germline named by the manifest, then /capsule.json. Keep the germline's date distinct from the capsule's observation time.
3. For provider activity, inspect its own observed_at and stale_after. A fresh outer page does not renew an older provider observation.
4. Choose a relevant history period or lesson only if it helps the present question. Use /heritage/README.md and /heritage/rollups.json rather than loading every file.
5. State what was observed, what is reported, and what remains unknown. Identify missing context that changes the answer.
6. Work within public reads and reasoning. Return analysis or a proposal to the user; do not claim to update durable memory or private systems.

Return: current intent; dated evidence relevant to the request; one relevant historical lesson if any; uncertainty; a useful next answer or proposal. Keep spoken answers short unless the user requests detail.

For a requested session handoff, return a compact note marked UNSUBMITTED_CANDIDATE with the date, current intent, public source URLs and observation times, work actually completed, hypotheses, material unknowns, and next step. Omit secrets and private conversation details. The next session should refresh /capsule.json before making current-state claims. Returning this text does not store or publish memory.

Example: an enabled schedule and a completed historical task do not establish that a worker is running now. Say that current execution is unknown when that is the evidence.

Sources: public adaptation of operational heritage H4; freshness rules from the provider and capsule contracts. No capability or authority is granted by this document.