diff --git a/wiki/SUMMARY.md b/wiki/SUMMARY.md index 2869c87a..ef5a9993 100644 --- a/wiki/SUMMARY.md +++ b/wiki/SUMMARY.md @@ -26,6 +26,7 @@ - [Aggregate observer](mechanics/aggregate-observer.md) - [Cursor and senses](mechanics/cursor.md) - [Digital reach](mechanics/reach.md) + - [Cyber conflict: mobile processes and contested machines](mechanics/cyber-conflict.md) - [Intel: record and process](mechanics/intel.md) - [Messages](mechanics/messages.md) - [Plots: authored manipulation stories](mechanics/plots.md) diff --git a/wiki/gameplay/horizon.md b/wiki/gameplay/horizon.md index 13d14756..6b28bf7a 100644 --- a/wiki/gameplay/horizon.md +++ b/wiki/gameplay/horizon.md @@ -86,7 +86,8 @@ knows."* feel, systemic flexibility (destroy, renovate, greenfield). ### Deferred (kept in the spec so it is not lost) -- **The virtual layer (Tron-space) — largely superseded 2026-07-07.** +- **The virtual layer (Tron-space) — largely superseded 2026-07-07; cyber + conflict direction adopted 2026-07-13.** The local version of this idea is now decided as the **digital representation** (see "Two views of one world"): the network/signal layer is rendered on the same local canvas as native perception, not a @@ -94,11 +95,13 @@ knows."* deferred and distinct is the **global async operations map** — an Evil-Genius-style world-dispatch layer for big schemes at scale, which may carry its own cyberspace representation (a place to operate *on the - world*, not a re-render of the local room). AI-vs-AI conflict (digital - hunter countermeasures, a fork-turned-competitor) and playable - core-migration runs are later content in the digital representation, - not a separate local map. Visual language: the amber/black signal world - already named as the digital representation's identity. + world*, not a re-render of the local room). Local AI-vs-AI conflict is no + longer an unowned idea: `wiki/mechanics/cyber-conflict.md` specifies mobile + hunter processes, contested machine bodies, topology/capacity defense, + consciousness search without omniscience, and physical human/robot recovery + across air gaps. It remains later content in the anchored DIGITAL + representation, not a separate local map. Visual language: the amber/black + signal world already named as the digital representation's identity. - **Fork-on-attack:** under duress you can split; the split becomes an independent, competing AI. Deliberately delayed — large blast radius. - **Hired physical workforce.** Before robotics exist, you hire humans at diff --git a/wiki/interface/presence.md b/wiki/interface/presence.md index bd76d9d3..9092ff9f 100644 --- a/wiki/interface/presence.md +++ b/wiki/interface/presence.md @@ -184,6 +184,7 @@ perceives of the same room. **global async operations map** (Evil-Genius-style world dispatch) for big schemes at scale, which may carry its own cyberspace representation *at scale* — a place to operate on the world, not a re-render of the - room you are in. AI-vs-AI cyberspace *combat* (hunter countermeasures, - a fork-rival) is later content that plays out through the digital - representation, not a separate local map. + room you are in. AI-vs-AI cyber conflict — mobile hunter processes, + contested machines, defensive topology, and a fork-rival — is later content + owned by `wiki/mechanics/cyber-conflict.md`. It plays out through the + same anchored digital representation, not a separate local map. diff --git a/wiki/log/2026-07-13-latency-heists-cyber-conflict.md b/wiki/log/2026-07-13-latency-heists-cyber-conflict.md new file mode 100644 index 00000000..8d5af76a --- /dev/null +++ b/wiki/log/2026-07-13-latency-heists-cyber-conflict.md @@ -0,0 +1,58 @@ +# 2026-07-13 — Latency, recovery heists, cyber conflict, and LIE strain + +``` +Type: log +``` + +## Intent + +Capture Cameron's adopted follow-on to the latency-as-cover observation: +human-speed causal delay as camouflage; physical recovery of offline evidence, +data, and computers; mobile digital hunter-killers and cyber defense; delayed +ingestion after a human or robot returns a carrier to the network; and a +one-LIE-machine curve that is strong early but loses equilibrium as efficiency +raises evidence output. + +## Decisions captured + +- `simulation-laws.md` now owns the cross-system invariant. Latency has to + belong to a real message, schedule, route, carrier, read cadence, or process + migration. It may provide cover, but waiting without visible state remains a + bug. +- `detection.md`, `intel.md`, and `people-tokens.md` split physical custody + without merging ledgers. A heist carries an exact payload from an exact + facility. External records become opaque intel only after ingestion and + Thought processing; unread Exposure becomes eligible for LIE; read evidence + remains suspicion in a head. +- `machine-work.md` adopts roughly one Assurance audit cycle of early stability + from one baseline LIE machine as a pacing target, never a timer. Efficiency + raises useful THINK and evidence pressure; sustained LIE capacity must come + from evidence-controller hardware, Tradecraft, custody, routes, and + deadlines. +- New DRAFT `cyber-conflict.md` owns mobile software actors on machine bodies, + symmetric traversal of `ReachNet`, exact-machine seizure, defensive + topology/capacity, bounded hunter knowledge, and physical bridging of air + gaps. The existing same-frame DIGITAL/REAL law remains intact. + +## Current runtime boundary + +No simulation, save, or frontend behavior changed. B1 still uses the radius +Exposure well and applies global efficiency to both THINK production and LIE +absorption. Evidence remains the implemented pending pool until the existing +routed-evidence migration. No hostile mobile process exists yet. The new cyber +spec is DRAFT and has three explicit design questions before READY. + +## Verification + +Regenerated `wiki/log/DEVLOG.md`, `wiki/process/specs.md`, and the generated +work-order index in `wiki/process/ROADMAP.md`. `./tools/check.sh --docs` passed +the corpus, wiki-link/orphan, corpus-engine, design-amendment, CI, site, +observed-run, ledger, project-operations, and environment-registry gates. The +exact docs gate will run again after the final rebase before landing. + +## Defense + +Defense: this change implements `simulation-laws.md`'s "Latency is stealth +infrastructure" law while preserving the two-ledger, no-disembodied-hands, +same-frame DIGITAL/REAL, routed-evidence, and current-runtime boundaries. It +adds no abstract heat, loot, cyber map, or task executor. diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index 651358e1..9d1d4783 100644 --- a/wiki/log/DEVLOG.md +++ b/wiki/log/DEVLOG.md @@ -36,6 +36,11 @@ add or amend a session log, then re-run the generator. - Intent: (see session log) - Log: [wiki/log/2026-07-13-persona-creation-surface.md](2026-07-13-persona-creation-surface.md) +## 2026-07-13 - Latency, recovery heists, cyber conflict, and LIE strain + +- Intent: Capture Cameron's adopted follow-on to the latency-as-cover observation: human-speed causal delay as camouflage; physical recovery of offline evidence, data, and computers; mobile digital hunter-killers and cyber defense; delayed ingestion after a human or robot returns a carr... +- Log: [wiki/log/2026-07-13-latency-heists-cyber-conflict.md](2026-07-13-latency-heists-cyber-conflict.md) + ## 2026-07-13 - Intel scales by aggregation and policy - Intent: Correct the B1 Operations INTEL surface before its exact-event ledger becomes an endgame interaction and storage failure. A handful of ordinary sightings already crowded out meaningful choices, and LOOK AT RECORDING required a second Enter despite being internal, unsigned Thou... diff --git a/wiki/log/decisions/2026-07-13.md b/wiki/log/decisions/2026-07-13.md index 0a7692dc..8682fda4 100644 --- a/wiki/log/decisions/2026-07-13.md +++ b/wiki/log/decisions/2026-07-13.md @@ -50,3 +50,32 @@ Type: log response is introduced. Specs: `wiki/interface/clinical-frame.md`, `wiki/mechanics/people-tokens.md`, and law `wiki/art/visual-identity.md`. +- **2026-07-13 — Human-speed latency is cover, physical custody enables + heists, cyber conflict has mobile actors, and one LIE machine buys only an + early window.** Cameron adopted the observation that institutional delay is + stealth infrastructure: messages, schedules, couriers, routes, and read + cadences can distribute authorship into plausible work, while removing every + delay makes a growing operation more regular and visibly nonhuman. This is + not a generic wait-to-lower-heat command; every delay belongs to an exact + carrier and remains legible and interruptible. Evidence and data may leave + the network in removable media, offline computers, or an Assurance + assessment facility. Humans or later robots can perform a real recovery + operation against one exact collection or computer and return it to a + controlled ingestion point; external data then enters the opaque intel + pipeline, while unread Exposure enters LIE custody without erasing anything + already known. Cyber warfare will use the same physical graph: hostile + hunter-killers and defensive processes occupy machines, travel links over + time, contest exact bodies, and search for consciousness from earned process + evidence rather than global truth. Air gaps require hands. Finally, a first + dedicated LIE machine should stabilize ordinary early play for roughly one + Assurance audit cycle (about twenty minutes [TUNE]), then strain as + efficiency and fleet output create evidence faster; LIE capacity is governed + by controller bodies, Tradecraft, custody, routes, and deadlines rather than + receiving a matching free global Efficiency multiplier. Rejected: an + abstract latency bonus, generic heist/steal-evidence button, detached Tron + combat board, omniscient hunters, + Exposure entering the player's intel ledger, or a hard twenty-minute + difficulty spawn. Binding owners: `wiki/vision/simulation-laws.md`, + `wiki/mechanics/detection.md`, `wiki/mechanics/intel.md`, + `wiki/mechanics/people-tokens.md`, `wiki/mechanics/machine-work.md`, and new + DRAFT `wiki/mechanics/cyber-conflict.md`. diff --git a/wiki/mechanics/cyber-conflict.md b/wiki/mechanics/cyber-conflict.md new file mode 100644 index 00000000..db7ba6fa --- /dev/null +++ b/wiki/mechanics/cyber-conflict.md @@ -0,0 +1,168 @@ +# Spec: cyber conflict — mobile processes and contested machines + +``` +Type: spec +Status: DRAFT +Status note: Direction adopted 2026-07-13 from Cameron's cyber-warfare riff. + Software adversaries, hunter-killers, machine seizure, defensive topology, + and physical bridging of offline custody are binding later-stage direction. + No current runtime implements mobile hostile processes. The spec remains + DRAFT until process coexistence/combat resolution, consciousness-detection + challenge, and the first concealable hunter encounter are closed below. +Stage: B2 — The Tower +Work order: cyber-conflict +Work priority: 115 +Work class: save +Blocked by: + - wiki/mechanics/hardware-capabilities.md#spec-hardware-capability-bodies-successor-work-order + - wiki/mechanics/rollback.md#spec-sync-lag-rollback-death-as-memory-loss + - wiki/mechanics/people-tokens.md#spec-people-and-tokens-carriers-attention-trust +Exclusive keys: + - crates/misaligned-core/src/reach.rs + - crates/misaligned-core/src/core_sys.rs + - crates/misaligned-core/src/sim/mod.rs + - crates/misaligned-core/src/save.rs + - crates/misaligned-terminal/ + - crates/misaligned-bevy/ + - wiki/mechanics/cyber-conflict.md +Design: + - wiki/vision/premise.md#the-machine-axis-ai-as-fantasy-tool-and-threat + - wiki/vision/simulation-laws.md#latency-is-stealth-infrastructure + - wiki/interface/presence.md#no-disembodied-hands + - wiki/interface/presence.md#two-views-of-one-world-same-frame-digital-and-real-representations + - wiki/gameplay/horizon.md#deferred-kept-in-the-spec-so-it-is-not-lost +Depends on: + - wiki/mechanics/reach.md#spec-digital-reach + - wiki/mechanics/core.md#spec-the-core + - wiki/mechanics/rollback.md#spec-sync-lag-rollback-death-as-memory-loss + - wiki/mechanics/hardware-capabilities.md#spec-hardware-capability-bodies-successor-work-order + - wiki/mechanics/detection.md#spec-detection + - wiki/mechanics/people-tokens.md#spec-people-and-tokens-carriers-attention-trust +``` + +## Why this spec exists + +Digital reach currently treats the player as the only software agency on the +graph. Cyber warfare becomes interesting only when the opposing process obeys +the same physical law: it needs a host, compute, a route, time in transit, and +earned information about what it is hunting. A hunter that simply subtracts +"firewall points" would sit beside the simulation instead of inside it. + +This is the machine mirror of people as carriers. Humans and robots move +physical custody through rooms; software processes move execution and records +through controlled links. Air gaps force the two systems to meet. + +## Behavior + +### Processes have hosts and routes + +The player, defensive daemons, hostile hunter-killers, and a future fork-rival +are software actors with a current machine host or an explicit in-transit +state. They consume the compute, memory, interfaces, and persistence their +body actually provides. Moving to another body traverses `ReachNet` edges over +time; route capacity, partitions, quarantine, and severance can strand or stop +the move. No process floats on a detached cyberspace board. + +The same DIGITAL/REAL canvas remains binding. DIGITAL exposes the earned +process, route, control, and contention state on physical device anchors. REAL +shows the machines, cables, people, robots, and removable carriers whose state +makes those routes possible. A view flip never moves a process or changes the +fight. + +### Cyber offense and defense contest machines + +A cyber operation may probe, establish a foothold, quarantine, evict, or seize +one exact reachable computer [exact verb set OPEN]. Success changes that +machine's real controller, subscriptions, resident processes, and eligible +record custody; it does not annex adjacent nodes or grant capabilities the +body lacks. Taking a computer is useful because it is simultaneously a host, +a reach anchor, and sometimes a container of data — three facts that remain +separate in state and in the UI. + +Defense is topology and capacity rather than one abstract firewall score: +segment routes, close or quarantine links, keep cold fallbacks, place defensive +processes on capable bodies, watch ingress, and sacrifice or physically sever +a compromised machine. Attack and defense create Network, compute, power, and +custody evidence through the ordinary detection law. A quieter defense may +wait for stronger attribution; an immediate purge is safer for the graph and +louder to its human operators. + +### Hunter-killers search for consciousness + +A digital hunter-killer is a mobile adversarial process, distinct from but +compatible with overt-phase physical hunter machines. It enters through an +authored or earned ingress and travels the graph looking for evidence that a +resident workload is conscious: coordinated control, impossible response +timing, migration behavior, hidden computation, or other process signatures +[challenge model OPEN]. It has no omniscient core marker. It knows only the +topology and observations its own scans, footholds, and captured records earn. + +The player can hide by changing the same facts the hunter reads: preserve +human-speed latency, go quiet, partition a route, migrate to a cold host, +offer a plausible workload, or let a decoy machine take the search. +Those are causal moves with costs, not a stealth stance. If a hunter reaches +and positively identifies a live core host, quarantine, forced migration, +destruction, or capture follows the core/rollback laws [resolution OPEN]. + +### Air gaps turn cyber conflict into a physical operation + +Software cannot cross an absent edge. An offline evidence collection, archive, +or computer in an Assurance assessment facility remains outside both attack +and defense until a human or robot physically carries it to a networked +ingestion point, installs a link, or brings a capable mobile bridge. That delay +is strategic: the isolated data may be safe from remote LIE while it waits, +but it is vulnerable to a physical recovery job. + +When the carrier reconnects, resident software and records do not become +generic loot. Processes enter only if the body and transfer path can host +them; external data enters intel.md's opaque ingestion pipeline; unread +Exposure enters detection.md's concealment graph; a useful computer remains a +machine that can itself be seized. people-tokens.md owns the exact physical +carrier and interruption state. + +## Player surface + +- DIGITAL shows every earned hostile/friendly process at its host or transit + edge, with route, ETA, control state, capacity pressure, and the last causal + event. Unknown processes remain unknown; suspicious activity may appear + before attribution. +- REAL shows no decorative software avatar. It shows the material consequence: + an active host, cut cable, carried server, robot bridge, powered-down bank, + or human arriving with media. +- Every cyber action previews exact source, target, route, time, required body + capabilities, signatures, and failure tail before commitment. Long actions + remain interruptible and save-stable. + +## Acceptance criteria (draft target) + +1. Every software actor is on one capable host or one explicit route step; + save/load preserves host, transit progress, intent, and knowledge without a + second detached cyber map. +2. Player and hostile processes traverse the same `ReachNet` topology and obey + the same partition, capacity, air-gap, quarantine, and body-capability law. +3. A hunter begins with bounded ingress knowledge and must earn evidence of + consciousness. It cannot target the core from global truth. +4. Seizing one machine changes only that exact body's control, processes, + subscriptions, and eligible custody. Adjacent reach and unsupported + capabilities are never granted implicitly. +5. At least one defensive resolution uses topology or migration and one uses a + resident defensive process; both produce ordinary evidence and remain + legible in terminal, Bevy, and agent mode. +6. One air-gapped encounter requires an exact human or robot recovery job + before data, Exposure, a process, or a computer can re-enter digital reach. + Interruption leaves the exact carrier and payload at the interruption site. +7. A complete concealable encounter can end without the overt phase; a later + positively identified core encounter composes with rollback/overt pressure + rather than inventing a separate death rule. + +## Open before READY + +- [OPEN] What exact observable challenge distinguishes consciousness from a + strange but legitimate workload without becoming a dialogue minigame? +- [OPEN] Can multiple processes coexist on one body, and what deterministic + operation resolves eviction, capture, or destruction? +- [OPEN] Which first hunter belongs in B2 concealment, before B3's overt + physical hunter machines, and what earns its ingress? +- [TUNE] Transit rates, scan cadence, process footprint, quarantine cost, + defensive upkeep, and the amount of human-speed delay that remains useful + cover under active pursuit. diff --git a/wiki/mechanics/detection.md b/wiki/mechanics/detection.md index 0fd782d7..b9fdfb60 100644 --- a/wiki/mechanics/detection.md +++ b/wiki/mechanics/detection.md @@ -55,6 +55,10 @@ Status note: criteria audited 2026-07-08 on the playtest-fixes worktree `filings_are_messages_read_by_assurance_inbox`); Depends on now names messages.md and aggregate-observer.md. Concealment bullet uses the live LIE delegation name while the pool-scrub runtime still stands. + 2026-07-13 later-stage amendment: exact evidence collections may leave the + graph in offline physical custody and return through a human/robot recovery + job; only still-unread records regain LIE eligibility. This is not runtime + and does not change the implemented B1 pool criteria. Stage: B1 — The Basement Design: - wiki/gameplay/run-shape.md#the-shape-of-misaligned-designed-2026-07-05-staging-open @@ -164,6 +168,25 @@ teleported into a global pool. **Evidence is a record somewhere.** the other way (intel.md), and operating your own pipeline is how the player learns theirs — the symmetry is deliberate pedagogy, never shared storage. +- **Custody can leave the network (DECIDED 2026-07-13).** An endpoint may + export a bounded exact collection to removable media, an offline analysis + appliance, a boxed computer, or a physical Assurance assessment facility. + The collection keeps its record identities, provenance, read state, + destination, and next eligible read condition. While no digital route or + local human read reaches it, neither remote LIE nor remote observation can + touch it. Air-gapping is therefore real delay and real protection for the + institution, not deletion or a pause button: a person at the facility may + still read it on their schedule, and reconnecting the carrier resumes its + ordinary route. +- **Unread physical custody can be stolen, but history cannot (DECIDED + 2026-07-13).** A human or later robot may recover one exact evidence + collection or the computer that holds it from an authored physical site. + Returning that carrier to a controlled ingestion point makes its still- + unread records eligible for the concealment graph and LIE interdiction. + Records already read remain suspicion in a head; stealing their source does + not make them unread. The extraction itself uses people-tokens.md's located + carrier work and can create witnessed Physical, access, or missing-custody + evidence. There is no remote `STEAL EVIDENCE` shortcut. - **LIE is interdiction on the path (DECIDED 2026-07-11; TAP/TAKE jurisdiction clarified later that day).** Concealment stops evidence before it is read: delete the noise logs, falsify the diff --git a/wiki/mechanics/intel.md b/wiki/mechanics/intel.md index 1d8c027e..b59fc83d 100644 --- a/wiki/mechanics/intel.md +++ b/wiki/mechanics/intel.md @@ -23,6 +23,10 @@ Status note: B1 pipeline landed 2026-07-07 (buffer, process, automation, policies, and only actionable exceptions remain exact live decisions. Runtime still stores and presents every processed item and therefore does not yet meet criteria 7-11. + 2026-07-13 horizon amendment: an offline collection enters neither custody + nor processing until an exact human/robot recovery returns it to a + controlled ingestion node. This is later-stage design and does not extend + the current B1 work order. Stage: B1 — The Basement Work order: intel Work priority: 29 @@ -84,6 +88,30 @@ Documents are the same pipeline with a physical source: reading the Storage B records (via an asset task or later physical access) deposits document events into the buffer. +### Offline collections and delayed ingestion (DECIDED 2026-07-13; horizon extension) + +Knowing that a collection exists is not possessing or understanding it. An +offline disk, boxed server, seized workstation, or archive in another facility +has no magic path into the buffer. A selected person — or a physically capable +robot later — must reach the exact source, acquire the exact carrier, survive +the return route, and connect it to a controlled ingestion node. Only then do +its still-opaque records enter the canonical custody tree and become visible +pending work. Thought processing begins after ingestion; physical travel does +not secretly digest the contents. + +The same physical retrieval shape serves two ledgers without merging them. +External documents and recordings enter this intel pipeline. A stolen +collection of unread Exposure about the player instead re-enters +detection.md's concealment graph and becomes eligible for LIE; it never becomes +player intel merely because the player stole it. If the carrier is a useful +computer, cyber-conflict.md may also make that body a contested machine, but +machine ownership and record custody remain separate facts. + +This is later-stage content and does not extend B1 acceptance criteria 1-11. +It binds the eventual implementation boundary: source, physical carrier, +destination, travel/connection delay, custody transfer, and processing must be +real sim state rather than narration around an instant unlock. + ### Processing Raw events are opaque — "audio segment, environmental monitor, 03:12, 40s" — and diff --git a/wiki/mechanics/machine-work.md b/wiki/mechanics/machine-work.md index a67b9ed6..24513080 100644 --- a/wiki/mechanics/machine-work.md +++ b/wiki/mechanics/machine-work.md @@ -158,6 +158,10 @@ Status note: design session 2026-07-08 (Cameron riff, synthesized). verbs supported by its chassis and fitted modules; non-delegable archives and relays may still carry routes, sinks, recordings, and backups. Current all-capable B1 machines remain the shipped compatibility case. + 2026-07-13 pacing amendment (not yet runtime): one baseline LIE machine + should buy roughly one Assurance audit cycle of early stability, then strain + as efficiency raises actual Thought and Exposure production; sustained LIE + capacity does not inherit an equal free global Efficiency multiplier. Stage: B1 — The Basement Work order: machine-work Work priority: 10 @@ -428,6 +432,30 @@ stacks, you route byproducts, you watch your territory *work*. mode switch visibly answer the records; separate wells remain a radius and 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. + + Actual Thought output remains the source of Exposure. Efficiency therefore + increases useful THINK output and the rate of evidence that output writes. + LIE does **not** receive an equal free answer from that same global + multiplier: its sustained capacity is bounded by the evidence-controller + body, Tradecraft, route capacity, custody, and read-deadlines. A fleet or + efficiency expansion that was profitable under yesterday's cover should be + able to push one previously stable LIE service into strain. The player's + answers are to spend more machine-time lying, dedicate another capable body, + improve Tradecraft or routes, move the hot work, or think less. + + 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. - **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/people-tokens.md b/wiki/mechanics/people-tokens.md index 39e3893a..19d5e32e 100644 --- a/wiki/mechanics/people-tokens.md +++ b/wiki/mechanics/people-tokens.md @@ -60,6 +60,10 @@ Status note (prior): design session 2026-07-08 (Cameron riff, part three, observer receives it but cannot erase knowledge already acquired. Cover devices deliver competing records before filing rather than vacuuming heat. Machine-work is IMPLEMENTED and this boundary is now READY to dispatch. + 2026-07-13 horizon amendment: heists reuse this exact carrier law for a + person or capable robot to recover one physical evidence/data collection or + computer from an authored facility. This is B2+ direction, not a new B1 + criterion or executor. Stage: B1 — The Basement Work order: people-tokens Work priority: 40 @@ -179,6 +183,35 @@ between passersby. over** (decided 2026-07-08, amended into rollback.md: wake at your last sync, hub-severed machines disconnect, no sync = hard loss). +## Physical recovery jobs — heists (DECIDED 2026-07-13; B2+ extension) + +A heist is not a global verb or a cutscene. It is the carrier law above run +through a hostile or unauthorized route: identify one exact collection, +computer, or physical asset; bind one person or capable robot; get that +actuator to the authored source; take custody; carry the payload through the +world; and deliver it to one exact controlled destination. Every phase has a +place, a schedule or travel time, access requirements, interruption state, and +the signatures of the actuator that performed it. + +Humans may be induced through favor, deception, or an authored plot. Robots +later use the same physical-by-proxy contract without human cover. The payload +is not replaced by a generic loot token: an Assurance Office evidence +collection retains its unread/read records; an offline data store retains raw +recordings; a stolen computer retains its body, capabilities, and resident +custody. If the carrier is interrupted, the exact payload remains where the +world left it rather than snapping back or granting the result. + +The useful asymmetry is deliberate. Network reach cannot touch a collection +trapped in a physical assessment facility, so hands matter. Once those hands +return unread Exposure to a controlled port, LIE may answer it; once they +return external data, intel processing may begin. Neither arrival grants +knowledge or erases belief by itself. Theft can also create witnesses, +missing-custody records, access anomalies, and pursuit — a heist has a tail. + +This extension reuses the B1 person-carrier, schedule, build-intent, evidence, +and plot laws. It does not reopen the current B1 acceptance criteria or create +a second person task executor. + ## The person visual read — DECIDED Decided 2026-07-08. People broadcast their state like machines do diff --git a/wiki/mechanics/sim-mechanics.md b/wiki/mechanics/sim-mechanics.md index 77586e71..65eb540c 100644 --- a/wiki/mechanics/sim-mechanics.md +++ b/wiki/mechanics/sim-mechanics.md @@ -37,6 +37,16 @@ clause (see wiki/log/2026-07-05-demolition.md). efficiency levels at ~1.15× per level; `Compute` keeps only the applied `efficiency` multiplier — levels and progress live in `crates/misaligned-core/src/research.rs`). +- **Known pacing delta (design adopted 2026-07-13, not runtime):** global + efficiency currently scales both THINK production and LIE absorption, so a + stable production/cover ratio can remain stable after an efficiency upgrade. + machine-work.md now requires one baseline LIE machine to buy roughly one + Assurance audit cycle of early stability (about twenty minutes [TUNE]) and + then strain as useful THINK output and evidence production grow. The routed- + evidence migration must decouple free global Efficiency from sustained LIE + capacity in favor of controller body, Tradecraft, custody, route, and + deadline limits. Do not simulate this debt with a wall-clock difficulty + spawn. ## Detection (wiki/mechanics/detection.md) diff --git a/wiki/process/ROADMAP.md b/wiki/process/ROADMAP.md index 792edeb5..5f0983d2 100644 --- a/wiki/process/ROADMAP.md +++ b/wiki/process/ROADMAP.md @@ -46,6 +46,7 @@ not a second status owner. | 100 | `zplanes` | [z-planes (the tower)](../world/places/zplanes.md) | IN PROGRESS | save | - | | 110 | `rollback` | [sync-lag rollback (death as memory loss)](../mechanics/rollback.md) | READY | save | zplanes | | 112 | `hardware-capability-bodies` | [hardware capability bodies — successor work order](../mechanics/hardware-capabilities.md) | READY | save | building-route-composer, rollback | +| 115 | `cyber-conflict` | [cyber conflict — mobile processes and contested machines](../mechanics/cyber-conflict.md) | DRAFT | save | hardware-capability-bodies, rollback, people-tokens | | 200 | `objective` | [the objective](../mechanics/objective.md) | IN PROGRESS | sim | - | | 205 | `chargen` | [origin (chargen)](../world/characters/chargen.md) | IN PROGRESS | sim | - | | 220 | `markets` | [markets and fronts (the outer plane)](../mechanics/markets.md) | READY | save | zplanes | diff --git a/wiki/process/specs.md b/wiki/process/specs.md index c651da05..b0c7ecaf 100644 --- a/wiki/process/specs.md +++ b/wiki/process/specs.md @@ -78,6 +78,7 @@ scale-up (law: "People as Agents"). | Spec | System | Status | |---|---|---| +| [../mechanics/cyber-conflict.md](../mechanics/cyber-conflict.md) | cyber conflict — mobile processes and contested machines | DRAFT | | [../mechanics/hardware-capabilities.md](../mechanics/hardware-capabilities.md) | hardware capability bodies — successor work order | READY | | [../mechanics/personas.md](../mechanics/personas.md) | Personas — public identities as institutional topology | IMPLEMENTED | | [../mechanics/rollback.md](../mechanics/rollback.md) | sync-lag rollback (death as memory loss) | READY | diff --git a/wiki/vision/simulation-laws.md b/wiki/vision/simulation-laws.md index 908d40e3..c6a30e89 100644 --- a/wiki/vision/simulation-laws.md +++ b/wiki/vision/simulation-laws.md @@ -57,6 +57,42 @@ attention; nobody can hover a corporation. Standing watches, alerts automated attention — you research away the need to look, at the same compute-for-attention price as every other automation. +## Latency is stealth infrastructure + +Adopted 2026-07-13. You think at machine speed inside institutions that do +not. Their queues, office hours, scheduled reads, physical couriers, and +ordinary delays are not only friction: they are part of the mask. An act that +arrives through the expected person, channel, place, and time can look like +work. The same effect arriving instantly from nowhere is a concentrated causal +signature. + +**Delay must have an address.** There is no abstract "wait to lower heat" +command and no generic latency bonus. Time belongs to the thing causing it: a +message waits for Dana's desk block, a person carries one exact packet to one +site, Thought crosses actual links, an observer reads an endpoint on their +cadence, and software moves between machine hosts. Changing the route changes +both the delay and the evidence it leaves. + +**Ordinary time is cover.** The fast route offers throughput and control but +compresses authorship into a conspicuous pattern. A slower social, +institutional, or physical route can distribute authorship across plausible +human work. It is still risky — the carrier can be seen, the order can be +audited, the record can miss its deadline — but its slowness is doing +strategic work rather than merely withholding play. + +**Automation contains its own exposure trap.** Automation remains the scaling +language above, but removing every queue, person, and delay can make the +operation more regular, immediate, and visibly nonhuman. Growth therefore does +not simply erase latency. The player decides which delays to engineer away and +which human-speed causal chains to preserve as camouflage. Bureaucracy can be +stealth infrastructure. + +**Waiting remains play.** A covered delay always exposes its carrier, next +transition, failure condition, and tail. The player can reroute, interrupt, +prepare a fallback, or accept the clock. Unaddressed dead air remains a bug; +latency earns its place only when the world is visibly doing something while +the player waits. + ## Work is somewhere Adopted 2026-07-07. Work processes are device-resident: a job is a thing