TRIAL1-ARCH-PROOF-001 · recorded 2026-08-20T01:16Z

A proof record that only lists successes is marketing, not evidence.

This is the formal build record and evidence register. Figures are read from the live database at capture time, not transcribed from earlier notes, and every row states what the number does not establish.

Automated verification

72 tests, five consecutive identical runs

Suite	Tests	Covers
gonogo.test.ts	27	The 13 dossier Go/No-Go gates
contracts.test.ts	12	Structured error contract, Golden Assignment composition
domain.statemachine.test.ts	10	28 states, declared transitions, guard wiring
kernel.integration.test.ts	8	Eligibility gate, concurrency, illegal transitions, chain linkage
incidents.test.ts	7	SEV model, seven-stage lifecycle, root-cause and resume discipline
trialPause.test.ts	4	Intake refusal, error contract, in-flight assignments unaffected
audit.chain.test.ts	3	Hash-chain verification semantics
auth.logout.test.ts	1	Session teardown
total	72	0 failed · 0 skipped · TypeScript 0 errors

Platform state at record time

Measured, not estimated

0141

Assignments (test artifacts removed)

092

— of which golden-test fixtures

040

Closed and archived

04,591

Audit entries

0142

Eligibility snapshots (immutable)

01,513

State transitions recorded

0194

— rejected by guards

0597

AI actions logged

01,481

Human touches recorded

0 / 26 / 2

Vendors / held by hard gates

Evidence register

What was measured, where to re-check it, what it does not prove

Build and test evidence

Test suite

172 passed · 7 todo · 20 files

The 7 todo are named blockers, not silent skips

TypeScript

0 errors

pnpm check

Suite stability

Clean on repeat runs

After fixing shared-state contention

AI contract set

v1.0.0

5 of 12 contracts unexercised

Cohort integrity (G-12)

Assignments

144

Test-suite artifacts removed before capture

Record class SYNTHETIC

Golden fixtures that inject failures on purpose

Record class TRIAL

Generated trial-population records

Record class PRODUCTION

The most important number in this register

Eligibility snapshots

195

Immutable, canonical-hashed

Audit integrity (G-07)

Audit entries

7,638

Unchanged by artifact cleanup, by design

Linkage breaks

Verified across the full chain

Mutation paths

No update/delete of audit rows anywhere — asserted by test

Legacy unverifiable entries

Deliberately not rewritten

INSERT-only grants

NOT APPLIED

These credentials carry no GRANT authority

Scheduler durability (G-02)

Unattended sweeps

37 → 119

Consecutive failures: 0 · cadence 300s

External monitor

503 on FAILED/UNKNOWN

Caught DEGRADED, missedCadences: 1 during a real post-deploy stall

Post-deploy probe

Fails closed

Not yet a blocking pipeline step

Known constraint

Redeploy stalls cron silently

Job reads is_enable: true while delivering nothing

Defects

Found by something that genuinely tried to break the platform

Infinite timer retry loop

Timers whose referent no longer existed were released for retry on every sweep, creating an infinite loop that also masked genuine failures. Permanent failures are now abandoned with an audited reason, distinguished from transient ones.

Hardcoded CLEAN document status

The quarantine gate reported a clean scan result with no engine behind it. The status is now unresolved until a licensed engine answers, and certification is blocked while it is.

Two vacuous assertions

Two earlier assertions passed by finding nothing to attack. Fixing those mattered more than the ticks they produced.

Model and rules provenance

Which engine produced which record

Primary model claude-haiku-4-5 · fallback chain gemini-3-flash-preview → gpt-5-mini

rules v1 · platform 1.0.0-trial1 · 20 August 2026