Boundaries and verification

What the gateway can do

It can serve synthetic artifact and receipt projections, classify a supplied artifact, and present the explanation in a browser. It deliberately does not expose the standalone API’s demo-reset route.

The Agent can return a proposal for a human to review. It cannot execute a worker, approve its own proposal, change infrastructure or turn a synthetic record into authoritative evidence.

Where authority stays

Workers and their evidence stores are outside this application runtime. The in-process API store is disposable. A returned receipt, success label or HTTP 200 is not a new durable worker result.

The mutation_authorized=false field communicates the response contract. It is not a universal security control on its own: route selection, implemented code paths, environment permissions and separate authorization still matter.

The one-process gateway has no production-grade service isolation. Do not present it as a secure multi-tenant runtime, production monitoring console or durable evidence database.

What the tests check

The pinned public test suite covers:

three synthetic artifacts and the expected inspection responses;
same-origin gateway wiring, readiness and Agent health;
omission of the demo-reset route;
an unauthorized CORS preflight not receiving an allow-origin grant;
strict models and projection-content checks;
a container/browser workflow that builds Linux amd64, assigns PORT, exercises all three explanations and checks the browser journey.

The projection guard permits three exact public repository links in specified UI/test files. It does not permit arbitrary GitHub coordinates or private operational details.

The existence of a test or workflow is not proof that it ran successfully in every environment. The local setup page records the observed container results and Compose timing qualification explicitly. Detailed operational test records remain outside this documentation collection.

Verification is not engineering acceptance

A passing check establishes its specific tested behavior for a candidate and environment. An engineering acceptance decision needs its own authorized disposition. A missing acceptance record is not the same as a rejection.

Similarly, recording an exact source commit for these pages provides documentation provenance. It does not prove a whole private-to-public transformation lineage or attest the image currently running at an external endpoint.

Historical and current runtime claims

These pages make no new hosting or availability claim. A previous public deployment record is evidence about the event it recorded; it is not a permanent uptime guarantee. Absence of an independent runtime observation is not proof that a system failed or never existed.

No production traffic, SLO, autonomous action, persistent hosted evidence authority or complete processing/replication execution is claimed by this inspection demonstration.

Source and provenance

Curated adaptation of pinned public source; not a current hosted-deployment attestation.

Seemorghdev/edge-evidence-reference-platform-public @ 37e8a8f · source review recorded 2026-10-15T06:52:47Z UTC

Adapted from Apache-2.0 source by Seemorghdev. Changes are explanatory and do not amend the engineering source. Source license · NOTICE · Third-party notices · Source manifest