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.
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.
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 · Data codebook · Corrections · Open data