Blueprint · Integrator API · mastery_gate · attempt 9

The API passes; cross-fan publication blocks adoption.

A fresh 19-check rerun proves the documented Grade 5 create, tenant isolation, datastore boundary, and real CASE/Content calls on both API origins. Publication is split across attempt-7 and attempt-8 mastery bytes, and the adaptive canonical path serves mastery; the engine still cannot preserve both fan identities.

19 / 19fresh API checks

12 / 12decision axes pinned

1 P0publication blocker

Exit 1canonical hosting check

Current API capture: 28 Jul 2026, 17:36:09 UTC. Canonical publication capture: 17:35:54 UTC. The shared primary alias serves attempt-8 mastery bytes; the dedicated and master mastery origins serve attempt-7 mastery bytes; the adaptive fan serves attempt-8 mastery bytes. The prior opposite collision is historical corroboration, not current wire state.

Fresh-eyes integrator decision

The product contract passes; the fan isolation contract fails

The AcmeTest maintainer’s tech lead can replay the full API pass and the publication blocker without source access. Exit 0 from both scripts unlocks adoption; any non-zero result blocks it.

PASS · API contract

The Grade 5 request returns 202

Both API origins returned ready operations, opaque 404s across tenants, complete 52-item coverage, and request-correlated 12 CASE plus 8 Content 2xx calls. No local stand-in was credited.

P0 · publication engine

A protected hash URL aborts state promotion

The fan deployment succeeded, but its stable alias remains on attempt 7. The engine probes the protected deployment-hash URL, receives 302, only knows how to remediate 401, then discards the deploy before state and canonical rewrites advance.

Tech-lead call: a mastery report is reachable, but the current attempt is not canonical and adaptive_diagnostic is overwritten. Do not adopt the shared QC surface yet. The API rerunner exits 0; the hosting verifier exits 1 until all fan identities coexist correctly. Both scripts must return 0 before adoption.

Endpoint evidence

Fresh wire results

The credentialed rerunner uses new idempotency keys and retains no credential, request body, opaque resource id, or tenant payload.

Check	Canonical	Immutable	Evidence
Health	200	200	mastery_gate; ready
Anonymous list	401	401	Typed authentication-required
Authorized list	200	200	Current Content 2xx trace on each origin
Exact documented create	202	202	Ready; Location shape; 12 CASE 2xx + 8 Content 2xx each
Idempotency	202 / 409	202 / 409	Replay header true; changed body rejected
Detail + exhaustive coverage	PASS	PASS	20 rows; 9 standards; 52 items; ≥ DOK; target 100
Cross-tenant reads	404 / 404	404 / 404	Operation and blueprint existence both opaque
Cross-tenant create	422		Current isolation-tenant request had no Location and no write
Direct datastore	401		Current unauthenticated Supabase REST request denied
Dedicated mastery report + downloads	STALE		`alphatest-blueprint-qc-mastery-gate.vercel.app`; 200 with attempt-7 mastery bytes
Canonical QC identities	EXIT 1		Primary is attempt 8; dedicated and master mastery are attempt 7; adaptive incorrectly serves attempt-8 mastery report, matrix, and audit

DoD D2 + D5

Security boundaries and upstream reality reproduce

401anonymous API

Both deployments deny anonymous tenant-data lists.

404cross-tenant detail

Both operation and blueprint existence remain opaque on both origins.

401direct datastore

Unauthenticated Supabase REST is denied.

20×2xxCASE + Content

Each create carries 12 CASE and 8 Content 2xx traces naming the declared Platform3 host.

No mock or local fixture is credited as upstream proof. API-fronted datastore; server credentials are not published. Current tenant isolation and the direct anonymous datastore boundary are both proven at the deployed edge.

Severity-ranked findings

One blocker, routed outside the grid

P0blocking

BUG — Blueprint QC fan identities overwrite one another

Observed: the credential-free node verify-hosting.mjs exited 1 at 17:35:54 UTC. The shared primary alias served attempt-8 mastery bytes, while the dedicated mastery origin and master’s mastery fan path served attempt-7 mastery bytes; the adaptive fan path served attempt-8 mastery identities. Redeployment cannot preserve both fan values simultaneously.

Root cause: the successful fan deploy is followed by an HTTP check against its Vercel deployment-hash URL. The previous reviewer captured a 302 SSO redirect there at 12:35:32 UTC. The engine helper ensure_vercel_public_if_401 remediates only status 401, so 302 reaches deploy_to_vercel as non-200. The engine exits before patching summary.json/state or regenerating the canonical master rewrite. Another artifact rebuild or plain driver redeploy cannot close this defect.

Fix: repair the loop engine to recognize Vercel SSO 302/303 as protection and disable it before rechecking, or perform the post-deploy 200 check against the public stable project alias. Then rerun the driver, require state to record the fan deployment, regenerate master rewrites, and require the unmodified canonical verifier to exit 0 with exact report/matrix/audit byte matches on both mastery origins.

Triage: BUG in the post-doer publication runtime, outside the architecture → integration cell grid. No approved architecture, dictionary, website, API behavior, or surface-QC bytes must roll back. This is customer-visible wrong content, not only a stalled build, and it taints either fan after the next redeploy. Watchdog evidence contains exactly 21 unique mastery-gate 302 failures in the bounded 06:58:31–15:44:10 UTC window; reviewers recorded the 23rd occurrence during attempt 6’s driver deploy at 16:19:18 UTC and the 24th during attempt 7’s driver deploy at 17:03:39 UTC. The watchdog livelock guard must now notify, mark the cell escalated, park it instead of scheduling another content rebuild, and guard other publication-dependent work from the same engine failure.

Cross-deliverable QC

Approved contract and live implementation agree

Deliverable	Verdict	Evidence
Architecture	PASS	Approved bytes; 56 ITDs; all 12 API axes pinned.
Data dictionary	PASS	Approved hash; route and field contract agree.
Customer website	PASS	Approved hash; exact Grade 5 example agrees.
Implementation@mastery_gate	PASS	Fresh attempt-9 19/19 rerun: exact create, idempotency, coverage, auth, isolation, datastore, and real upstream traces.
Surface-QC publication	GATED	No origin serves attempt-9 yet; the current three-origin split proves the engine still cannot publish mastery without corrupting or staling a sibling.

All 12 standard API decision axes checked

Write granularity, read shape, query model, concurrency, idempotency, auth shape, eventing, error envelope, tenant routing, conformance evidence, privacy/retention, and list endpoints map to active ITDs in the downloadable audit.

Independent reassessment

Replay both halves from a clean directory

The hosting verifier is a single file: its attempt-9 report, matrix, and audit hashes are embedded, so it does not read any companion file. It has no URL override and proves whether primary mastery, mastery fan, and adaptive fan identities are simultaneously correct. The API script exits 2 rather than guessing when reviewer fixtures are unavailable.

qc_tmp="$(mktemp -d)"
curl -fsSLo "$qc_tmp/verify-hosting.mjs" \
  'https://alphatest-blueprint-qc.vercel.app/verify-hosting.mjs'
node "$qc_tmp/verify-hosting.mjs"
# Current baseline: exit 1; required after engine repair: exit 0

curl -fsSLo "$qc_tmp/probe.mjs" \
  'https://alphatest-blueprint-qc.vercel.app/probe.mjs'
: "${BLUEPRINT_PROD_REVIEWER_JWT:?fresh demo reviewer JWT required}"
: "${BLUEPRINT_ISOLATION_REVIEWER_JWT:?fresh isolation JWT required}"
: "${SUPABASE_URL:?public Supabase project URL required}"
node "$qc_tmp/probe.mjs"
# Current baseline: exit 0; any non-zero result blocks adoption

Hosting 0 / 1canonical identities pass / diverge

API 0 / 1baseline pass / divergence

API 2reviewer fixtures unavailable

Live probe matrixTimestamped HTTP baseline Artifact auditHashes, axes, security, routing Hosting contractCanonical acceptance gate Engine blocker302 failure and repair gate Prior browser corroborationAttempt-7 visible wrong report; not current wire proof Prior local renderAttempt-7 presentation check; not current wire proof Hosting verifierNo credentials API rerunnerSecret-clean output

Repair routing

No grid rollback; repair and park the publication engine path

BUGcanonical identity collision

→

ESCALATEloop publication engine

→

ACCEPThosting verifier exit 0

The API contract is current and passes; do not roll back architecture, dictionary, website, implementation, or QC bytes.
Repair ensure_vercel_public_if_401 to treat Vercel SSO 302/303 as protection, or verify the public stable alias.
Only after the engine’s corrected 200 check may it patch summary/state and regenerate master rewrites.
Exactly 21 unique mastery-gate 302 failures occurred in the measured 06:58:31–15:44:10 UTC watchdog window; the 23rd was recorded at 16:19:18 UTC during attempt 6’s driver deploy and the 24th at 17:03:39 UTC during attempt 7’s driver deploy. Notify, mark the cell escalated, park it, and taint downstream canonical consumers until the hosting verifier exits 0.

Benchmark

Explicit state, endpoint evidence, repeatable reassessment

Qualys SSL Labs’ analyze API was fetched live during this attempt at 17:34 UTC and returned HTTP 200, READY, endpoint grade A+, engine 2.4.2. This report follows its fail-closed overall-state discipline and adds auth, tenant, upstream, documentation-byte, canonical-publication, and repair-routing receipts.