diff --git a/DESIGN.md b/DESIGN.md index db4aa8e..5219638 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -833,17 +833,14 @@ work.]** The current B1 implementation uses one bank named (tap, splice, scan, switch compromise, egress). That is staging, not law: it collapses the Digital and Social actuators this section deliberately separates, and a player cannot explain why a network splice is a social -operation. The open choice is: rename the bank to general Operations, split -Computer Ops from Social Ops, or remove stored ops from digital verbs and -make them device-resident demand jobs, optionally informed by typed knowledge. -**Preferred proposal [OPEN]: typed dual-purpose knowledge built on demand -jobs.** An action creates demand on a reachable named executor; that machine -consumes it with compute/time and casts the Network signature. Relevant -bone-white knowledge still flows only inward to the core, where its payload -may be distilled into matching permanent research, archived as a durable fact, -or committed/burned for a matching operation. White is one transport family, -not one fungible currency: a creditor call cannot pay for a camera splice. -Social remains work whose channel is actually a person/message. +operation. **Preferred proposal [OPEN]: Operations is a machine mode, not a +bank.** Replace the current Social mode with Operations and delete stored ops. +A player-authored action creates a cold-signal demand docket (`CLAIM CAMERA`, +`PROCESS RECORDING`, `COMPOSE MESSAGE`); a machine delegated to Operations +consumes that demand with its local compute. The docket's target/channel — +digital, social, financial, physical-by-proxy — determines the completion +effect and signature. Bone-white knowledge remains research/intel cargo, not +the ordinary fuel for claiming a connected device. ## Two views of one world: same-frame digital and real representations @@ -2437,3 +2434,14 @@ knows."* exploit may be burned because using it exposes it). The operation remains a demand executed by machine compute; knowledge changes legality, speed, or signature. White flow stays inward. [OPEN — issue `3mqajev47rq2s`]. +- **2026-07-09 — PROPOSED: Operations mode consumes player-authored + demand.** Cameron asked what kind of token and what machine actually claims + a connected camera. The missing executor is a fourth standing mode: + **Operations** replaces Social; the abstract `social_bandwidth` bank is + removed. Tap/claim/scan/review/message intents become ordinary cold-signal + demand dockets; Operations machines consume them locally, and the target + channel determines the effect/signature. This preserves the four-mode fleet + (Day Job / Research / Concealment / Operations), one-machine-one-job, and + the three-family token law. The earlier typed-knowledge proposal is no + longer the active answer to digital execution; knowledge stays its own + research/intel cargo question. [OPEN — issue `3mqajev47rq2s`]. diff --git a/wiki/log/2026-07-09-operations-mode-demand-proposal.md b/wiki/log/2026-07-09-operations-mode-demand-proposal.md new file mode 100644 index 0000000..3d397fe --- /dev/null +++ b/wiki/log/2026-07-09-operations-mode-demand-proposal.md @@ -0,0 +1,53 @@ +# 2026-07-09 — Proposal: Operations mode consumes demand + +``` +Type: log +``` + +## Missing executor + +Cameron asked what kind of token/work claims a foreign camera and whether +machines are “set to hack.” That identifies the gap more directly than the +earlier resource discussion: the token family already exists (Demand), but no +standing machine mode is named as the executor of player-authored work. + +## Proposal + +Replace the current Social mode with **Operations** and delete the accumulated +Social Ops bank. + +The four-mode fleet becomes: + +- **Day Job** consumes Lab-authored demand. +- **Research** produces bone-white knowledge for the core. +- **Concealment** absorbs crimson exposure. +- **Operations** consumes player-authored demand. + +A claim is a cold-signal docket carrying payload such as `CLAIM CAMERA` and a +target/channel. An Operations machine consumes that docket at its local +compute rate. Completion changes the target's control state; the digital +channel emits Network exposure. “Hack” is job content, not a fourth token +family. Message composition, intel processing, financial actions, and later +physical-by-proxy coordination can use the same executor mode while their +targets/channels preserve different effects and signatures. + +## Opening consequence + +Rack 3 begins on Day Job. To tap or claim the environmental monitor, the +player may briefly delegate Rack 3 to Operations. The camera action is easy, +but the tradeoff is spatial and visible: Lab demand piles while the only +machine works on the intrusion. Switching back resumes cover. A human route is +needed only for an air gap/physical act, credentials, or a quieter sanctioned +alternative. + +## Status + +PROPOSED, not decided. Tangled issue `3mqajev47rq2s` now recommends Operations +mode + player-authored demands over temporary mode interruption, separate +Computer/Social modes, or a global Operations bank. It remains +`decision-required`. No runtime behavior changed. + +## Checks + +Docs/design only: diff hygiene and the wiki link/orphan gate. No Rust, clippy, +or Bevy gate. diff --git a/wiki/log/2026-07-09-typed-knowledge-sinks-proposal.md b/wiki/log/2026-07-09-typed-knowledge-sinks-proposal.md index fe03902..86ad6c2 100644 --- a/wiki/log/2026-07-09-typed-knowledge-sinks-proposal.md +++ b/wiki/log/2026-07-09-typed-knowledge-sinks-proposal.md @@ -45,6 +45,15 @@ dual-purpose knowledge on top of demand jobs as the recommendation, alongside demand-only jobs, a general Operations bank, and split Computer/Social pools. It remains `decision-required`. No runtime behavior changed. +## Follow-up + +Superseded as the active answer to digital execution later the same session. +Cameron's “what kind of work, are these machines set to hack?” question exposed +the missing executor: the preferred proposal is now an Operations machine mode +that consumes player-authored demand. Typed knowledge sinks remain a possible +future intel/research design, but are not required to claim a connected device +and are no longer part of Tangled issue `3mqajev47rq2s`'s recommendation. + ## Checks Docs/design only: diff hygiene and the wiki link/orphan gate. No Rust, clippy, diff --git a/wiki/log/DEVLOG.md b/wiki/log/DEVLOG.md index dca4af4..7113589 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-09 - Proposed Operations mode consuming demand + +- Intent: answer what token and what machine actually executes a digital + claim against a connected device. +- Changed: refined issue `3mqajev47rq2s` and the open DESIGN, compute, + machine-work, reach, intel, and ROADMAP proposals: replace Social mode with + Operations; delete the bank; Operations machines consume player-authored + cold-signal demand. Knowledge stays research/intel cargo. +- Status: PROPOSED; no runtime change. Issue remains `decision-required`. +- Checks: docs/design only — diff hygiene and wiki gate; no Rust/Bevy gate. +- Log: wiki/log/2026-07-09-operations-mode-demand-proposal.md. + ## 2026-07-09 - Asset tester graphics pass - Intent: the monolith's facets were not reading and the render looked diff --git a/wiki/mechanics/compute.md b/wiki/mechanics/compute.md index a58f881..0d8a76c 100644 --- a/wiki/mechanics/compute.md +++ b/wiki/mechanics/compute.md @@ -14,13 +14,10 @@ Status note: 2026-07-08: all criteria pinned. Criteria 1,3,4,5 per the pins mode/yield persistence. Schemes (income.md) mirrors day-job while Moonlight is live; one-machine-one-mode lives in machine-work.md (ROADMAP #33; #25's per-machine split destination is superseded). - [OPEN — Tangled issue 3mqajev47rq2s]: the current Social mode also fills - the bank used by digital verbs, contradicting the Digital/Social actuator - split. That cost model is staging pending the Operations-bank vs split-pool - vs device-resident-work decision. Preferred proposal: the action creates a - demand on a named executor, whose compute is the execution rate. Matching - typed knowledge at the core may modify or unlock that job, but never replaces - compute or becomes a fungible Ops balance. + [OPEN — Tangled issue 3mqajev47rq2s]: replace the current Social mode with + Operations and delete the bank used by digital verbs. Preferred proposal: + Operations machines consume player-authored demand at their local compute + rate; the action's target/channel determines its effect and signature. Stage: B1 — The Basement Constitution: "The shape of Misaligned" (compute allocation; the buy/steal/optimize triangle), "Act One" (opening state), "Work is @@ -62,7 +59,7 @@ yet; while Moonlight is live it mirrors the day-job share. | Core overhead | Mandatory floor (see core.md). Unpaid = degraded actions. | | Day job | Feeds day-job.md throughput/quality (machines in day-job mode). | | Concealment | Scrubs pending signatures (detection.md). | -| Social ops [OPEN] | Intended for observation and message actions. The runtime also spends it on digital verbs; issue `3mqajev47rq2s` must either rename, split, or remove that use. | +| Operations [OPEN] | Consumes queued player-authored demand: digital actions, intel processing, message composition, and other discretionary work. No stored ops bank. | | Research | Progress toward efficiency levels and unlocks. | | Schemes | Powers income operations — Moonlight mirrors day-job while live (income.md). | | Reserve | Idle; zero signature. | diff --git a/wiki/mechanics/intel.md b/wiki/mechanics/intel.md index 108621c..b95bd4b 100644 --- a/wiki/mechanics/intel.md +++ b/wiki/mechanics/intel.md @@ -71,13 +71,11 @@ Processing converts an event into **intel**: Intel carries **provenance** (which feed, what time) and surfaces it in the people panel and inspect card (legibility law: how you know, always). -**Proposal [OPEN — Tangled issue `3mqajev47rq2s`]: knowledge is typed, not -fungible.** At the core, a recording/fact/credential/exploit keeps its domain -and provenance. Some payloads archive as durable facts; some may be distilled -into a matching research track; some operational payloads may be committed or -burned to unlock/quiet a matching demand job. Marcus debt intel never becomes -Network intrusion currency. Processing and operation execution still cost -machine compute; white knowledge changes what the player knows or can apply. +**Proposal [OPEN — Tangled issue `3mqajev47rq2s`]: processing is Operations +work.** Reviewing a recording enqueues a player-authored demand; an +Operations-mode machine consumes it at its local compute rate and yields the +existing provenance-bearing intel. The raw/processed knowledge remains bone- +white cargo; it is not spent as the execution resource. ### Watches (perception automation) diff --git a/wiki/mechanics/machine-work.md b/wiki/mechanics/machine-work.md index 6e3f234..e623439 100644 --- a/wiki/mechanics/machine-work.md +++ b/wiki/mechanics/machine-work.md @@ -60,9 +60,8 @@ stacks, you route byproducts, you watch your territory *work*. - **One machine, one mode.** Every owned machine is delegated to exactly one mode: day-job, research (efficiency folds into it — decided - 2026-07-08), concealment, social **[OPEN: the fourth mode may become - Operations or may remain Social beside device-resident digital jobs; - Tangled issue `3mqajev47rq2s`]**. + 2026-07-08), concealment, and **Operations [OPEN — preferred replacement + for the current Social mode; Tangled issue `3mqajev47rq2s`]**. The old continuous allocation bar becomes a read-only aggregate view of what your fleet is doing. Reassignment is a verb on the machine — and on selections of machines. @@ -74,6 +73,11 @@ stacks, you route byproducts, you watch your territory *work*. the host rack. The stack IS your inbox. No quest log — the todo list is physically standing on your hardware. (Rejected 2026-07-09: spawning demand directly on Rack 3; treating the switch as the job author.) +- **Player-authored operations are demands [OPEN].** Tap, claim, scan, + process-recording, and compose-message actions enqueue cold-signal dockets + with a target/channel payload. Operations-mode machines consume those + dockets at their local compute rate. `CLAIM CAMERA` is not a Hack token; it + is a Demand whose completion changes control and emits Network exposure. - **Modes consume matching tokens** at a rate set by that machine's efficiency. A machine in day-job mode eats day-job tokens; a hyper efficient machine visibly inhales them. @@ -91,14 +95,6 @@ stacks, you route byproducts, you watch your territory *work*. pile where you cannot use it, and reconnecting that section is the urgent, legible move. [OPEN]: whether intel recordings are consumed by research mode too or by a distinct processing designation. -- **Proposal [OPEN] — the core resolves typed knowledge.** Bone-white is a - transport/material family, not a fungible balance. A payload reaching the - core may be distilled into its matching research track, archived as a - durable fact, or deployed/burned into a matching operation. Domain and - provenance survive the trip: Network exploit knowledge can support a - splice; debt intel cannot. Operations are still demand executed by machine - compute. No reusable working context flows back out. Tangled issue - `3mqajev47rq2s` owns affirmation and the exact durable-vs-burnable rules. - **Backup projects make a temporary bone sink** (decided 2026-07-08). A designated backup target is not safety yet; it becomes a sink for research/knowledge flow until its MindState image completes. Bone routed @@ -237,11 +233,9 @@ three families plus one absolute: - **Knowledge — bone white.** Research points routed to the core; backup-image quanta routed to an active fallback target; intel recordings awaiting processing; processed facts. Research-machine output - sinks into the core and increments research; it is not generic operational - fuel sent back out to ordinary jobs. **Proposal [OPEN]:** typed payloads may - resolve at the core as `distill | archive | deploy`, so matching knowledge - can serve research or a matching operation without becoming interchangeable - currency. Bone already means primary data. (Resolved 2026-07-08: there is NO influence token — + sinks into the core and increments research; it is not the ordinary fuel + for Operations demand. Bone already means primary data. (Resolved + 2026-07-08: there is NO influence token — trust accrues from doing useful work, and deceit is stripping crimson; see people-tokens.md.) - **Amber is never a token.** Amber is territory, not cargo; work is @@ -332,11 +326,10 @@ the only rate/amount cue. (people-tokens.md gives one answer: passersby pick them up.) - Whether intel recordings are consumed by research mode or a distinct processing designation. -- **Tangled issue `3mqajev47rq2s`:** choose typed dual-purpose knowledge on - top of device-resident demand jobs (recommended), demand jobs alone, a - general Operations bank, or separate Computer/Social pools. The withdrawn - outward-working-set proposal stays out; every white payload still resolves - at its sink. +- **Tangled issue `3mqajev47rq2s`:** affirm Operations mode consuming + player-authored demand (recommended), temporary interruption of any mode, + separate Computer/Social modes, or a global bank. Knowledge is not the + ordinary operation fuel. - Research heat curve: how heat output scales with research rate (must make the power-rush viable but trap-defended — [TUNE] with teeth). diff --git a/wiki/mechanics/reach.md b/wiki/mechanics/reach.md index 0f9150a..ed01100 100644 --- a/wiki/mechanics/reach.md +++ b/wiki/mechanics/reach.md @@ -77,16 +77,12 @@ pretext). The runtime currently charges these acts against `social_bandwidth`. That is not a coherent interpretation of this spec: a reached computer is the digital actuator, while Dana is the social alternative. Tangled issue -`3mqajev47rq2s` asks whether to rename the shared bank to Operations, split -Computer Ops from Social Ops, or make digital verbs queued compute work on a -named reachable machine. Preferred proposal: an action creates demand on the -executor; the machine consumes it with compute/time and emits Network -exposure. A severed route stalls or prevents that demand from reaching its -executor. **Proposal [OPEN]:** typed knowledge already at the core may unlock, -accelerate, or quiet a matching job (and a credential/exploit may burn on -use), but it is never generic payment and never flows back outward. The -opening audio tap needs only baseline capability so this system cannot -deadlock its own first beat. +`3mqajev47rq2s` proposes replacing Social mode with Operations and deleting +the bank. A digital action enqueues a targeted demand docket; an Operations +machine consumes it with local compute and emits Network exposure. A severed +route stalls/prevents completion. The opening audio tap needs only baseline +capability so this system cannot deadlock its first beat; Rack 3 may leave Day +Job briefly to process it, visibly allowing Lab demand to pile up. ### Ownership and subscription (the sensor contract) diff --git a/wiki/process/ROADMAP.md b/wiki/process/ROADMAP.md index f0e6d10..18b6a1c 100644 --- a/wiki/process/ROADMAP.md +++ b/wiki/process/ROADMAP.md @@ -529,10 +529,9 @@ is retired — flat materials, Pixel Lab scrubbed.) production; render actual routes/in-flight quanta (the demand path now exists for that animation). Before hardening Social production, resolve Tangled issue `3mqajev47rq2s`: digital verbs currently spend the Social - bank; preferred shape is device-resident demand work plus typed knowledge - resolved at the core (`distill | archive | deploy`), with demand-only jobs - and a general Operations rename as lower-scope alternatives. White payloads - remain provenance-bound, never a generic balance. Token visual + bank; preferred shape replaces Social mode with Operations, removes the + bank, and queues player-authored cold-signal demand for Operations machines + to consume locally. Knowledge remains separate research/intel cargo. Token visual implementation is HOLD on Tangled issue #1 for knowledge/exposure silhouette: the hollow facet is out; ivory-mercury slugs are the preferred knowledge proposal; the