The framework in motion
Two real feature traces walked through the 6-floor stack. Pick a trace, scroll to advance, or press play. Floors light up as they fire, dim when they stay dormant.
Sprint I — 10 UI/DS token migrations
Low-risk mechanical work. Routed to a LITTLE core. Only 2 skills loaded.
- Floor 6v6.0 MeasurementInstrumentation overlay
- Floor 5v5.2 Dispatch IntelligenceParallel Write Safety
- Floor 4v5.1 Adaptive BatchThroughput primitives
- Floor 3v5.0 SoC-on-SoftwareReclaim context
- Floor 2Skills + CacheHub-and-spoke
- Floor 1Shared StateThe load-bearing slab
- Beat 1 of 7playing
Request arrives
Sprint I enters the framework: 10 mechanical UI/DS fixes queued from the audit backlog. Raw fonts, inline shadows, unmapped opacity literals.
- 10findings
- lowrisk
- Beat 2 of 7
Floor 1 — shared state read
audit-findings.json returns 10 unresolved UI/DS findings. feature-registry.json maps them to 6 views. design-system.json exposes the token API.
- Beat 3 of 7
Floor 5 — dispatch intelligence classifies
complexity_scoring: "mechanical token migration, low." task_complexity_gate routes to LITTLE core. tool_budgets allocates small Edit-heavy budget. No parallel dispatch needed.
- LITTLEcore
- serialdispatch
- Beat 4 of 7
Floor 3 — skills loaded on-demand
phase_skills["implement"] loads only `design` and `dev` SKILL.md. The other 9 skills stay dormant. compressed_view reads cache in palettized form.
- 2 / 11skills loaded
- ~27K tokcontext saved
- Beat 5 of 7
Floor 2 — cache tiers consulted
L1 cache returns the design/token map (AppText.displayXL = 36pt). L2 returns ux-foundations principles. L3 returns prior v2 migration patterns. cache-hits.json increments.
- Floor 2Floor 6— hits +3
- Beat 6 of 7
Floor 4 — systolic execution loop
Per finding: Grep → Read → Edit forwards results without reloading. 10 iterations in sequence. Floor 5 keeps a snapshot armed; rollback unnecessary, never fires.
- 10edits
- 0rollbacks
- Floor 4Floor 6— phase-timing tick
- Beat 7 of 7
Write-back & exit
audit-findings.json updated: 10 resolved. case-study-monitoring records phase transition. cache-metrics flushed. PR #97 opened and merged.
- 10 / 10findings resolved
- #97PR
How this works
Each trace is a beat-by-beat replay of a real feature that shipped through the framework. The floors mirror the static framework blueprint: Floor 1 is the shared state slab, Floors 2–5 are successive dispatch primitives, Floor 6 is the measurement overlay.
Floors marked firing are actively executing in that beat. Floors marked dormant were skipped entirely for this feature — which is the point: the framework selectively activates only what each task needs. Sprint I (mechanical) used 2 of 11 skills; the fitme-story build (UI-heavy) used 4 different ones.
The traces are pinned to the static methodology docs — click through for the full story.
A /pm-workflow dispatch travels through cache tiers and systolic chains on its way to commit — the trace above names each one as it fires. Hover any underlined term here or in case studies for a plain-language definition.