The framework
Six floors. Hover to explore how each layer contributes.
- Floor 6v6.0 MeasurementInstrumentation overlay
- phase-timing.json
- cache-hits.json
- CU v2
- rolling baselines
- Floor 5v5.2 Dispatch IntelligenceParallel Write Safety
- complexity_scoring
- model_routing
- tool_budgets
- mirror_pattern
- snapshot/rollback
- Floor 4v5.1 Adaptive BatchThroughput primitives
- batch_dispatch
- result_forwarding
- model_tiering
- speculative_preload
- systolic_chains
- task_complexity_gate
- Floor 3v5.0 SoC-on-SoftwareReclaim context
- phase_skills (skill-on-demand)
- compressed_view (cache compression)
- Floor 2Skills + CacheHub-and-spoke
- pm-workflow/SKILL.md
- .claude/cache/ L1/L2/L3
- Floor 1Shared StateThe load-bearing slab
- audit-findings.json
- skill-routing.json
- feature-registry.json
- design-system.json
- token-budget.json
Hover or focus a floor to reveal its components.
How the floors cooperate
The framework is organized as six floors stacked on a shared slab. Floor 1 holds the source-of-truth state. Floor 2 is the hub-and-spoke of skills and their cache tiers. Floors 3–5 add successive SoC-inspired primitives — skill-on-demand loading, batch dispatch, dispatch intelligence. Floor 6 observes everything else via the v6.0 measurement overlay.
For the full worked example of a single sprint flowing through these floors, see the SoC-v5.0 case study.
See the framework in motion →
Two real feature traces walked through the six floors — scroll-driven, with floor-by-floor firing order.
Developer guide (v1.0 → v7.7) →
Technical reference for developers onboarding to the framework. 4 enforcement layers, state.json schema, phase lifecycle, dispatch model, cache architecture, measurement protocol, 13 integrity check codes + 1 advisory, 3 operational walkthroughs, compressed v1.0 → v7.7 timeline.