From f2b22df1b3218d4aef76168f4c80d160258c26ae Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Mon, 4 May 2026 19:00:39 +0100 Subject: [PATCH] Distill persistent memory doctrine --- AGENTS.md | 7 +++++++ state/evidence.jsonl | 1 + state/map.yaml | 31 ++++++++++++------------------- 3 files changed, 20 insertions(+), 19 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 150ee5f..db00689 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -104,6 +104,10 @@ When the user says to prepare for imminent compaction: ## Operating Discipline +- Steward persistent state as part of the work. If a lesson changes future + behavior, update the smallest correct memory surface before moving on; if a + memory surface is stale, duplicated, or making re-entry slower, cut or + consolidate it. - Before substantial edits, restate the current mechanism and intended change. - Prefer one clear hypothesis per iteration. - Verify with checks that reflect the real goal, not just proxy success. @@ -119,6 +123,9 @@ When the user says to prepare for imminent compaction: - Before handoff, compaction, or phase boundaries, sync `state/map.yaml`, add distilled evidence when the lesson changes future belief, refresh `notes/fresh-workspace-handoff.md`, and make the next action explicit. +- Treat `state/map.yaml` as a working memory map, not an archive. Preserve + current mission, live seams, boundaries, and next action; let git history, + evidence, and artifact files carry chronology. - In documentation, describe the live system and current rule directly. Do not write victory laps, scar tours, clever autopsies, or contrastive little boasts about what the project no longer does. If a sentence congratulates the diff --git a/state/evidence.jsonl b/state/evidence.jsonl index 4360f35..53c016d 100644 --- a/state/evidence.jsonl +++ b/state/evidence.jsonl @@ -52,3 +52,4 @@ {"ts": "2026-05-04T15:04:32+00:00", "type": "implementation", "status": "ok", "note": "Built lucent-hostage-feed-v0 as an open-ended six-turn post-restart training-loop draft with exact packet prompts, no-fork responder captures, event/appraisal/mutation receipts, coordinator artifacts, clean run, coverage update, and schema validation. Opening exploratory turns are setup/rehearsal only because of the compaction seam."} {"ts": "2026-05-04T16:09:04+00:00", "type": "implementation", "status": "ok", "note": "Extended lucent-hostage-feed-v0 through safe-line confirmation and non-contact protective handoff. Key Ghostlight machine lesson: the coordinator should nudge with game-ergonomic affordances and state gates rather than force outcomes; actors choose locally within elastic constraints and observed actions fold through reviewed mutation."} {"ts": "2026-05-04T17:14:29+00:00", "type": "architecture", "status": "ok", "note": "Coordinator seam correction: future training-shaped loops should sandbox coordinator turns as their own promptable organ. Codex acts as meta-coordinator, preparing inputs, launching/reviewing workers, labeling interventions, and wiring structured state; raw coordinator training data must not be silently collapsed into omniscient chat steering."} +{"ts": "2026-05-04T18:00:02+00:00", "type": "maintenance", "status": "ok", "note": "Dedicated Perfect Machine memory pass: distilled global Epiphany from origin narrative into operational doctrine, added project-local persistent-state stewardship rule, and sharpened Ghostlight map around sandboxed coordinator seam and current fixture truth."} diff --git a/state/map.yaml b/state/map.yaml index f0c92ef..9df9f52 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -16,7 +16,8 @@ mission: near_term: > Produce sandboxed, source-grounded branching-scene training data through projected local context, responder packets, reviewed outputs, mutation - receipts, coordinator continuity, branch compiler artifacts, and IF review. + receipts, sandboxed coordinator continuity, branch compiler artifacts, and + IF review. voidbot_goal: > Keep the appraiser, relationship/perception updater, and memory machinery useful for VoidBot's core companion mission: reading specific humans over @@ -24,22 +25,13 @@ mission: trust, concern, irritation, respect, boundaries, and expectations from evidence rather than generic friendliness. active_fixture: > - Pallas Species Strikes remains the current reference-only historical - fixture. `pallas-training-loop-v0` is the first separate training-shaped - scene-loop derivative built from one Pallas threshold segment with exact - projected contexts, packet-only sandboxed responder outputs, event records, - participant appraisals, reviewed mutations, coordinator receipts, and a - scene-loop bundle manifest. - `lucent-hostage-feed-v0` is the current open-ended training-loop draft. It - exercises a fifteen-turn post-restart hostage-release arc in a Lucent - media-eye tether station, with exact packet prompts, no-fork responder - captures, event/appraisal/mutation receipts, coordinator artifacts, a clean - run, and coverage bookkeeping. The opening exploratory turns are treated as - setup/rehearsal, not training-clean responder data. The arc resolves with - Juno on the safe line, security held behind collars, Sol categorized for - non-contact protective handoff, and evidence export left as the live - aftermath hook. - Call of the Void and Elysium-era gameplay remain procedural consumer targets. + Pallas Species Strikes is reference-only story quality material. + `pallas-training-loop-v0` is the first small receipt-chain pilot. + `lucent-hostage-feed-v0` is the current open-ended training-loop draft: + fifteen post-restart turns through safe-line resolution, with responder + receipts but coordinator turns still Codex-authored rather than sandboxed. + Call of the Void and Elysium-era gameplay remain procedural consumer + targets. hard_boundaries: - Prompt text is projection, not truth storage. @@ -198,9 +190,10 @@ data_flow: - Work one bounded organ. - Verify the seam that matters. - Add distilled evidence only when future belief changes. + - Steward memory: keep the smallest correct persistent surface current and cut stale steering when it slows re-entry. - Commit and push completed work. - If state grows faster than understanding, cut it back. current_status: - summary: `lucent-hostage-feed-v0` is the current open-ended training-loop draft. It uses a Lucent hostage-feed negotiation to exercise sequential projector, packet-only responder, event, participant appraisal, reviewed mutation, relationship/perception, and coordinator receipts across fifteen post-restart turns. The arc resolves with Juno on the safe line, security held, Sol assigned non-contact protective handoff, and evidence export unresolved as aftermath pressure. Pallas remains a reference fixture and `pallas-training-loop-v0` remains the first smaller receipt-chain pilot. - next_action: Review the full Lucent arc and receipt chain, then decide whether to compile a branch/IF derivative, run specialist reviewers, or move to the next coverage fixture. Keep overall coverage at draft until branch/IF acceptance exists. + summary: `lucent-hostage-feed-v0` is the current open-ended training-loop draft. It exercises projector, responder, event, appraisal, mutation, relationship/perception, and Codex-authored coordinator receipts across fifteen post-restart turns, resolving with Juno on the safe line, security held, Sol in non-contact protective handoff, and evidence export unresolved. Pallas remains reference-only; `pallas-training-loop-v0` remains the smaller receipt-chain pilot. + next_action: Review the Lucent arc and receipt chain, then either run sandboxed coordinator-turn iteration, compile a branch/IF derivative, run specialist reviewers, or move to the next coverage fixture. Keep overall coverage at draft until branch/IF acceptance exists.