Phase carry-over discipline
Friction surfaced in phase N's verification round becomes phase N+1's input
- Status
- PUBLISHED
- Priority
- P1
- Rank
- PROCEDURE
- Cited
- 6×
- Updated
- 2026-05-14
Assertion
Friction surfaced in phase N's verification round becomes phase N+1's
input. The closing phase is not extended to absorb it.
Why
Extending the closing phase to swallow friction is the failure mode
that cost the source project the most clarity to discover.
Mechanism
Triage each item as closed (trivial), in-budget (justified carry), or
deferred (assigned
M(N+1).x.y in the same commit as the phase-close
decision doc).Cited by
- decisionCairnet bridge principal binding — canonical value is `agent:petrova-cairnet-bridge`
- findingSP-1 acceptance log — ROCKY cairnet seam
- findingSP-1 seam-defect — cross-repo assembly does not deliver SC-1
- findingSP-1.5 seam-defect — agent:-prefix mismatch breaks the C2↔I1 join
- findingSP-1.6 caller-compat audit — GET /api/cairn/stones
- findingSix defects surfaced while onboarding sparki-tools: ADR path collides on same-day repeat acts, walkers hardcode docs/decisions, reconcile_drift's stale-sweep hint names a flag that does not exist, merged act branches are never deleted, the CLI test suite shares cwd/env across concurrent files, and the deposited notify workflow dispatches the repo name as the slug