One evidence boundary, tested as a system
OGES connects a signed release manifest to typed evidence, entities, events, declared-universe denominators and exposure edges. A conformant bundle must preserve exact schema and object bytes, signed source-rights decisions, executable method provenance, bitemporal ordering, privacy state, event-evidence roles and explicit quantified-versus-qualitative boundaries.
| Layer | What the gate binds | What it does not claim |
|---|---|---|
| Evidence | Source, retrieval, time, availability, rights state and hashes | That the source statement is true |
| Event | Actors, state, coding, evidence roles and confirmation eligibility | Complete ground truth |
| Universe | Included, excluded, unmappable and stale members against one frame | Coverage outside the declared frame |
| Exposure | Endpoints, method, denominator, period, uncertainty and limitations | Realized loss, causation or advice |
| Release | Exact membership, policy snapshots and detached signature | Government or institutional endorsement |
The suite cannot be passed by refusing everything
One complete deterministic synthetic release must pass. Ten independently registered variants must fail for their exact reason: signature tampering, role-spoofed official confirmation, a dropped universe member, an invented method, numeric data on a qualitative edge, a future measurement period, rewritten rights state, duplicate JSON keys, false object counts and exposed restricted evidence. No case may be skipped.
python -m src.oges_conformance profile
python -m src.oges_conformance self-test
python -m src.oges_conformance validate --bundle /path/to/bundleThe runner is offline. Its report contains the profile, validator and schema hashes, release ID, release hash, object counts and refusal codes—not evidence text, exposure values, credentials or private keys.
One release, four deterministic products
The implemented synthetic Evidence Output Engine turns one validated release and one bounded event-to-target query into a research package, board-brief draft, newsroom claim card and authenticated offline audit bundle. All four products use the same object and evidence hashes. Fixed templates—not a language model—write their reader-visible sentences; every sentence carries object and evidence IDs, and a resealed prose or number change fails semantic recompilation.
The public compiler refuses non-public evidence and unlicensed artifact redistribution. A no-path result remains visible and is never reframed as proof of no exposure. The audit verifier requires a digest obtained outside the ZIP, rejects unsafe archive entries, checks every byte and revalidates the canonical release without executing bundled code.
- Synthetic four-output result — embedded products, exact release lineage and archive digest.
- Offline audit test bundle — synthetic source metadata and public test keys only.
- Strict output-set schema.
This proves deterministic construction and refusal behaviour, not a production release, real exposure map, external utility result or institutional adoption.
One synthetic world across four Max engines
The published Exposure Traversal, Sensor Fusion, Shock Compiler and Evidence Output records now read the same signed fixture release. The shared-world certificate verifies one release identity, non-conflicting object digests, one rights position, compatible time boundaries and exact coverage denominators; the traversal record exposes the bounded typed-edge path that the joined outputs reference.
Both artifacts are fixed synthetic L0 conformance vectors. Agreement is not accuracy, and neither artifact claims a real event, entity, source, right, dependency, exposure, propagation, forecast, causation, advice, production release, external utility or adoption.
Normative downloads
- Machine profile 0.1.0 — exact validator, schema-registry, specification and test-vector hashes.
- Adversarial case registry — eleven expected pass/refusal outcomes.
- Normative draft specification.
- Canonical release schema, EvidenceItem, Entity, Event, UniverseRelease and ExposureEdge; plus the availability receipt, replay ledger and replay output schemas for the synthetic knowledge-time foundation; and the Sensor Fusion output schema for semantically separated multi-lane collation; and the Exposure DNA output schema for non-scalar snapshots and release-to-release deltas; plus the bounded scenario input schema and Shock Compiler output schema; and the four-product evidence output schema; plus the bounded exposure-traversal schema and shared- world certificate schema.
What a pass means
A pass licenses only this narrow statement: the supplied release conforms to OGES public draft 0.1.0 under the profile and test vector named in its report. It does not establish substantive truth, legal correctness of a signed rights decision, empirical independence of providers, causal attribution, forecast accuracy, comprehensive event coverage or endorsement by IGRM or any public institution.
The deterministic fixture keys are intentionally public test keys and must never be placed in a production trust registry. Production releases need independently controlled signer keys, real signed rights decisions and substantive review. The specification, machine profile, synthetic vectors and reference code are available under the repository's MIT License; reuse or conformance does not imply endorsement.
Measurement methodology · Knowledge replay · Sensor Fusion · India Exposure DNA · Shock Compiler · Data codebook · Corrections · Open data