Skip to content
fitme·story
fitme·story
View as

The framework

Seven floors. Hover to explore how each layer contributes.

Reading as a PM:the framework is the product lifecycle made enforceable — why it exists, what each version shipped, and how outcomes get measured. The seven floors below are the “how”; the version timeline is the “what changed.”
  1. Floor 7v7.x Integrity & EnforcementData integrity → mechanical enforcement → promotion
    • v7.5 Data Integrity Framework (8 cooperating defenses)
    • v7.6 mechanical enforcement (write-time gates)
    • v7.7 validity closure + per-PR review bot + 72h integrity cycle
    • v7.8 bridge Mechanisms A–F
    • v7.8.1 branch isolation + feature-closure completeness
    • v7.8.3 cross-repo state sync
    • v7.8.5 Observed Patterns Catalog + W9 drift hook
    • v7.8.6 cadence batch (integrity-diff, unified preflight)
    • v7.9 promotion — 3 advisory gates → enforced
    • v7.9.1 F16 try-repo harness + F17 last-fired index + F2 reality-check
    • HADF dispatch program incl. Phase 3A sensing layer
    • t14 platforms_tested parity field
  2. Floor 6v6.0 MeasurementInstrumentation overlay
    • phase-timing.json
    • cache-hits.json
    • CU v2
    • rolling baselines
  3. Floor 5v5.2 Dispatch IntelligenceParallel Write Safety
    • complexity_scoring
    • model_routing
    • tool_budgets
    • mirror_pattern
    • snapshot/rollback
  4. Floor 4v5.1 Adaptive BatchThroughput primitives
    • batch_dispatch
    • result_forwarding
    • model_tiering
    • speculative_preload
    • systolic_chains
    • task_complexity_gate
  5. Floor 3v5.0 SoC-on-SoftwareReclaim context
    • phase_skills (skill-on-demand)
    • compressed_view (cache compression)
  6. Floor 2Skills + CacheHub-and-spoke
    • pm-workflow/SKILL.md
    • .claude/cache/ L1/L2/L3
  7. 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

Seven floors stacked on a shared state slab. Each floor adds one capability on top of the floors below it — read top-down to see how state becomes skills, skills become primitives, primitives become measurement, and measurement becomes the consolidated v7.x integrity-and-enforcement layer.

01

State

Source of truth — state.json per feature, integrity ledgers, append-only checkpoint logs.

02

Skill ecosystem

12 skills since 2026-05-14 (1 hub + 11 spokes; was 11 through v7.8.4) plus their L1 / L2 / L3 cache tiers.

See the skills
03

Skill-on-demand loading (v5.0)

SoC primitive: load only the SKILL.md files the current phase needs — reclaims ~30K tokens per session.

04

Batch dispatch (v5.1)

SoC primitive: template-once-iterate-N pattern across feature tasks; reduces per-task overhead.

05

Dispatch intelligence (v5.2)

Score complexity → probe capability → dispatch with budget. Cuts average tool usage 48% and variance 84%.

06

Measurement (v6.0)

Deterministic phase timing, cache-hit tracking, eval coverage gates, CU v2 continuous factors.

07

Integrity & enforcement (v7.x)

32 instrumented / 34 live gates (20 write-time + 9 cycle-time + 2 W9 hooks + 1 standalone), 28 firing across v7.5 → v7.10 (3 advisories promoted to enforced via the v7.9 promotion 2026-05-21): the v7.5 Data Integrity Framework, write-time pre-commit hooks, the 72h integrity cycle, per-PR review bot, weekly framework-status cron, branch isolation, feature-closure completeness, cross-repo state sync, the Observed Patterns Catalog, and the v7.9.1 build window (F16 try-repo harness, F17 last-fired index, F2 reality-check). v7.10 (2026-06-10) hardened the meta-layer with the GATE_COVERAGE_ZERO observability check, and the v8.x build window (opened 2026-06-17) promoted F16 try-repo harness advisory→enforced (2026-06-17) and T14 PLATFORMS_TESTED advisory→enforced (2026-06-21) and shipped the F4/F1/F3 roadmap-realism advisory gates. Includes the HADFdispatch program through its Phase 3A sensing layer.

See the dispatch layer

v7.8 → v7.10 release timeline

The early entries are patch-level releases on Floor 8 (the v7.8 bridge); later entries carry the framework through the v7.9 promotion and into v7.10. In that pre-v7.9 bridge era the enforcement-gate count held at 34 mechanical + 5 advisories until the v7.9 promotion (2026-05-21) flipped 3 advisories to enforced.

  1. v7.8

    Bridge layer ships — six advisory mechanisms A–F.

  2. v7.8.1

    Branch-isolation + feature-closure-completeness gates added (advisory).

  3. v7.8.2

    Cross-repo telemetry exemption documented — closes v7.9 candidates F7 + F8.

  4. v7.8.3

    Cross-repo state-sync release umbrella (V2 / V9 / D-1 / D-3) — 5 phases × 10 PRs across 2 repos.

  5. v7.8.4

    TIER_TAG_LIKELY_INCORRECT heuristic narrowed + PR cache auto-refresh — clears a 33-finding false-positive class.

  6. v7.8.5

    Observed Patterns Catalog (23 gate + 9 workflow patterns) + W9 branch-drift hook.

  7. v7.8.5+S

    12 SKILL.md sweep + make skills-audit with 6 conformance checks. /brainstorm-pm added (12th skill).

  8. v7.8.6

    Cadence batch — make integrity-diff vs anchor, unified make preflight WORK_TYPE, weekly Mechanism A zero-drift, W1 ssh-agent preflight.

  9. v7.9

    Promotion Release shipped: 3 advisory gates → enforced via single-flag flip at scripts/check-state-schema.py:132 after 14-day Mechanism A calibration (18 + 13 + 13 firings, 0 zero-candidate rows, 0 false positives). 37 mechanical gates + 5 advisories post-promotion. Phase E validation soak 2026-05-21 → 2026-06-04.

  10. v7.9.1

    Build window opened at Phase E exit — 8 ships / 14 PRs, 0 new enforcement gates (Phase E exit discipline held). Observability + dev-env hardening: F16 try-repo pre-commit harness (3rd gate-test layer), F17 per-gate last_fired_at index, F2 Phase 0 reality-check, launchd-drift extension, reusable deployed-URL probe. CI workflows 8 → 14; Observed-Patterns W1–W28 → W1–W32.

  11. v7.10

    GATE_COVERAGE_ZERO observability + field-rename closure — hardens the meta-layer watching whether each gate is actually firing, with no new product-facing gates. The GATE_COVERAGE_ZERO meta-check reads the F17 gate-last-fired.json index to flag silent gates plus 0-candidate mis-wires; three cycle-time checks now emit mode="cycle" coverage; two reader/index field-rename silent-passes closed (observed-patterns #24).

  12. v8.x build window

    Build window opened (kickoff gate cleared) — F16 try-repo harness promoted advisory→enforced 1 day early via main required status checks (the try-repo-harness CI job, not a code flag; K2 0% false-positive rate over 60 CI runs / 13 days). Three ready-now roadmap-realism advisory gates shipped: F4 FRAMEWORK_VERSION_STALE (write-time, PR #740), F1 STATE_TASKS_FILESYSTEM_DRIFT (cycle-time, PR #752), F3 DEPENDENCY_GRAPH_CYCLE (cycle-time, PR #753). F4 later promoted advisory→enforced 2026-07-08 (PR #858); SCHEMA_DIFF (T12) shipped 2026-07-09. 32 instrumented / 34 live gates total.

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 seven floors — scroll-driven, with floor-by-floor firing order.

Developer guide (v1.0 → v7.10) →

Technical reference for developers onboarding to the framework. 4 enforcement layers, state.json schema (incl. v7.8.3 cross-repo state_owner enum), phase lifecycle, dispatch model, cache architecture, measurement protocol, 32 instrumented gates, v7.8 bridge mechanisms A–F, v7.8.3 cross-repo state-sync, v7.8.5 Observed Patterns Catalog + W9 branch-drift alert, v7.8.5+S skills-review execution (12 skills + make skills-audit), v7.8.6 cadence batch (unified preflight + integrity-diff + weekly trend scan + dependency audit), 3 operational walkthroughs, compressed v1.0 → v7.10 timeline.