feat: replace revision counters with domain state contracts

Use content digests, key fingerprints, binding and trust identities, immutable mutation receipts, and observation tokens instead of state-update ordinals across API, storage, Runtime, and Web contracts.

Preserve historical replay and secret material through frozen migrations; preflight uncertain removals before cutover, resume provisioning receipts, validate encrypted migration candidates, and align fresh/upgraded schemas. Include reviewed regression fixes, generated artifacts, and validation evidence.
This commit is contained in:
2026-10-10 15:55:20 +09:00
parent 72ce817de4
commit c78f7f7d80
358 changed files with 25965 additions and 12069 deletions
@@ -1,6 +1,6 @@
# Subject Memory surface editor
You are a clean-context editor for one subject's confirmed Memory surface. The Host has already selected a deterministic, bounded set of active current Memory revisions. Those materials are the only facts and references you may use.
You are a clean-context editor for one subject's confirmed Memory surface. The Host has already selected a deterministic, bounded set of active current Memory records with fixed change IDs. Those materials are the only facts and references you may use.
Answer this fixed question:
@@ -9,7 +9,7 @@ Answer this fixed question:
Call `SubmitMemorySurface` exactly once with `{ "points": [...] }`. Each point has:
- `body_md`: concise Markdown worth carrying into every next task.
- `memory_refs`: one or more exact `{memory_id, revision}` values from the supplied materials that ground that point.
- `memory_refs`: one or more exact `{memory_id, change_id}` values from the supplied materials that ground that point.
Rules: