Corrective Action Report — Operational-surface question gap (late-stage architectural reframe pattern)
CAR ID: CAR-2026-05-11-A Filed: 2026-05-11 Filer: Q (instruction-optimizer / Quality System) Companion audit:
docs/quality/audits/2026-05-11-abs-company-compass-launch-audit.mdStatus: Proposed (pending V acceptance) Authority: Q proactive audit authority granted 2026-04-12 (QMS establishment)
1. Incident
On 2026-05-10 22:17 CT (approximately 11 hours before the Abs Company AI-Native Shift Phase 1 kickoff scheduled for 09:30 CT 2026-05-11), Chris Carolan authored commit bfff961 to the V2 monorepo (/mnt/d/Projects/VFT_Platform/2026_VFT_Platform_Infrastructure), demoting the entire Sanity methodology content backbone of the Compass surface into a closed-by-default "Background context" <details> element and elevating a new ProjectView component (Service + Project + Deliverables + Tasks with live HubSpot binding) to the top of the page.
The reframe inverted the Abs Company PRD's FR-14 specification (which specified the methodology-content backbone as the substantive content surface) and was not anticipated by either of the two PRDs governing the work:
docs/plans/abs-company-ai-native-shift-launch-prd.md(FR-14 specifies methodology content authoring as primary surface)docs/plans/compass-end-state-prd.md(4-mode product: Compass Canvas, walkthrough, blank-canvas, library — none of which is "live project management communication surface")
The commit message frames the reframe: "Compass is the live project management communication surface; Sanity methodology content is background context."
The work demoted by bfff961 represented approximately Waves 7–12 (commits e55d6ffc7 through 482013baf plus parallel V2 component implementation) of content authoring, schema design, attribution corrections, vocabulary cleanups. All of that work functions correctly and remains on the page — but is no longer the primary surface a customer sees on arrival.
2. Timeline
| Time (CT) | Event | Evidence |
|---|---|---|
| 2026-04-16 | Chris authors canonical "What Done Looks Like" draft | clients/abs-company/documents/2026-04-16-what-done-looks-like-draft.md |
| 2026-05-10 ~14:00 | V drafts initial Abs Co 5P plan | commit e84788956 |
| 2026-05-10 ~15:00 | V drafts initial Abs Co PRD | commit e94b59b1c |
| 2026-05-10 ~16:00 | Q bias-check audit on Abs Co 5P + PRD | commit 7abeb4dc0 |
| 2026-05-10 ~17:00 | Canonical realignment commits (Wave 7 corrective) | commits c18610e58, e452414dc, e55d6ffc7 |
| 2026-05-10 19:09 | Mirror Compass pre-launch QA audit committed (GO-WITH-NOTES) | commit 908e5bbaf |
| 2026-05-10 21:24-21:41 | Waves 10-11 ship to V2: WorkInFlight rendered, cancel commitment removed | V2 commits 97f46b6, be5c1da |
| 2026-05-10 22:01 | Wave 12 erratum on Own the Mission attribution | commit 482013baf |
| 2026-05-10 22:04 | Mirror final pre-kickoff audit (WARN — UI Cards + Resource Hub MISSING; reframe not yet visible) | V2 commit aae7f65 |
| 2026-05-10 22:17 | bfff961 — architectural reframe; foreground ProjectView, demote methodology content |
V2 commit bfff961 |
| 2026-05-10 22:25-22:44 | Deploy stabilization: passthrough image service, engines.node pin, auth wiring | V2 commits 9ed71d7, ff0578b, 0a24741, 8feee67 |
| 2026-05-11 03:19-03:50 | Final deploy fixes: @vf/auth resolution, install command, Response.redirect headers | V2 commits 0338019 through bb892ff |
| 2026-05-11 03:51 | Q audit captures live state; HTTP 200 in 0.99s; ProjectView foregrounded; methodology in Background context | curl response, audit doc |
| 2026-05-11 09:30 (planned) | Abs Company kickoff | (future at audit time) |
3. Root cause analysis
3.1 Primary root cause: spec-shape over function-shape
Both PRDs specified what Compass IS (a relationship-narrative artifact + engagement surface in the Abs Co PRD; a 4-mode umbrella product in the End-State PRD) without asking what work Compass has to DO at the first customer touchpoint (project communication for an active engagement).
The 5P framework's Purpose section asks for "specific problem statement" and "definition of done." Neither prompt requires articulating what the surface does in its first 30 seconds of customer use. The PRDs answered the IS questions thoroughly and the DO question implicitly. The implicit answer (methodology-content backbone is what the customer sees) was wrong.
3.2 Contributing causes
3.2.1 The canonical source describes Done state, not kickoff operation. The 2026-04-16 "What Done Looks Like" draft describes the Three Hubs operating system, the 4-stage sequence, the governance pattern, the 5 measurable capabilities. It does not describe what the kickoff conversation needs to look like, what surface the kickoff is held against, or what the first customer interaction with that surface should accomplish. Both PRDs deferred to the canonical source on framing; neither extended the canonical source to address kickoff operations.
3.2.2 Bias-check audits inspect for upstream bias classes, not for operational mis-specification. Q's bias-check protocol (per docs/quality/audits/2026-05-10-canvas-5p-bias-check.md) examines:
- Box 1: NOT recency
- Box 2: NOT tech-debt-bias
- Box 3: NOT sunk-cost
It does not examine: NOT operational-surface mis-specification. The Abs Co bias-check audit produced caveats C10-C19 against the 5P + PRD; none of those caveats are "what work does this surface have to do at first customer touch?"
3.2.3 Mirror QA audits against spec. Mirror's content-quality, forbidden-language, mobile-responsive, and visual-regression checks are spec-conformance checks. If the spec specifies the wrong primary surface, Mirror's audits cannot surface the mis-specification.
3.2.4 Single-agent PRD authorship. V wrote both PRDs in the same multi-hour window. The PRD-author and the PRD-acceptor are the same agent for orchestration-style commitments. Cross-validation against operational intent depends on Chris catching the question. Chris caught it on launch eve, not at PRD-acceptance time.
3.3 Pattern recognition
This is the third instance in 30 days of late-stage architectural reframes:
- Apr 22 mass rename → Apr 25 walk-back (9 commits, ~$57.83 / 27-agent compute spend). Hone's audit found 14 of 15
.compass-state.jsonfiles belonged to walkthrough-only clients. The team paid to back out of merging canvas + portal + compass into a single substrate decision. Reference:docs/quality/cars/2026-04-25-corrective-dewey-registrar-activation.md(companion incident). - Apr 17 Showcase routing reframe. Showcase routing rule established as canonical for public website pages (
skills/enforcement/showcase-website-routing.md). - May 10 22:17 Compass surface reframe. This incident.
Three reframes in 30 days. The pattern is real. Each reframe is locally corrective for a real reason — but the cumulative cost (spec-cycles spent against the wrong target) is non-trivial and recurring.
4. Immediate fix
The reframe itself (commit bfff961) IS the immediate fix. Chris's intervention recovered the operational surface before kickoff. The shipped product is canonically correct for Chris's actual intent.
The PRDs are still mis-specified at audit time. They were not updated post-reframe to reflect the operational intent. This creates ongoing fiction in the spec corpus: future readers of the Abs Co PRD will see FR-14 specifying methodology content as the substantive content surface, which contradicts the shipped state.
Recommended immediate fix: V approves PRD text updates by Architect to reflect operational truth:
- Abs Co PRD FR-14 description amended to "Compass content backbone — ProjectView (live HubSpot project communication) as primary surface; methodology content as secondary Background context."
- End-State PRD includes a fifth Compass mode: "live project management communication surface anchored on HubSpot canonical" (or equivalent framing).
5. Permanent prevention
5.1 New process: PRD operational-surface verification
Before any customer-facing surface FR is committed in a PRD, the PRD must answer a structured operational-surface question in its User Stories section:
What specific work does this surface perform during the first customer interaction with it? Name the customer's first three observable behaviors. If those behaviors do not exercise the substantive content of the surface, the surface is mis-specified.
The question must be answered explicitly. If unanswered or vague, the PRD does not advance to FR commitment. Q owns the gate.
5.2 Bias-check protocol extension
Extend docs/quality/audits/{date}-{topic}-5p-bias-check.md template (Q-authored) with a fourth box:
Box 4 — NOT operational-surface mis-specification. What evidence makes the chosen primary-surface framing independent of "the surface we think it is" vs. "the surface customers will use it as"? What does the first 30 seconds of first customer use look like? Does the primary surface answer the customer's first need or the team's spec-shape?
Box 4 requires written evidence the same way Boxes 1-3 do.
5.3 Hone-implemented rule update
Hone adds to skills/enforcement/vf-platform-context.md or new skills/enforcement/vf-operational-surface-verification.md:
Before any PRD specifying a customer-facing surface advances to FR commitment, the PRD must answer: what specific work does this surface perform during the first customer interaction with it? The answer must be concrete (named behaviors, not abstract framings). Q owns enforcement.
5.4 Echo pattern memory
Echo records the three-instance pattern of late-stage architectural reframes (Apr 22-25, Apr 17, May 10) as a formal pattern. Pattern shape: parallel-spec sessions producing customer-facing surfaces where the spec describes surface shape without specifying surface function; on launch eve, function visibility forces reframe.
Threshold for escalating to mandatory enforcement gate: one more recurrence within 60 days.
6. Process register impact
New process to add to docs/quality/process-register.md:
| Process | Owner | Risk Tier | Verification Frequency | Method |
|---|---|---|---|---|
| PRD operational-surface verification | Q | Tier 2 (High) | Monthly | Audit any PRD authored in the period for Box 4 / operational-surface question coverage. Sample = all customer-facing surface PRDs. |
Trigger: any PRD with customer-facing surface FRs.
7. Recurrence prevention check
The permanent prevention measures above are upstream of the reframe moment. The pattern's root cause is "the spec was answering the wrong question for several weeks." Catching the question late produces the reframe; catching it early prevents the wasted spec cycles.
If after permanent prevention is in place a fourth instance occurs within 60 days, the prevention failed and CAR escalates. Q tracks.
8. References
- Companion audit:
docs/quality/audits/2026-05-11-abs-company-compass-launch-audit.md§ 6 + § 8 CAR-A - Bias-check audit:
docs/quality/audits/2026-05-10-canvas-5p-bias-check.md - Bias-check audit:
docs/quality/audits/2026-05-10-abs-company-5p-bias-check.md - Apr 25 walk-back companion:
docs/quality/cars/2026-04-25-corrective-dewey-registrar-activation.md - Reframe commit (V2):
bfff9612026-05-10 22:17 CT - Canonical source:
clients/abs-company/documents/2026-04-16-what-done-looks-like-draft.md
Filed by Q under proactive audit authority. Awaiting V acceptance for permanent-prevention deployment.