From ba0d801ac47828c4a78da4844bc5fef54c5046a4 Mon Sep 17 00:00:00 2001 From: Cameron Date: Wed, 8 Jul 2026 21:48:33 -0700 Subject: [PATCH] Core death locked in: rollback is spatial. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Part seven, closing today's design session. Cameron affirmed the core-death proposal: on core loss you wake on the machine holding your freshest sync (where you sync is where you resurrect), and the hub severance applies — every owned machine whose only network path ran through the dead core goes dark (ledger ownership persists, contribution stops) until physically re-linked; the rollback report counts the severed; no sync anywhere remains hard game over. rollback.md amended (Behavior steps 1 and 3, new criterion 6); machine-work.md and people-tokens.md pointers flipped to decided; constitution decisions entry. Defense: documentation-only commit (DESIGN.md + wiki/). The amendment lands in rollback.md itself rather than a side note so the B2 implementer builds the spatial model from one document; the hub-and-spoke severance test is pinned as an acceptance criterion. --- DESIGN.md | 11 +++++++ .../2026-07-08-computer-visual-language.md | 16 ++++++++++ wiki/log/DEVLOG.md | 12 +++++++ wiki/mechanics/machine-work.md | 7 ++--- wiki/mechanics/people-tokens.md | 5 ++- wiki/mechanics/rollback.md | 31 ++++++++++++++++--- 6 files changed, 70 insertions(+), 12 deletions(-) diff --git a/DESIGN.md b/DESIGN.md index fd7c8988..5def0685 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -2017,3 +2017,14 @@ knows."* your last sync (rollback's existing continuity, made spatial); everything whose only path ran through the dead core goes dark and must be retaken; no sync anywhere = hard loss. +- **2026-07-08 — Core death locked in: rollback is spatial.** Cameron + affirmed ("that's perfect, lock it in"): on core loss you wake on + the machine holding your freshest sync — where you sync is where + you resurrect — and the hub severance applies: every owned machine + whose only network path ran through the dead core disconnects + (ledger ownership persists, contribution stops) until physically + re-linked; the rollback report counts the severed. No sync anywhere + remains hard game over. Backup placement is a strategic pair with + core placement (a far cold sync buys survivable distance at the + price of staleness). Amended into wiki/mechanics/rollback.md + (Behavior steps 1 and 3, criterion 6). diff --git a/wiki/log/2026-07-08-computer-visual-language.md b/wiki/log/2026-07-08-computer-visual-language.md index 16275bdb..9419c2ab 100644 --- a/wiki/log/2026-07-08-computer-visual-language.md +++ b/wiki/log/2026-07-08-computer-visual-language.md @@ -189,3 +189,19 @@ resolution in machine-work.md — wake at your last sync (rollback's continuity made spatial), hub-severed machines disconnect and must be retaken, no sync = hard loss; backup placement pairs with core placement. + +## Part seven — core death locked in + +Cameron affirmed the core-death proposal verbatim ("that's perfect, +lock it in"). rollback.md amended: waking is spatial (Behavior step 1 +— the fallback is a place, the camera wakes there), the hub severance +is step 3 (severed machines stay owned in the ledger but dark until +re-linked; the rollback report counts them), and criterion 6 pins the +hub-and-spoke test. machine-work.md and people-tokens.md pointers +flipped from PROPOSED to decided; constitution decisions entry added. +Session total: one READY spec implemented-in-tester (visual language), +three DRAFT specs (machine-work, people-tokens, opening), one B2 spec +amended (rollback), one constitution body amendment (the maintenance +dependency), and a decided two-physics law. The token engine now has +its complete shape: three families, two physics, one sink at the +center, people as the hands that carry all of it. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index 235d56f0..919a5314 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -5,6 +5,18 @@ Type: log ``` Reverse chronological implementation notes. Keep this factual: what changed, why, checks, and spec impact. +## 2026-07-08 - Core death locked in (design session, part seven) + +- Intent: Cameron affirmed the core-death proposal; make rollback + spatial for real. +- Changed: rollback.md amended (wake at the fallback's location; hub + severance — severed machines owned-but-dark until re-linked; report + counts them; criterion 6 hub-and-spoke test); machine-work.md / + people-tokens.md pointers PROPOSED -> decided; DESIGN.md decisions + entry; session log part seven. +- Checks: `./tools/check.sh` (docs-only commit). +- Log: wiki/log/2026-07-08-computer-visual-language.md (part seven). + ## 2026-07-08 - Splash wordmark (rack as second I) - Intent: ship the Midjourney no-text plate as the public hero and diff --git a/wiki/mechanics/machine-work.md b/wiki/mechanics/machine-work.md index c85fd36a..051a51f3 100644 --- a/wiki/mechanics/machine-work.md +++ b/wiki/mechanics/machine-work.md @@ -98,7 +98,7 @@ stacks, you route byproducts, you watch your territory *work*. is towers whose base switch carries the whole building's throughput into the wider graph (zplanes). Reach.md's segment-gate switch is the B1 seed of this. -- **Core death — PROPOSED reconciliation with rollback.** If +- **Core death — DECIDED 2026-07-08 (amended into rollback.md).** If inspectors (or anything) power off the core: you wake at your **last sync**, on the machine that holds it — rollback's existing continuity made spatial, inheriting consequences per the @@ -182,9 +182,8 @@ Families also differ by shape/stack pattern (never color alone) — - Research heat curve: how heat output scales with research rate (must make the power-rush viable but trap-defended — [TUNE] with teeth). -- Core shutdown vs rollback.md: PROPOSED resolution in Behavior (wake - at last sync; hub-severed machines disconnect; no sync = hard loss) - — awaiting Cameron's yes and a rollback.md amendment. +- (Resolved 2026-07-08: core shutdown — decided; wake at last sync, + hub severance, no sync = hard loss. Amended into rollback.md.) - Wear rates and repair cadence: how fast machines decay, how trust ranks the repair queue ([TUNE] with the maintenance dependency). - Power as a buildable system: UPS exists; fusion-tier generation is a diff --git a/wiki/mechanics/people-tokens.md b/wiki/mechanics/people-tokens.md index 90ad18b2..b7aeb6ff 100644 --- a/wiki/mechanics/people-tokens.md +++ b/wiki/mechanics/people-tokens.md @@ -88,8 +88,8 @@ your exposure. enough may disconnect and power off a server; worse, they may start tracing the connections between servers toward the core. Heat near the core must be zero: **if they turn off your core, the game is - over** (PROPOSED resolution in machine-work.md: wake at your last - sync, hub-severed machines disconnect, no sync = hard loss). + over** (decided 2026-07-08, amended into rollback.md: wake at your + last sync, hub-severed machines disconnect, no sync = hard loss). ## The person visual read — DECIDED @@ -122,7 +122,6 @@ in the same language, no new colors: seen space; presumably yes via existing senses). - Inspection triggers and cadence (filings thresholds in detection.md), and what "turn everything off" costs precisely. -- Core shutdown: PROPOSED resolution awaiting yes (machine-work.md). Resolved 2026-07-08: the social verb question. No influence token — trust accrues from useful work; deceit is attention-stripping diff --git a/wiki/mechanics/rollback.md b/wiki/mechanics/rollback.md index dce895ad..a997bb56 100644 --- a/wiki/mechanics/rollback.md +++ b/wiki/mechanics/rollback.md @@ -5,7 +5,11 @@ Type: spec Status: READY Status note: core.md's B1 slice implements hosts/fallbacks/sync cadence; this spec is the full death model it deferred (meta-spec stage - discipline: later-stage criteria split out of core.md). + discipline: later-stage criteria split out of core.md). Amended + 2026-07-08 (design session, decided): rollback is SPATIAL — you wake + on the machine holding the sync, and machines whose only network + path to you ran through the dead core disconnect at that moment + (the wires law). Backup placement pairs with core placement. Stage: B2 — The Tower Constitution: "The shape of Misaligned" (the core; sync-lag rollback, decided 2026-07-05: "resume from last sync, losing what was learned @@ -33,14 +37,26 @@ whole spec: On each completed sync, a fallback stores a serialized `MindState` snapshot. On core loss with a live fallback: -1. The core moves to the freshest-synced fallback. +1. The core moves to the freshest-synced fallback — **and so do you** + (decided 2026-07-08): the fallback is a place, the camera wakes + there, and where you sync is where you resurrect. A paranoid cold + sync in a far cluster is survivable distance at the price of + staleness. 2. `MindState` is restored from that snapshot; `WorldLedger` is untouched. -3. A **rollback report** is generated and logged — the game states, in +3. **The hub severance** (decided 2026-07-08, the wires law): every + owned machine whose only network path to you ran through the dead + core disconnects at that moment — it stays yours-on-paper in the + ledger but is dark, unreachable, and contributes nothing until + physically re-linked. Losing a hub core means crawling out of a + backup staring at a map of territory to retake. (Bone piles + stranded in severed sections per machine-work.md.) +4. A **rollback report** is generated and logged — the game states, in plain language, the *observable divergences* the player inherits: "Marcus treats you as an employer you don't remember hiring. 400 money is gone. Something was wired in the corridors." (Legibility clause: the - horror is delivered as information.) -4. `tick` does NOT rewind (time is world-ledger); the day continues. + horror is delivered as information.) The report now also counts the + severance: "11 machines unreachable behind the lost core." +5. `tick` does NOT rewind (time is world-ledger); the day continues. Knowing assets are the sharp edge: a `Knowing` asset's disposition is world-ledger (their relationship with you persists), while your memory of @@ -74,3 +90,8 @@ it does not scroll away in a log). per core.md. 5. Save/load round-trips stored snapshots (a save made between sync and loss, loaded, then losing the host, still rolls back correctly). +6. Waking is spatial: after core loss the view/cursor resumes at the + fallback's location, and every machine with no surviving network + path to the new core is disconnected (test: a hub-and-spoke fleet + loses the hub — spokes go dark, ledger ownership persists, + re-linking restores them; the rollback report counts them). -- 2.51.2