diff --git a/crates/misaligned-bevy/src/main.rs b/crates/misaligned-bevy/src/main.rs
index e42a409..ede4a58 100644
--- a/crates/misaligned-bevy/src/main.rs
+++ b/crates/misaligned-bevy/src/main.rs
@@ -8896,6 +8896,8 @@ mod operations_workspace_tests {
     #[test]
     fn workspace_rows_explain_and_dispatch_the_bound_commands() {
         let mut sim = scenario();
+        // Leverage remains an exact strategic choice under recursive custody;
+        // routine Schedule events correctly fold into bounded streams.
         sim.intel.push(misaligned::intel::ProcessedIntel {
             raw_id: 777,
             tick: 5,
@@ -8905,7 +8907,7 @@ mod operations_workspace_tests {
             x: 0,
             y: 0,
             person: Some(0),
-            kind: misaligned::intel::IntelKind::Schedule,
+            kind: misaligned::intel::IntelKind::Leverage(misaligned::person::Leverage::Debt),
         });
 
         // The blocked Moonlight start renders its exact reason.
diff --git a/wiki/interface/bevy-visual-floor.md b/wiki/interface/bevy-visual-floor.md
index 86caa28..ea95a46 100644
--- a/wiki/interface/bevy-visual-floor.md
+++ b/wiki/interface/bevy-visual-floor.md
@@ -174,6 +174,12 @@ remain (title, game-over, context-menu card, Operations) use the same
 amber/bone/crimson vocabulary as the main frame — dark translucent background,
 light border, padding, selected-row highlight, footer hints.
 
+Amended 2026-07-14: Bevy parity fixtures must respect the current semantic
+projection. An exact-target dispatch test uses evidence that remains an exact
+strategic choice (for example leverage); routine sightings and schedules that
+the Intel custody tree intentionally aggregates cannot stand in for an exact
+sale target merely to preserve an obsolete test shape.
+
 ### Color and typography
 
 The terminal palette's meanings bind here too: bone/chrome/gunmetal for data
diff --git a/wiki/interface/operations-workspace.md b/wiki/interface/operations-workspace.md
index 97721de..fe9a0c9 100644
--- a/wiki/interface/operations-workspace.md
+++ b/wiki/interface/operations-workspace.md
@@ -40,7 +40,9 @@ Status note: The initial renderer-neutral workspace landed 2026-07-12. One
   object and decision type, and gives 32% to the exception-first object list
   while preserving the shared semantic order and every existing input/state
   boundary. This presentation-only pass does not alter the implemented
-  recursive-Intel behavior or status.
+  recursive-Intel behavior or status. Its bound-sale parity fixture uses an
+  exact leverage holding; a routine schedule event correctly belongs to the
+  bounded custody stream and cannot stand in for an exact sale target.
 Stage: B1 — The Basement
 Work order: operations-workspace
 Work priority: 28