Patterns · film scene 06
Command bar
One intent becomes the right instrument. One approved scope survives every shape.
The command field grows into a stock forecast, scheduler timer, revenue comparison, change history or reconciliation plan. Read-only questions produce views. A write needs a current version-bound approval. The reconciliation surface reports each target, waits for read-back and returns to its order with a scoped checkmark.
Interactive fixture, not a connected account. Compare with film scene 06. Play and direct manipulation share the same controls and state transitions.
What to try
Open with ⌘K on macOS or Ctrl K elsewhere, or use the field. Type an example intent or choose a chip. Pin a result, pause new Shopify runs for 30 seconds, and keep typing while its countdown continues. Review the reconciliation and Apply. Try losing the mapping acknowledgment, inspect the unknown result and read it back instead of retrying. The stale-version fixture demonstrates an approval being refused. Escape closes or folds the surface.
The contract it holds
| Rule IDs | What remains true |
|---|---|
INV-01, INV-13, INV-19, INV-20 | The forecast is a labeled scenario, not observed inventory. Revenue compares matched periods with the same currency and basis. The plan writes net to net while preserving gross. A typed intent is never an authority grant. |
INV-02, INV-03, INV-04, INV-05, INV-06, INV-11 | Apply revalidates the displayed version. Each target reports its own Applied or unknown outcome. Read-back checks changed and preserved fields and names unobservable scope. Scheduler stop requests, acknowledgments, expiration and resumption are separate states. |
INV-07, INV-09, INV-16; MOT-01, MOT-05, MOT-08, MOT-09, MOT-11, MOT-12 | The same Shapeshift becomes a row badge. The input node persists through result and timer updates. ⌘K is immediate. Unknown outcomes stay still. Pin flights use transforms. A focused result waits for the person to leave or explicitly fold it rather than stealing focus. |
What differs from the film, and why
The film turns writes directly into Done and Synced, and resumes a separate paused sync as part of reconciliation. Lyotic keeps Applied separate from read-back, never resumes the separate pause through an unrelated approval, and distinguishes a forecast from source evidence. Read-only result pins keep their snapshot time; the timer pin retains live scheduler state. Playback can fold after its hand leaves the result; a keyboard user’s focused result does not disappear merely because a background read-back arrived.
Implementation and limits
Uses the existing Shapeshift rather than reproducing the engine. The persistent form, per-target result elements and time-based countdown are scene-owned content. Intent parsing is a small deterministic router for the shown fixtures, not a language-model service. No ERP, marketplace, bank or external scheduler is connected. The plan and DOM inspector does not substitute for testing real adapters or assistive technology.
Form adapts. Meaning persists. Walk the full inventory-mapping case, or read the model and rule IDs.