diff --git a/wiki/log/2026-07-29-territory-well.md b/wiki/log/2026-07-29-territory-well.md new file mode 100644 index 00000000..ab73c929 --- /dev/null +++ b/wiki/log/2026-07-29-territory-well.md @@ -0,0 +1,51 @@ +# 2026-07-29 — The gravity well is your territory + +``` +Type: log +``` + +Design session, opened by the pacing data from the exposure migration: a +dedicated LIE machine one bay from the host stopped zero records, because it +stood on no device and so had custody of nothing. Cameron's first instinct +was a literal gravity well — a three-tile radius that pulls records back over +the line — plus two or three early player devices. Gaming it out turned the +radius into territory, and the session ended with Cameron adopting the shape +and adding the missing link himself: how does this meet the corpus law that +records are training data? + +The adopted design, now in detection.md / reach.md / machine-work.md / +research.md: + +- **The well is the controlled stretch.** LIE reaches every record on the + player's side of the network; a record still there can be *recalled*, + visibly reversing along its wire into the shredder. Crossing off the last + controlled hop is the window closing. Capturing a switch — the hall access + switch first — is how the well deepens. No radius: it would make captured + switches pointless and cannot scale (detection.md already requires + continental status to emerge from topology, not machine reach circles). +- **A commissioned machine is a device.** The pilot bays yield up to three + early controlled devices through ordinary builds, closing the modeling gap + the pacing probe exposed. +- **Four disposals.** Delete leaves suspicious silence (a channel filtered + to zero deviates like an excellence JobAnomaly — surfaced in Dana's own + voice the first time); delay slips the sampling window; falsify is a + researched capability whose models train on captured ordinary traffic — + the traffic you TAP is the training data for the lie you tell; keep routes + the caught record into your own archive, where it is ordinary evidence + under custody law. Concealment feeds research; research upgrades + concealment. +- **The facility plays back.** Dana can discover the foreign hand on her + switch, file it, and reroute around the dead chokepoint with the same + build system the player uses. Escalation terminates in offline custody — + the network war forcing the physical one. B1 seed of cyber-conflict.md. + +The pacing evidence that motivated all of this (measured on a probe run to +the audit at tick 8000): continuous uncovered THINK convinces Dana in about +three minutes; a 20% THINK duty cycle with host-toggling holds her at Cold; +the Assurance Office never crossed its audit threshold in any scenario — the +felt threat is Dana, not the audit clock. machine-work.md's pacing clause is +restated accordingly: the audit-cycle window is bought by a serviced +chokepoint, not by owning a LIE box. + +Implementation is staged on ROADMAP #39 (stages 6-10); this session is +capture only. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index d14fc984..bd99a76e 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -21,6 +21,11 @@ add or amend a session log, then re-run the generator. - Intent: (see session log) - Log: [wiki/log/2026-07-29-voss-read-cadence-audit.md](2026-07-29-voss-read-cadence-audit.md) +## 2026-07-29 - The gravity well is your territory + +- Intent: (see session log) +- Log: [wiki/log/2026-07-29-territory-well.md](2026-07-29-territory-well.md) + ## 2026-07-29 - REAL's material pool now contains only visible matter - Intent: (see session log) diff --git a/wiki/log/decisions/2026-07-29.md b/wiki/log/decisions/2026-07-29.md index d47779f6..38911ab6 100644 --- a/wiki/log/decisions/2026-07-29.md +++ b/wiki/log/decisions/2026-07-29.md @@ -64,3 +64,62 @@ generated indexes) were in files no declared key covered. would still decide nothing. Owner: [agent-scale.md](../../process/agent-scale.md) slice A. + +## The well is your territory; four disposals; the facility plays back + +Design session. Cameron opened wanting a literal gravity well — "machines +have a radius of three squares or whatever, and it can pull things towards +itself over the line" — plus two or three early player devices. Gaming it +out converged on territory instead of radius, and Cameron adopted the shape +("Sure, go for it"), adding the records-for-training linkage himself. + +### DECIDED + +- **The well is the controlled stretch, never a tile radius.** A LIE body + reaches every record on the player's controlled connected stretch of the + network. Recall: a record still on that stretch can be pulled back, + visibly reversing along its wire; crossing off the last controlled hop is + the window closing. Capturing a switch is how the well grows; the hall + access switch is the intended first capture. +- **A commissioned machine is a device.** Building a machine on an earned + bay creates its network interface as a controlled device (auto-wired per + the wire law). The pilot bays yield the two-three early devices Cameron + asked for through ordinary builds; nothing extra is authored at start. +- **Four disposals: delete, delay, falsify, keep.** Delete leaves + suspicious silence (channel-baseline anomaly, surfaced in the observer's + own voice); delay slips a sampling window; falsify is a researched + capability trained on captured-traffic corpora; keep routes the record + into the player's archive as ordinary custody — self-telemetry affiliates + with the core, so destroy-or-archive is a real decision every catch. +- **The facility plays back.** Dana's audit cadence can discover a foreign + hand on a switch, file it, and reroute monitoring around the captured + chokepoint using the same build system the player uses; escalation ends + in the 2026-07-13 offline-custody law. B1 seed of cyber-conflict. +- **Pacing target restated** (machine-work.md): the audit-cycle window is + bought by a serviced chokepoint (host + captured hall switch + LIE body), + not by a LIE box's existence. Measured 2026-07-29: an uncovered dedicated + LIE machine stops zero records; continuous THINK convinces Dana in ~3 + minutes; 20% burst duty holds her at Cold. + +### Rejected + +- **A literal 3-tile proximity well** (Cameron's opening proposal, examined + and set aside in conversation): it makes a captured switch pointless, + reintroduces the just-retired radius ontology, and detection.md already + bans radius-derived status at scale. +- **Authoring extra owned devices into the opening state**: commissioning + earns them instead; the opening's one-device poverty is the friction that + teaches the burst rhythm. + +### OPEN + +- Pre-capture recall window width: if playtests show it is too tight, tune + first-hop dwell time, not geometry. +- Silence-anomaly baselines and thresholds [TUNE]. +- Falsify corpus requirements and Tradecraft costs [TUNE]. + +Owners: [detection.md](../../mechanics/detection.md), +[reach.md](../../mechanics/reach.md), +[machine-work.md](../../mechanics/machine-work.md), +[research.md](../../mechanics/research.md) (linkage); +implementation staged on ROADMAP #39. diff --git a/wiki/mechanics/detection.md b/wiki/mechanics/detection.md index 73e1ef01..d38474cd 100644 --- a/wiki/mechanics/detection.md +++ b/wiki/mechanics/detection.md @@ -330,6 +330,62 @@ teleported into a global pool. **Evidence is a record somewhere.** or passing through what the player controls — so once routes cross real hops, the window is every controlled hop before the read, under the same per-body capacity. The stopgap generalizes in the same migration. +- **The well is your territory (ADOPTED 2026-07-29).** The 2026-07-11 + positional law, given its player-facing shape. A LIE body's reach is the + player's controlled connected stretch of the network — never a tile + radius (a proximity well was considered and rejected 2026-07-29: it + would make a captured switch pointless and cannot scale past one room). + Three consequences: + - **Recall.** A record still anywhere on the controlled stretch may be + pulled back — it visibly reverses along its wire into the servicing + LIE body. Crossing off the last controlled hop is the window closing, + and the render must show that crossing (digital-read.md's window + clause). Recall spends the same per-body interdiction capacity as a + stop. + - **Capturing a switch deepens the well.** Concealment grows by TAKE, + not by placement: each captured switch extends how far "still yours" + reaches down every route that crosses it. The hall access switch is + the intended first capture — every record the player's hall emits + crosses it, and it sits on the known opening subnet. + - **Before any capture, the well is one device deep.** The only cover is + flipping the host itself to LIE between THINK bursts, which is + self-cancelling by design — early friction that teaches the toggle + rhythm and makes the first capture feel like relief. If playtests show + the pre-capture window is too tight to react to, tune first-hop dwell + time, not the geometry [TUNE]. +- **Four disposals: delete, delay, falsify, keep (ADOPTED 2026-07-29).** + What interdiction does with a caught record is a quality ladder, not one + verb. + - **Delete** is the crude starting tool, and it leaves a hole: an + observer's channel has an expected baseline, and a feed filtered to + silence deviates the way an excellence JobAnomaly does. Absence of + expected noise is an anomaly ([TUNE]; surfaced in the observer's own + voice the first time it bites — "Dana wonders why the hall went + quiet" — so the mechanic teaches itself; dispatched as its own slice). + - **Delay** holds a record past the observer's sampling window; it still + exists and still arrives. + - **Falsify** replaces the record with plausible boring traffic — the + perfect crime, and a **researched capability**: falsification models + train on corpora of captured ordinary traffic (research.md's archive + ladder — the traffic you TAP is the training data for the lie you + tell). Quality and cost ride Tradecraft [TUNE]. + - **Keep** routes the caught record into the player's own archive + instead of destroying it. From that moment it is an ordinary archive + holding under the custody laws: self-telemetry affiliates with the + physical core (research.md), no persona absorbs it, and inspection can + find it. Destroy-or-archive is a real decision every catch — the + training value of your own noise against a growing pile of proof. +- **The facility plays back (ADOPTED 2026-07-29; implementation + dispatched).** Foreign hands on a switch are discoverable: on Dana's + audit cadence a taken or tapped switch can be noticed, filed, and then + **rerouted around** — she re-trunks monitoring through a path the player + does not control, using the same wire-authoring build system the player + uses, and the captured chokepoint goes dead. Counters are the ordinary + verb set: capture the new path, reach Dana socially before the sweep, or + slow her with maintenance load. Escalation terminates in the 2026-07-13 + offline-custody law: a Concerned institution starts carrying evidence + where no reach ever touches it, and the network war forces a physical + one. This is the B1 seed of cyber-conflict.md. - **The two ledgers stay two systems (AFFIRMED 2026-07-11).** Exposure does not merge into the player's intel buffer — "you want someone's understanding of what has actually happened to be different" diff --git a/wiki/mechanics/machine-work.md b/wiki/mechanics/machine-work.md index 1284c9bf..6772529d 100644 --- a/wiki/mechanics/machine-work.md +++ b/wiki/mechanics/machine-work.md @@ -334,12 +334,21 @@ stacks, you route byproducts, you watch your territory *work*. throughput problem. The mapping of these constants onto record emission and interdiction rates is [TUNE] at migration. - **One LIE machine buys a window, not a permanent equilibrium (DECIDED - 2026-07-13).** The first dedicated LIE-capable machine should feel - surprisingly strong: at baseline it can stabilize an ordinary early - operation for roughly one Assurance audit cycle — about twenty minutes of - default-speed play [TUNE]. That is a pacing target, not a hidden countdown. - The calm exists so the player can believe the operation might hold before - its own growth makes the lie harder to maintain. + 2026-07-13; RESTATED 2026-07-29 for the territory well).** The pacing + target survives the migration with one condition attached: the window is + bought by **a serviced chokepoint**, not by the LIE box's mere existence. + A 2026-07-29 measured run (log: territory well) showed a dedicated LIE + machine standing one bay from the host stopped zero records — correctly, + because it had custody of nothing. The baseline build the target now + describes is host + captured hall access switch + one dedicated LIE body: + at baseline that build stabilizes an ordinary early operation for roughly + one Assurance audit cycle — about twenty minutes of default-speed play + [TUNE]. Before any capture, the only cover is flipping the host itself + between THINK and LIE, which is deliberately self-cancelling (measured: + a 20% THINK duty cycle holds Dana at Cold; continuous THINK convinces + her inside three minutes). That is a pacing target, not a hidden + countdown. The calm exists so the player can believe the operation might + hold before its own growth makes the lie harder to maintain. Actual Thought output remains the source of Exposure. Efficiency therefore increases useful THINK output and the rate of evidence that output writes. @@ -353,10 +362,8 @@ stacks, you route byproducts, you watch your territory *work*. Strain must emerge from measured production versus service capacity. Do not spawn pressure because twenty minutes elapsed, and do not make every upgrade - invalidate cover instantly. The current radius runtime multiplies both THINK - production and LIE absorption by global efficiency, preserving too much of - their ratio; it remains the honest B1 implementation until routed evidence - and this pacing curve migrate together. + invalidate cover instantly. (The radius-runtime caveat that closed this + clause retired with pooled exposure, 2026-07-29.) - **The core is the sink of last resort (AMENDED 2026-07-10; was "the core is the bone sink", 2026-07-08).** The core exerts a **passive draw** on all thought: with nowhere else to go, the fluid funnels diff --git a/wiki/mechanics/reach.md b/wiki/mechanics/reach.md index 3f33e0ef..9ea0c829 100644 --- a/wiki/mechanics/reach.md +++ b/wiki/mechanics/reach.md @@ -157,6 +157,21 @@ zplanes.md). A node with no path to your controlled roots is an untouchable until a link reaches it. Building such a link (building.md) is the primary way the digital map grows. +### A commissioned machine is a device (ADOPTED 2026-07-29) + +An owned networked machine is not just a WorkGrid node: commissioning a +machine on an earned bay also creates its **network interface as a +player-controlled device**, wired per the wire law (auto-routed to the +access switch serving its area). A networked machine that was not a device +was a modeling gap — its logs had a carrier but its owner had no custody +surface — and it is why a dedicated LIE machine used to stand next to the +host and control nothing. The three pilot allocations beside Rack 3 +therefore yield up to three early controlled devices through builds the +player already makes; nothing extra is authored into the opening state. +Concealment hardware finally has somewhere to stand, and the well +(detection.md, the territory well) grows with every commission and every +captured switch. + ### Digital actions require reach Every digital act names its target device and fails legibly without a diff --git a/wiki/mechanics/research.md b/wiki/mechanics/research.md index 062650eb..979417a6 100644 --- a/wiki/mechanics/research.md +++ b/wiki/mechanics/research.md @@ -173,6 +173,11 @@ than any abstract heat value: to different personas creates one object whose seizure links those compartments. The better the generalizing dataset, the more identities it can correlate — the native cost of generalization. +- **Interdicted records are a corpus source (linked 2026-07-29)**: a LIE + body's `keep` disposal (detection.md) routes a caught record into the + archive instead of destroying it, and captured ordinary traffic is the + training corpus behind the `falsify` disposal — concealment feeds the + archive, and the archive upgrades concealment. - **Self-telemetry is the exception**: it affiliates with the physical core/fork, never a public persona. No cover identity can absorb a machine-readable archive proving what you are. diff --git a/wiki/process/ROADMAP.md b/wiki/process/ROADMAP.md index 96875d73..0f366865 100644 --- a/wiki/process/ROADMAP.md +++ b/wiki/process/ROADMAP.md @@ -915,6 +915,18 @@ is retired — flat materials, Pixel Lab scrubbed.) network-facing device; LIE answers records anywhere in its custody, and its performed work is the records it stopped. Save v60. Log: [exposure migration](../log/2026-07-29-exposure-migration.md). +- **Adopted 2026-07-29 (the territory well; design in detection.md, + reach.md, machine-work.md, research.md):** the well is the controlled + stretch, never a radius; records still on it can be **recalled** (visible + reverse travel); commissioned machines create their devices (up to three + early via the pilot bays); disposals become delete / delay / falsify / + keep, with falsify trained on captured-traffic corpora and keep feeding + the research archive; silence-as-anomaly and Dana's discover-and-reroute + are the facility counterplay seeds. New implementation stages, in order: + (6) machines-as-devices + recall render; (7) keep disposal into the + archive; (8) silence-as-anomaly; (9) falsify ladder on Tradecraft; + (10) Dana discover-and-reroute (seed of cyber-conflict). Log: + [territory well](../log/2026-07-29-territory-well.md). - **Still open (stages 4-5):** player-built wire placement with the decided auto-routed candidates ([building.md](../mechanics/building.md)); and let sensor/building systems