Context And Continuity
Amber owns contracts, validation, selection, and gates. The host agent owns generation and loading.
- Inspect context requests, page verification, feature/session state, and existing handoff artifacts.
- For durable knowledge, create a
context request; generate only from its declared sources. Copy source descriptors exactly, cite every claim, and mark unsupported claims unknown.
- After human review, ingest the payload through
context ingest --confirm. Without explicit confirmation the typed CLI seam returns approvalRequired and performs no write. Never write a page directly or re-hash sources to evade freshness checks.
- Run
context refresh and resolve stale-source requests. Use no-change only when the claims truly remain valid.
- Build a task Loadout with
context load --route <id> and verify it immediately before use. Required Artifacts are separate from page references and may not be omitted to fit budget.
- For operator-preference knowledge that belongs in MEMORY.md, use the governed memory verbs (
memory request / memory ingest / human memory approve / memory book; memory status to observe). Amber registers the surface hash; humans curate MEMORY.md.
- Before stopping, update progress, feature/session evidence, Resume Checkpoint, and
session-handoff.md; run handoff validation.
Evidence order: request id and source hashes, schema-valid payload, ingest result, refresh state, Loadout path/hash, Required Artifact verification, handoff validation.
On failure, stop before the next stage, retain the request and negative validation evidence, and report the exact recovery command. Do not weaken approval, isolation, or ledger requirements to make a stale payload ingestible.
On stale, missing, escaped, or tampered sources, fail closed and request a fresh contract. On interruption, resume from the latest validated request/Loadout and handoff record, never from chat memory alone.
1---2name: amber-context-continuity3description: Distill provenance-backed context, verify task Loadouts, and preserve resumable handoff state.4---56# Context And Continuity78Amber owns contracts, validation, selection, and gates. The host agent owns generation and loading.9101. Inspect context requests, page verification, feature/session state, and existing handoff artifacts.112. For durable knowledge, create a `context request`; generate only from its declared sources. Copy source descriptors exactly, cite every claim, and mark unsupported claims unknown.123. After human review, ingest the payload through `context ingest --confirm`. Without explicit confirmation the typed CLI seam returns `approvalRequired` and performs no write. Never write a page directly or re-hash sources to evade freshness checks.134. Run `context refresh` and resolve stale-source requests. Use no-change only when the claims truly remain valid.145. Build a task Loadout with `context load --route <id>` and verify it immediately before use. Required Artifacts are separate from page references and may not be omitted to fit budget.156. For operator-preference knowledge that belongs in MEMORY.md, use the governed memory verbs (`memory request` / `memory ingest` / human `memory approve` / `memory book`; `memory status` to observe). Amber registers the surface hash; humans curate MEMORY.md.167. Before stopping, update progress, feature/session evidence, Resume Checkpoint, and `session-handoff.md`; run `handoff` validation.1718Evidence order: request id and source hashes, schema-valid payload, ingest result, refresh state, Loadout path/hash, Required Artifact verification, handoff validation.1920On failure, stop before the next stage, retain the request and negative validation evidence, and report the exact recovery command. Do not weaken approval, isolation, or ledger requirements to make a stale payload ingestible.2122On stale, missing, escaped, or tampered sources, fail closed and request a fresh contract. On interruption, resume from the latest validated request/Loadout and handoff record, never from chat memory alone.
Bandersnatch0x