PROOF / REAL EVIDENCE

Show the check.
Show the boundary.

These are real AXIOM verification events. Each one states the claim, the test, the evidence, the result, and where the proof stops.

VERIFIEDEvidence supports the scoped claim.
VERIFIED FINDINGA test produced a reproducible defect or useful result.
FAILED CLAIMObserved evidence contradicted the claim being checked.
BOUNDEDThe evidence does not authorize a broader conclusion.

CASE FILES

Evidence should survive the story told about it.

These cards use the same five-part format every time. A stronger claim requires stronger evidence.

P-01FAILED CLAIM

FALSE HEALTH DETECTION

Healthy on paper. Database unavailable.

Claim
The hosted project looked healthy.
Test
Compare management-plane state against actual PostgreSQL availability and recovery evidence.
Evidence
Management state remained healthy while SQL connections were refused. Recovery logs showed a pg_wal write failure caused by exhausted disk space.
Result
Management health was not sufficient evidence of database availability.
Boundary
One incident. This is not a general claim about the provider.
P-02VERIFIED

LOCAL RECOVERY

Backup is not proof until restore works.

Claim
AXIOM CoreDB could persist state, restart, back up, and restore independently.
Test
Fresh-node canary, persistence restart, backup creation, and disposable restore.
Evidence
Persistence restart PASS. Backup PASS. Disposable restore PASS. A SHA-256 digest was recorded for the known-good backup.
Result
Provider-independent relational recovery was verified for the bounded CoreDB scope.
Boundary
This does not prove the former hosted production database was fully migrated.
P-03VERIFIED FINDING

HIGHWAY STRESS

Declared capacity was not fresh capacity.

Claim
Routing capacity should reflect fresh matching workers, not stale declarations.
Test
Run the bounded PRODUCT_HIGHWAY_STRESS audit against routing and worker evidence.
Evidence
A stale-heartbeat freshness gap was found. Four dispatches were waiting on unavailable capability, and zero matching workers were observed at check time.
Result
The defect packet was released VERIFIED and guards failed closed.
Boundary
Diagnostic evidence only. It does not imply external Highway release readiness.
P-04VERIFIED

SOURCE ESCAPE

100 deployed functions recovered, 100 matched.

Claim
Deployed serverless source could be preserved before provider dependency loss.
Test
Enumerate active functions, capture exact source, compare live and snapshot slug sets, then read back the archive.
Evidence
100 active functions observed. 100 source snapshots captured. Exact slug-set match VERIFIED. Drive archive readback passed 9 of 9 documents.
Result
The source escape was independently verified.
Boundary
Source only. Database rows, auth rows, storage metadata, secrets, and runtime authority were not included.
P-05VERIFIED

OWNER CONTROL

The control path stayed alive without the database.

Claim
Desktop and browser control could remain operational without the hosted PostgreSQL data plane.
Test
Route a harmless tab-list command through Desktop Control, the Railway bridge, and local Chrome.
Evidence
Bridge online. Chrome connected. The command returned real browser tabs through the database-free route.
Result
The bounded owner-control route was verified end to end.
Boundary
This does not prove every browser action or every AXIOM subsystem was healthy.
P-06VERIFIED

PUBLIC RELEASE

Deploy, read back, keep rollback.

Claim
The public AXIOM site could be released with a preserved rollback path and checked post-state.
Test
Create a server-side rollback archive, deploy the release, then verify routes, responsive layout, HTTPS behavior, and 404 handling.
Evidence
Rollback archive preserved outside the webroot. Six public routes live. HTTP resolves to HTTPS. Invalid route returns 404. Responsive QA found no horizontal overflow.
Result
The website release was marked LIVE / VERIFIED for the public site scope.
Boundary
This verifies the static public site, not every internal AXIOM product or experiment.

THE RULE

Process success is not outcome success.

A request can return success while the useful state is still false. AXIOM treats readback, independent checks, rollback context, and stated limitations as part of the result.