Intent Fidelity Dashboard | P4 Project Atlas

L1 Intent · Current Alignment

62%

Fidelity

20pt drift from Intent

Since Sprint 3, small decisions have compounded. 23pt below the 85% target.

↓ Last week 82% → This week 62%

Fidelity over 8 weeks W1–W8 · Target 85%

Actual Drift zone Target 85%

Drift cause analysis · Detected causes

Sprint 3 · 2026-04-08

Dev's "performance optimization" call — exploration flow shortened

Weight −14pt

Sprint 2 · 2026-03-24

Design's "shortest path" refinement — browsing elements removed

Weight −4pt

Sprint 1 · 2026-03-10

Minor spec change from PM — added filter conditions

Weight −2pt

Intent Drift · automated analysis log ▼ expanded

14:36:02compare_intent(L1.v1) ↔ implementation(sprint-3.commit-a4f)

14:36:03→keyword-drift: "welcome hesitation" (7) → 0 (removed in nav.tsx)

14:36:04→behavior-drift: avg-dwell 4.2s → 1.8s (measured in staging)

14:36:05→cause-weight: Dev decision +14, Design refactor +4, PM spec +2

14:36:06✓alignment_score = 0.62 · confidence = 0.94

How do you want to handle this drift?

Option A · Accept

Accept the drift

Update Intent to justify the new direction. Learning writes back to L1.

Option B · Update

Rewrite the Intent

Edit L1 Intent. History is preserved — replayable later.

Option C · Revert

Fix the implementation

Course-correct in Sprint 4. Intent stays. Code closes the gap.