diff --git a/DESIGN.md b/DESIGN.md
index 44730919..d2cafc9a 100644
--- a/DESIGN.md
+++ b/DESIGN.md
@@ -835,9 +835,13 @@ 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 compute jobs. The preferred proposal is the last:
-a reachable named computer performs the work over time and casts the Network
-signature; Social remains work whose channel is actually a person/message.
+make them device-resident compute jobs. **Preferred proposal [OPEN]:
+knowledge-fed work.** An action creates a demand; the core routes a
+bone-white working set to a reachable named computer; that machine spends
+compute/time and casts the Network signature. The knowledge is reserved and
+released, not burned like mana. In one sentence: **demand + knowledge +
+compute -> completed work + exposure.** Social remains work whose channel is
+actually a person/message.
 
 ## Two views of one world: same-frame digital and real representations
 
@@ -2403,3 +2407,13 @@ knows."*
   LEDs, claim ring, core light) and is never a chassis fill. Amended into
   wiki/interface/computer-visual-language.md; the monolith chassis is built
   in the asset tester ahead of game adoption (ROADMAP #32).
+- **2026-07-09 — PROPOSED: white knowledge feeds work.** Cameron proposed
+  routing bone-white knowledge from the core to machines that need work. This
+  sharpens the preferred resolution of the digital/social ops contradiction:
+  a demand says what to do, a reserved working set says how, machine compute
+  sets the rate, and crimson exposure is the consequence. Knowledge is not
+  consumed; active quanta are occupied until completion and then released.
+  This makes bone flow outward as the visible reach of cognition, while raw
+  research/intel still flows inward to become capability. [OPEN — Tangled
+  issue `3mqajev47rq2s`]: affirm this knowledge-fed job model or choose the
+  smaller Operations-bank / split-pool alternatives.
diff --git a/wiki/log/2026-07-09-knowledge-fed-work-proposal.md b/wiki/log/2026-07-09-knowledge-fed-work-proposal.md
new file mode 100644
index 00000000..5c24f7f2
--- /dev/null
+++ b/wiki/log/2026-07-09-knowledge-fed-work-proposal.md
@@ -0,0 +1,56 @@
+# 2026-07-09 — Proposal: white knowledge feeds work
+
+```
+Type: log
+```
+
+## Riff
+
+Cameron proposed using white knowledge to flow to machines that need work,
+instead of inventing “computer ops” to replace the incoherent Social-funded
+splice cost.
+
+## Synthesis
+
+The proposal closes the three-family token loop:
+
+```text
+demand + knowledge + compute -> completed work + exposure
+```
+
+- A cold-signal demand says **what** needs doing.
+- Bone-white knowledge is the active working context that says **how**.
+- The named machine's compute determines execution rate.
+- Crimson exposure is the physical consequence of doing the work.
+
+This makes white flow the visible reach of the AI's cognition. Raw research
+and intel still travel inward to the core and become capability; active
+working knowledge travels outward from the core to a machine with demand.
+Direction gives one material two legible roles without adding a fourth token
+family.
+
+## Guardrail and tension
+
+Knowledge must not become mana. Learned capability is not destroyed when a
+splice completes. The preferred mechanical reading is a **conserved working-
+set reservation**: a job occupies bone quanta, routes them to its executor,
+and releases them on completion. A broken route stalls the job and strands
+that active capacity until reconnection; it does not erase what the AI knows.
+
+Free copying is simpler but risks making the white flow decorative. Literal
+consumption makes knowledge feel like fuel and contradicts persistent
+learning. Reservation creates a real concurrency/topology constraint between
+those failures.
+
+## Status
+
+PROPOSED, not decided. Tangled issue `3mqajev47rq2s` was updated so
+knowledge-fed device work is option 3 and the recommendation. The first scope
+would replace digital tap/splice/scan/egress costs; generalizing the knowledge
+prerequisite to every machine mode waits for an observed opening playtest.
+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/DEVLOG.md b/wiki/log/DEVLOG.md
index 977daa7e..b9db171c 100644
--- a/wiki/log/DEVLOG.md
+++ b/wiki/log/DEVLOG.md
@@ -5,6 +5,19 @@ Type: log
 ```
 Reverse chronological implementation notes. Keep this factual: what changed, why, checks, and spec impact.
 
+## 2026-07-09 - Proposed white knowledge as working context
+
+- Intent: explore Cameron's proposal that bone-white knowledge flow to
+  machines that need work, resolving digital actions through the existing
+  token law rather than a new Computer Ops currency.
+- Changed: refined Tangled issue `3mqajev47rq2s` and the open DESIGN,
+  machine-work, reach, compute, and ROADMAP markers around `demand + knowledge
+  + compute -> completed work + exposure`; proposed conserved working-set
+  reservations, not consumed knowledge or free decorative copies.
+- Status: PROPOSED; no runtime change. Start with digital jobs if affirmed.
+- Checks: docs/design only — diff hygiene and wiki gate; no Rust/Bevy gate.
+- Log: wiki/log/2026-07-09-knowledge-fed-work-proposal.md.
+
 ## 2026-07-09 - The monolith rack: ownership albedo + mode strip
 
 - Intent: Cameron directed the racks to the identity plate's monolith —
diff --git a/wiki/mechanics/compute.md b/wiki/mechanics/compute.md
index 86a7d265..a452de9a 100644
--- a/wiki/mechanics/compute.md
+++ b/wiki/mechanics/compute.md
@@ -17,7 +17,9 @@ Status note: 2026-07-08: all criteria pinned. Criteria 1,3,4,5 per the
   [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.
+  vs device-resident-work decision. Preferred proposal: device work starts
+  only after a reserved bone-white working set reaches its machine; compute is
+  the execution rate and knowledge releases on completion.
 Stage: B1 — The Basement
 Constitution: "The shape of Misaligned" (compute allocation; the
   buy/steal/optimize triangle), "Act One" (opening state), "Work is
diff --git a/wiki/mechanics/machine-work.md b/wiki/mechanics/machine-work.md
index e4894060..6c7cf88e 100644
--- a/wiki/mechanics/machine-work.md
+++ b/wiki/mechanics/machine-work.md
@@ -91,6 +91,16 @@ 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 also dispatches working knowledge.** Raw
+  research/intel still flows inward to become capability; active work sends a
+  temporary bone-white working set outward to the machine carrying the
+  demand. A job reserves that knowledge rather than consuming it, waits for
+  the white flow to arrive, spends machine compute over time, produces
+  exposure, then releases the working set. This gives all three families one
+  sentence: `demand + knowledge + compute -> completed work + exposure`.
+  Tangled issue `3mqajev47rq2s` owns affirmation. Start with digital verbs;
+  generalizing the prerequisite to every mode waits on an observed opening
+  playtest.
 - **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
@@ -228,7 +238,10 @@ three families plus one absolute:
   is a correct alarm wherever it stands.
 - **Knowledge — bone white.** Research points routed to the core;
   backup-image quanta routed to an active fallback target; intel
-  recordings awaiting processing; processed facts. Bone already means
+  recordings awaiting processing; processed facts. **Proposal [OPEN]:** the
+  same family carries reserved working context outward from the core to a
+  machine with demand. Direction distinguishes learning (inward) from acting
+  (outward); the working set is released, not destroyed. 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.)
@@ -320,6 +333,11 @@ 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`:** affirm knowledge-fed work (recommended),
+  a general Operations bank, or separate Computer/Social pools. If
+  knowledge-fed work wins, specify whether working-set quanta are strictly
+  conserved reservations or cheap temporary copies; recommendation:
+  reservation, because free copies make the white flow decorative.
 - 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 94e850bd..7f92e9b7 100644
--- a/wiki/mechanics/reach.md
+++ b/wiki/mechanics/reach.md
@@ -79,8 +79,11 @@ 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: queued device-resident work, so
-duration/compute and Network signature both follow the actual actuator.
+named reachable machine. Preferred proposal: an action creates a demand and
+reserves bone-white working knowledge at the core; that context routes to the
+executor, which spends compute/time and emits Network exposure. Completion
+releases the knowledge. A severed route stalls the job and strands the active
+working set until reconnection; it does not erase learned capability.
 
 ### Ownership and subscription (the sensor contract)
 
diff --git a/wiki/process/ROADMAP.md b/wiki/process/ROADMAP.md
index a1fe0661..63b29ae7 100644
--- a/wiki/process/ROADMAP.md
+++ b/wiki/process/ROADMAP.md
@@ -529,8 +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 compute work, with a general
-  Operations rename as the lower-scope alternative. Token visual
+  bank; preferred shape is knowledge-fed device work (`demand + reserved
+  knowledge + compute -> completion + exposure`), with a general Operations
+  rename as the lower-scope alternative. 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