v1 namespace

Stable URIs for the Obligation-First specification, currently on the v0.6.6 release line. Under the bind-by-major policy the /v1/ namespace serves the entire v0.x→1.x major, so records bound today keep resolving as the spec advances toward 1.0. The v0.6 contract is implemented and published across EveryAILaw, PubLedge, and AI Incident Law. Adopters fetch the context at https://obligationfirst.org/v1/context.jsonld; terms already expand under the permanent https://w3id.org/of/v1/ vocabulary prefix. Dereferencing those IRIs remains pending external redirect acceptance and live verification.

Vocabulary documentation

Browse all expanded terms and their context aliases. Term documentation is hosted here; the w3id contribution is prepared but not submitted.

JSON-LD context

• /v1/context.jsonld Canonical context. Adopters reference this URL in their records.

JSON Schemas

• /v1/schema/common.schema.json Shared v0.6 definitions used by entity schemas
• /v1/schema/authority.schema.json of:Authority
• /v1/schema/jurisdiction.schema.json of:Jurisdiction
• /v1/schema/party.schema.json of:Party
• /v1/schema/instrument.schema.json of:Instrument
• /v1/schema/term.schema.json of:Term
• /v1/schema/obligation.schema.json of:Obligation (Requirement / Restriction / Permission / Reparation)
• /v1/schema/obligation-category.schema.json of:ObligationCategory
• /v1/schema/proceeding.schema.json of:Proceeding
• /v1/schema/allegation.schema.json of:Allegation
• /v1/schema/determination.schema.json of:Determination
• /v1/schema/tombstone.schema.json of:Tombstone
• /v1/schema/executable-encoding.schema.json Polymorphic executable-encoding reference
• /v1/schema/naming-profile.schema.json Adopter .well-known naming profile (VoID uriSpace + RFC 6570 template + crosswalks)

Worked-example records

Five worked record sets round-tripped through the current draft, served as JSON for direct fetch and validation. The Colorado evolution companion is explicitly synthetic and evidence-bounded. Every record carries a neutral https://obligationfirst.org/ identifier; where an example corresponds to a real adopter entity, that adopter's published IRI appears only as a crosswalk (via sameAs, describesSameEntityAs, or anchors), never as the record's own @id. GitHub Pages serves no directory listings, so each link below resolves to one concrete record; browse the rest of a set from its README.

Browse the worked-example index for the published record inventory and validation context.

• colorado-sb24-205/records/authority-co-general-assembly.json 13 records - Colorado AI Act, three-layer reality
• colorado-evolution/records/instrument-co-sb26-189-successor.json 2 records - synthetic current-contract succession with unknown operation and enforcement
• air-canada/records/authority-bccrt.json 8 records - Moffatt v. Air Canada, Parties and common-law recognition
• publedge-jia-utah-72/records/authority-us-ut-oaip.json 4 records - Utah OAIP JIA contractual Term
• eu-ai-act-article-50/records/authority-eu-commission.json 26 records - EU AI Act Article 50 transparency obligations

Set READMEs on GitHub: colorado-sb24-205, colorado-evolution, air-canada, publedge-jia-utah-72, eu-ai-act-article-50.

Source-of-truth links

• PROTOCOL.md The specification
• reference/crosswalks/ gist, LegalRuleML, Akoma Ntoso, ELI/ECLI
• CHANGELOG.md Version history
• /.well-known/assistant-guide.txt GuideCheck Human-Verifiable Assistant Guide for assistant-assisted repo work
• /.well-known/assistant-guide-manifest.txt GuideCheck integrity sidecar manifest