Production Revision
Record the exact deployed main commit SHA.
OMOS-REF-0001 • Production Proof • Critical Gate
OMOS-REF-0001 is the reference-run standard for proving that OMOS is not merely implemented in source code, but operating correctly on the canonical production runtime. This page does not self-certify production status. A PASS requires verifiable evidence for all nine gates below.
Record the exact deployed main commit SHA.
/api/v1/persistence must report PostgreSQL with durable persistence enabled.
A real browser-submitted Ask OMOS request creates a unique Decision ID.
Layer 1 → Alignment → Council → Governed Synthesis completes with stage state preserved.
The server records the authorized APPROVED or REJECTED disposition.
The complete record is saved with provenance, timestamps, version state, and hashes.
The production runtime is restarted or redeployed after the record is created.
The exact Decision ID and human disposition survive the restart.
Dashboard History finds and reopens the exact same Decision Record with lineage intact.
PASS only when all nine gates have production evidence. A successful-looking run that disappears after restart is an automatic FAIL. A merged commit is not proof of deployment, and a deployment is not proof that the required production behavior works.
Checking the public persistence endpoint…
The public endpoint above is one piece of evidence only. The exact deployed SHA, real browser run, Human Gate record, restart test, and Dashboard reopen still require their own proof.
Functional means implemented enough for controlled validation. Verified means the relevant behavior has passed defined tests. Production applies only to the specific component/revision demonstrated to be running and working in the intended environment. Use MERGED_NOT_DEPLOYED and DEPLOYMENT_READY when those are the accurate states.
Start the browser journey · Open Dashboard · Open Persistence API · Runtime Health