Run Explanations
Why did each analysis produce this result? Evidence-cited, deterministic — no LLM in the loop.
PASS4/11/2026
ISC 0.92CCS 0.89Truth A
All integrity checks satisfied — webhook delivery tracking follows golden pattern
Why
- • All route handlers include runtime validation at the boundary, consistent with golden pattern GP-004
- • The delivery tracker correctly imports from packages/shared-utils/src/logger.ts per immutable wire
- • Test coverage includes both success and failure delivery paths
Evidence
ISC Signal
Task intent precise with constraints specified → ISC 0.92
CCS Signal
Bundle covered all webhook dispatcher files + shared retry → CCS 0.89
ECL History
4 prior webhook PRs by Sara all passed with confidence >0.85
Golden Pattern
GP-005 (Retry with Backoff Pattern) matched
Confidence Breakdown
intentConfidence: 0.92
dependencyCoverage: 0.88
testCoverage: 0.91
structuralValidity: 0.87
stakeholderCoverage: 0.85
WARN4/10/2026
ISC 0.82CCS 0.64Truth B
1 P1 finding — promo route missing runtime validation
Why
- • Route handler POST /billing/promo accepts promoCode without runtime type guard — financial data requires boundary validation
- • Direct new Date() in promo-validator.ts bypasses shared-utils timezone-safe date handling
- • 2 prior billing PRs by Marcus had identical runtime-validation findings
Evidence
ISC Signal
Clear intent but no discount bound constraints → ISC 0.82
CCS Signal
Missed packages/validation/billing.ts in bundle → CCS 0.64
ECL History
ECL entries #147, #152 show same pattern in billing service
Confidence Breakdown
intentConfidence: 0.82
dependencyCoverage: 0.61
testCoverage: 0.72
structuralValidity: 0.68
stakeholderCoverage: 0.55
BLOCK4/8/2026
ISC 0.58CCS 0.42Truth C
Immutable wire violation — auth token refresh bypassed centralized JWT verification
Why
- • services/auth/routes/refresh.ts imports a local JWT helper instead of services/auth/middleware/jwt-verify.ts — violates immutable wire
- • The local helper was AI-generated and not imported by the middleware barrel export (ghost file pattern)
- • Evidence gate eg-001 requires "observed" tier for auth middleware changes — only "possible" evidence present
Evidence
ISC Signal
Vague intent ("refactor auth token refresh") → ISC 0.58
CCS Signal
Bundle missed jwt-verify.ts dependency → CCS 0.42
Structural Trust
Immutable wire violation: login route → jwt-verify.ts
Evidence Gate
eg-001 requires "observed" tier — only "possible" evidence found
Confidence Breakdown
intentConfidence: 0.58
dependencyCoverage: 0.38
testCoverage: 0.31
structuralValidity: 0.25
stakeholderCoverage: 0.40