Map the world by obligation, not by text.

Bind your dataset (current draft: v0.6)

Adopters bind via JSON-LD @context. obligationfirst.org/v1/ is the live resolution target; w3id.org/of/v1/ is the planned permanent vocabulary prefix. Legacy v0.5 shapes remain schema-valid, while projections using v0.6 vocabulary migrate deterministically and declare obligation-first >=0.6.0 <0.7.0.

{
  "@context": "https://obligationfirst.org/v1/context.jsonld",
  "@type": "of:Instrument",
  "@id": "https://obligationfirst.org/v1/examples/colorado-evolution/instrument/predecessor",
  "title": "Colorado SB 24-205 predecessor, current-contract teaching representation",
  "operative_status": "unknown",
  "enforcement_status": "unknown",
  "computed_as_of": "2026-09-05",
  "describesSameEntityAs": [
    "https://obligationfirst.org/v1/examples/colorado-sb24-205/instrument/sb24-205"
  ]
}

# Each entity has a schema at /v1/schema/

curl https://obligationfirst.org/v1/schema/instrument.schema.json
curl https://obligationfirst.org/v1/schema/term.schema.json
curl https://obligationfirst.org/v1/schema/obligation.schema.json
curl https://obligationfirst.org/v1/schema/proceeding.schema.json

# Validate with any JSON Schema 2020-12 validator

Scope continuity evaluation

Scope evaluator v1 checks exact territorial and institutional identifiers against adopter-owned inventories and continuity baselines. Recognition, modeled coverage, uncovered scope, and unknown evidence remain distinct. It complements schema and fingerprint checks without changing the v0.6 record contract or certifying legal applicability.

Review the scope contract and diagnostics, inventory tooling schema, and synthetic evaluation fixtures. The deterministic evals cover scope substitutions, institutional and territorial confusion, lost specificity, and unknown evidence.

Implementation status beyond the release package

The v0.6.6 reference package includes scope continuity evaluation. F14 qualified-time evaluation is released offline reference tooling: expected/fallback branches and evidence/date boundaries are tested, while the v0.6 record schema and production serialization are unchanged. These fixtures do not determine legal applicability or predecessor operative history.

Operational federation reconciliation checks supplied source, projection, exact-edge and deployed-artifact evidence for EveryAILaw, PubLedge and AI Incident Law. EveryAILaw owns collection and scheduling; EveryAILaw Pro is a downstream service, not an adopter. Byte equivalence is not deployment attestation or proof that legal content is current. Independent missing-run notification and live recovery acceptance remain open. Operational reconciliation contract.

The machine-readable evaluation status supplements the release-versioned agent files. It describes implementation scope, not deployment acceptance. The F14 fixture contract defines the evidence boundaries and remaining work.

Three steps to bind a dataset

1. Reference the canonical @context — set @context: "https://obligationfirst.org/v1/context.jsonld" on every record. Repo-local extensions go in a second context object.
2. Validate shape and graph contracts — run every record through the schema for its Obligation-First @type, validate graph coherence and every emitted surface, and publish a .well-known naming profile.
3. Cite obligationfirst.org as the canonical reference — preserve record identifiers. The separate w3id vocabulary redirect remains pending.

Assistant-assisted setup

For assistant-assisted repository work, start with the GuideCheck artifact at /.well-known/assistant-guide.txt. Verify it with GuideCheck or another conformant verifier before the assistant acts. The Level 4 sidecar manifest is published at /.well-known/assistant-guide-manifest.txt. Conformance verifies form and provenance, not safety.

Conformance levels