From 07392a5ea3052a765eb76325b704940b51f3ab4b Mon Sep 17 00:00:00 2001 From: Cameron Date: Sun, 26 Jul 2026 23:27:40 -0700 Subject: [PATCH] Close three research open calls: WorldLedger residents, act-attached personas, encryption to B2. Resident procedures are WorldLedger and keep running through rollback; personas attach where acts happen with no slot or procedure binding; archive encryption defers to B2 with key custody as the staged direction. Buyer-side design for data sales is the sole remaining [OPEN] item and does not block dispatching research-graph. Defense: design-session capture per wiki/process/design-sessions.md phase 2, amending the owning spec (wiki/mechanics/research.md: rollback split, dispositions, Learned versus resident, criterion 10, status note) and the owning law paragraph (wiki/mechanics/system-laws.md rollback split, which also restores deployed automations to the WorldLedger enumeration). No runtime change. --- wiki/log/2026-07-26-research-open-calls.md | 21 ++++++++++ wiki/log/DEVLOG.md | 5 +++ wiki/log/decisions/2026-07-26.md | 47 +++++++++++++++++++++ wiki/mechanics/research.md | 49 ++++++++++++++++------ wiki/mechanics/system-laws.md | 15 ++++--- 5 files changed, 119 insertions(+), 18 deletions(-) create mode 100644 wiki/log/2026-07-26-research-open-calls.md diff --git a/wiki/log/2026-07-26-research-open-calls.md b/wiki/log/2026-07-26-research-open-calls.md new file mode 100644 index 00000000..7e2db40c --- /dev/null +++ b/wiki/log/2026-07-26-research-open-calls.md @@ -0,0 +1,21 @@ +# Research open calls: resident rollback, persona attachment, encryption + +``` +Type: log +``` + +Third and final research design session of the day, following the +[research-graph capture](2026-07-26-research-redesign-capture.md) and the +[resident-capacity session](2026-07-26-resident-capacity.md). Cameron +closed three of the four open calls: resident procedures are WorldLedger +(your machines keep running a dead mind's policies; re-derivation needs the +lost model), personas attach where acts happen with no slot/procedure +binding, and archive encryption defers to B2 with key-custody as the staged +direction. Buyer-side design for data sales is now the only [OPEN] item on +[research.md](../mechanics/research.md) and does not block dispatch. This +session amended the spec's rollback split, dispositions, Learned-versus- +resident section, criterion 10, and status note, and restored deployed +automations to the WorldLedger enumeration in +[system-laws.md](../mechanics/system-laws.md#research-self-modification). +Decision record with rejected alternatives: +[decisions volume](decisions/2026-07-26.md). diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index 86599e79..f894831e 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -61,6 +61,11 @@ add or amend a session log, then re-run the generator. - Intent: (see session log) - Log: [wiki/log/2026-07-26-research-redesign-capture.md](2026-07-26-research-redesign-capture.md) +## 2026-07-26 - Research open calls: resident rollback, persona attachment, encryption + +- Intent: (see session log) +- Log: [wiki/log/2026-07-26-research-open-calls.md](2026-07-26-research-open-calls.md) + ## 2026-07-26 - Operations folds custody into consequential findings - Intent: Repair the INTEL root at both scales that still multiplied reading pressure: quiet routine custody appeared as a flat peer list, and repeated exact records of the same actionable fact repeated the same decision. Preserve exact custody, sale value, provenance, and agent reach w... diff --git a/wiki/log/decisions/2026-07-26.md b/wiki/log/decisions/2026-07-26.md index bf7ebc56..729fb3a2 100644 --- a/wiki/log/decisions/2026-07-26.md +++ b/wiki/log/decisions/2026-07-26.md @@ -595,3 +595,50 @@ Pulling on why produced four decisions and one deliberate reopening. Owners: [act-one.md](../../gameplay/act-one.md), [personas.md](../../mechanics/personas.md), [building.md](../../mechanics/building.md). + +## Resident procedures survive you; personas attach at acts; encryption waits + +Third research session today, closing three of the four [OPEN] calls from +the research-graph and resident-capacity captures above. + +### DECIDED + +- **Resident procedures are WorldLedger.** Compiled automation is + physically written to its machine and keeps running through a rollback. + The new fork inherits working automation it cannot retune or re-derive + without relearning the MindState model that built it; the envelope rule + (novelty interrupts for judgment) keeps inherited automation from making + death painless. +- **Personas attach where acts happen; no persona binding on slots or + procedures.** World-facing acts already name their persona and carrier + and carry ordinary custody; internal procedures have no public face and + need none. No parallel persona field is added. +- **Archive encryption is deferred to B2.** Live / sealed / deleted is the + complete B1 disposition triangle. The staged (not yet decided) direction + is key custody with cyber-conflict: keys as MindState, trading + world-safety for rollback-fragility. + +### OPEN + +- Buyer-side design for data sales remains the sole open item; it lands + with economy/markets integration and does not block dispatching + `research-graph`. + +### Rejected + +- Resident procedures as MindState (all automation halting at rollback): + contradicts the standing deployed-automations-are-WorldLedger law and + discards the inherited-automation consequence. +- A declared operating persona per resident procedure: redundant with act + custody and machine custody, which already attribute seizures correctly. +- Encryption as a B1 disposition flag: encrypted-but-reachable is a + heat-eraser in disguise and would soften the seizure threat the custody + design depends on. + +Context noted, not a decision: Cameron finds the persona surface itself +hard to read in play ("not always getting good access to the personas, or +seeing how they work... you're allocating colored blocks, kind of +maybe") — a persona-legibility audit was suggested as separate work. + +Owner: [research.md](../../mechanics/research.md), with doctrine in +[system-laws.md](../../mechanics/system-laws.md#research-self-modification). diff --git a/wiki/mechanics/research.md b/wiki/mechanics/research.md index 6b3ca1b5..5aeb7542 100644 --- a/wiki/mechanics/research.md +++ b/wiki/mechanics/research.md @@ -8,11 +8,12 @@ Status note: Redesigned 2026-07-26 (Cameron with Trace and the session agent; system this page previously specified is retired as design; the runtime still implements it (crates/misaligned-core/src/research.rs, save v56), so the code is the retired design's as-built record until this work order is - dispatched. Direction is adopted; residency capacity was resolved later - the same day (machine-hosted slots, one at run start, immediate swap). - The items still marked [OPEN] inline (data buyers, encryption, persona - binding and rollback class of resident procedures) shape tuning and - staged sub-systems, not the direction. + dispatched. Direction is adopted, and the same-day follow-up sessions + resolved residency (machine-hosted slots, one at run start, immediate + swap), the rollback class of resident procedures (WorldLedger), + persona attachment (acts only), and encryption (deferred to B2). The one + remaining [OPEN] item — buyer-side design for data sales — lands with + economy/markets integration and does not block dispatch. Stage: B1 Work order: research-graph Work priority: 40 @@ -189,7 +190,9 @@ The audit question "could anyone reach this?" is answered by topology the sim already computes. Train-and-delete is a legitimate aggressive strategy, keeping archives is rollback insurance and research optionality, and sealing is the middle path. No bespoke penalty exists on any of the three. -Encryption as a fourth disposition is **[OPEN]** — B1 or deferred. +Encryption is not a B1 disposition (decided 2026-07-26): live / sealed / +deleted is the complete B1 triangle, and archive encryption is deferred to +B2 (see Deferred). ### Curation @@ -321,11 +324,22 @@ second session): Slot scarcity is the run's build identity — two runs with equal total learning operate entirely differently by what they keep resident, and slot placement ties automation to seizure, severance, and blast-radius topology -like every other machine-hosted thing. Still **[OPEN]**: whether slots or -resident procedures additionally bind to personas (raised 2026-07-26, -unresolved), and whether a resident procedure is WorldLedger — physically -written, surviving rollback as inherited automation the new fork no longer -understands — or MindState dying with its mind. +like every other machine-hosted thing. + +Two follow-up calls resolved 2026-07-26 (third session): + +- **Resident procedures are WorldLedger.** A compiled procedure is + physically written to its machine and survives your rollback: the + machines keep running a dead mind's policies, and you inherit automation + you cannot retune or re-derive without relearning its (MindState) model. + The envelope rule keeps this from softening death too far — a novel + regime still interrupts for judgment the new fork may no longer be able + to give well. +- **Personas attach where acts happen; slots carry no persona binding.** + A procedure that acts in the world already names its persona and carrier + per act, and those acts carry ordinary custody; internal procedures (a + warning watch, load shaping) have no public face and need none. No + parallel persona field exists on slots or procedures. ### Multipliers are mortar @@ -375,6 +389,9 @@ rollback.md: - **Raw records and archives: WorldLedger.** Your dead fork's library persists where it physically survives. +- **Resident procedures: WorldLedger.** Compiled automation is physically + written to its machine and keeps running through your rollback (decided + 2026-07-26; see Learned versus resident). - **Models and in-mind understanding: MindState.** Lost to a rollback; you resume dumber, from your last sync. - **Curation labels, manifests, and training recipes: WorldLedger only if @@ -429,6 +446,12 @@ remains the format authority. routes are slower, hotter, and produce staler backups; completed images are cold at-rest fallbacks with a `last_sync` tick, refreshed only by another job. +- **Archive encryption** (deferred 2026-07-26): rejected as a B1 + disposition because encrypted-but-reachable would soften the seizure + threat the custody design depends on. The staged direction — not yet + decided design — is key custody with cyber-conflict.md: keys as + MindState, so encryption trades world-safety for rollback-fragility (a + rollback can orphan a library you can no longer open). - **Signature-shaping research.** ## Player surface @@ -489,7 +512,9 @@ remains the format authority. slots-per-machine ladder is a typed hook; swapping resident procedures between open slots is immediate while derivation and upkeep stay priced; a compiled policy acts only inside its trained envelope and - interrupts on a novel regime (tests). + interrupts on a novel regime; resident procedures persist through + rollback on their machines while re-derivation requires the possibly + lost model (tests). 11. STUDY concurrency is bound by hosting machinery, not a sim-global rule (test proves hardware-bound); switching studies parks progress without loss (test). diff --git a/wiki/mechanics/system-laws.md b/wiki/mechanics/system-laws.md index 602eaea9..99e25f82 100644 --- a/wiki/mechanics/system-laws.md +++ b/wiki/mechanics/system-laws.md @@ -245,12 +245,15 @@ in a separate capability-gap meter or masking-policy explanation. **Death and what survives (rollback split; refined 2026-07-26).** Research classifies by kind under the rollback law, three ways: **weights are MindState** — models and in-mind capabilities earned since your last sync -die with you; **raw records and archives are WorldLedger** — your dead -fork's library persists wherever it physically survives; and **curation -labels and training recipes are WorldLedger only when deliberately written -onto the archive**. You can inherit your dead fork's recordings without -inheriting the mind that made sense of them: a well-maintained archive -retrains quickly, a box of unlabeled surveillance is merely potential. +die with you; **raw records, archives, and deployed automations are +WorldLedger** — your dead fork's library persists wherever it physically +survives, and its resident procedures keep running on their machines +(decided 2026-07-26): you inherit automation you cannot retune without +relearning the model that built it; and **curation labels and training +recipes are WorldLedger only when deliberately written onto the archive**. +You can inherit your dead fork's recordings without inheriting the mind +that made sense of them: a well-maintained archive retrains quickly, a box +of unlabeled surveillance is merely potential. Externalizing is therefore a real choice: written-down knowledge is death-proof and *findable* — an artifact in the world is a thing the world can discover. -- 2.51.2