diff --git a/DESIGN.md b/DESIGN.md
index d2cafc9..376929a 100644
--- a/DESIGN.md
+++ b/DESIGN.md
@@ -835,13 +835,12 @@ 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. **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.
+make them device-resident demand jobs. The preferred proposal is the last:
+an action creates demand on a reachable named executor; that machine consumes
+the demand with compute/time and casts the Network signature. In one sentence:
+**demand + compute -> completed work + exposure.** Bone-white knowledge keeps
+its existing meaning: research output sinks into the core to increment
+research. Social remains work whose channel is actually a person/message.
 
 ## Two views of one world: same-frame digital and real representations
 
@@ -2417,3 +2416,12 @@ knows."*
   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.
+- **2026-07-09 — White-working-set proposal withdrawn.** Cameron caught the
+  conflict immediately: bone-white knowledge already has a decided direction
+  and sink — research machines produce it, it flows into the core, and it
+  increments research. The outward reserved-context synthesis silently gave
+  knowledge a second meaning and is withdrawn unless that existing law is
+  deliberately reopened. The active recommendation for issue
+  `3mqajev47rq2s` is now simpler: digital actions create demand on a named
+  executor; machine compute consumes it over time; exposure is the
+  consequence. Knowledge remains research cargo.
diff --git a/wiki/log/2026-07-09-knowledge-core-sink-correction.md b/wiki/log/2026-07-09-knowledge-core-sink-correction.md
new file mode 100644
index 0000000..fccb0e6
--- /dev/null
+++ b/wiki/log/2026-07-09-knowledge-core-sink-correction.md
@@ -0,0 +1,40 @@
+# 2026-07-09 — Knowledge keeps its core sink
+
+```
+Type: log
+```
+
+## Correction
+
+Cameron pointed out that bone-white knowledge already has a decided mechanic:
+research machines produce it, it flows into the core, and sinking it advances
+research. The preceding working-set proposal was therefore not an elaboration
+of current knowledge; it proposed a second, opposite flow and a new reusable
+resource without naming that redesign.
+
+That overreach is withdrawn. Knowledge remains research cargo with the core as
+its sink.
+
+## Active proposal for digital work
+
+The digital/social ops contradiction can be resolved without touching
+knowledge:
+
+```text
+demand + compute -> completed work + exposure
+```
+
+A tap, splice, scan, compromise, or egress action creates a demand docket on a
+named reachable executor. The machine consumes that demand over time at its
+compute rate and produces Network/physical exposure according to the existing
+actuator rules. A missing or severed route prevents/stalls the demand. Social
+stays attached to people and messages; bone knowledge continues flowing into
+the core.
+
+Tangled issue `3mqajev47rq2s` now carries this corrected option and 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-knowledge-fed-work-proposal.md b/wiki/log/2026-07-09-knowledge-fed-work-proposal.md
index 5c24f7f..2f782f0 100644
--- a/wiki/log/2026-07-09-knowledge-fed-work-proposal.md
+++ b/wiki/log/2026-07-09-knowledge-fed-work-proposal.md
@@ -50,6 +50,15 @@ 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.
 
+## Correction
+
+Withdrawn later the same session. Cameron noted that knowledge already sinks
+into the core to increment research. The synthesis above gave it an
+unapproved second outward role. The active recommendation now keeps knowledge
+unchanged and models digital actions as demand consumed by a named executor's
+compute, producing exposure. See
+[the correction log](2026-07-09-knowledge-core-sink-correction.md).
+
 ## 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 b9db171..336f3ac 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 - Knowledge core-sink correction
+
+- Intent: answer whether the white-working-set synthesis changed knowledge;
+  it did, unintentionally.
+- Changed: withdrew outward working knowledge from the active proposal;
+  restored knowledge's decided research-machine -> core sink; corrected
+  Tangled issue `3mqajev47rq2s`, DESIGN, compute, reach, machine-work, and
+  ROADMAP to recommend device-resident demand jobs instead.
+- Status: PROPOSED digital-job model remains open; no runtime change.
+- Checks: docs/design only — diff hygiene and wiki gate; no Rust/Bevy gate.
+- Log: wiki/log/2026-07-09-knowledge-core-sink-correction.md.
+
 ## 2026-07-09 - Proposed white knowledge as working context
 
 - Intent: explore Cameron's proposal that bone-white knowledge flow to
diff --git a/wiki/mechanics/compute.md b/wiki/mechanics/compute.md
index a452de9..93e6b7a 100644
--- a/wiki/mechanics/compute.md
+++ b/wiki/mechanics/compute.md
@@ -17,9 +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. 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.
+  vs device-resident-work decision. Preferred proposal: the action creates a
+  demand on a named executor, whose compute is the execution rate. Knowledge
+  remains research output that sinks into the core.
 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 6c7cf88..1d627ac 100644
--- a/wiki/mechanics/machine-work.md
+++ b/wiki/mechanics/machine-work.md
@@ -91,16 +91,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 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
@@ -238,11 +228,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. **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 —
+  recordings awaiting processing; processed facts. Research-machine output
+  sinks into the core and increments research; it is not operational fuel
+  sent back out to ordinary jobs. 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
@@ -333,11 +322,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`:** 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.
+- **Tangled issue `3mqajev47rq2s`:** choose device-resident demand jobs
+  (recommended), a general Operations bank, or separate Computer/Social
+  pools. The withdrawn knowledge-fed-work proposal does not alter the decided
+  core sink.
 - 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 7f92e9b..ab19466 100644
--- a/wiki/mechanics/reach.md
+++ b/wiki/mechanics/reach.md
@@ -79,11 +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: 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.
+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. Bone-white knowledge is not part of this cost: it remains research
+output routed into the core.
 
 ### Ownership and subscription (the sensor contract)
 
diff --git a/wiki/process/ROADMAP.md b/wiki/process/ROADMAP.md
index 63b29ae..7521635 100644
--- a/wiki/process/ROADMAP.md
+++ b/wiki/process/ROADMAP.md
@@ -529,9 +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 knowledge-fed device work (`demand + reserved
-  knowledge + compute -> completion + exposure`), with a general Operations
-  rename as the lower-scope alternative. Token visual
+  bank; preferred shape is device-resident demand work (`demand + compute ->
+  completion + exposure`), with a general Operations rename as the lower-
+  scope alternative. Knowledge keeps its decided core-sink role. 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