Open upper schema for normative content https://obligationfirst.org/ 2026-08-04T12:00:00Z Sam Rogers https://www.linkedin.com/in/samrogers CC BY 4.0 (spec) / Apache 2.0 (code) Obligation-First https://obligationfirst.org/releases/v0.6.3 2026-08-04T12:00:00Z 2026-08-04T12:00:00Z

Repairs public and agent discovery surfaces and adds deterministic link, feed, sitemap, and version-drift gates without changing v0.6 semantics.

https://obligationfirst.org/releases/v0.6.2 2026-08-04T12:00:00Z 2026-08-04T12:00:00Z

Hardens graph diagnostics, JSON-LD round trips, identifier continuity, and managed version metadata without changing v0.6 semantics.

https://obligationfirst.org/releases/v0.6.1 2026-08-04T12:00:00Z 2026-08-04T12:00:00Z

Corrects released-state drift across public and agent-facing surfaces and adds a deterministic packaged-release state gate.

https://obligationfirst.org/releases/v0.6.0 2026-08-04T12:00:00Z 2026-08-04T12:00:00Z

Implements the v0.6 semantic contract, deterministic migration, schema-and-graph conformance, and local projections for EveryAILaw, PubLedge, and AI Incident Law while preserving the v1 IRI major and a bounded legacy-record compatibility window.

https://obligationfirst.org/releases/v0.5.0 2026-07-25T12:00:00Z 2026-07-25T12:00:00Z

Adds the of:ObligationCategory layer for jurisdiction-neutral duty concepts, extends of:anchors to reference them, and lets adopter naming profiles declare a version range so additive releases stop being lockstep flag days. Additive; v0.4.x records and profiles stay valid.

https://obligationfirst.org/releases/v0.4.3 2026-07-05T12:00:00Z 2026-07-05T12:00:00Z

Patch: revert unintended v0.4.2 jurisdiction/ref pattern constraint that broke supranational adopter records; restores the v0.4.1 contract.

https://obligationfirst.org/releases/v0.4.2 2026-07-01T12:00:00Z 2026-07-01T12:00:00Z

Correctness patch: JSON-LD @context resolution, release-URL 404 fix, validators fail on missing dirs, plus schema-field and publishing-surface reconciliation.

https://obligationfirst.org/releases/v0.4.1 2026-06-09T12:00:00Z 2026-06-09T12:00:00Z

v0.4.1 is a documentation-consistency patch from an external semantic review: README license note reconciled with NOTICE, phantom gist:Court removed from schema annotations and the gist crosswalk, schema count corrected to nine, w3id resolution wording made truthful, version-narrative drift fixed, and the Colorado SB26-189 issuer corrected. No of: vocabulary change; v0.1 through v0.4.0 adopter records remain valid without migration.

https://obligationfirst.org/releases/v0.4.0 2026-06-03T12:00:00Z 2026-06-03T12:00:00Z

v0.4.0 defines the naming-profile format. The .well-known naming profile, a Level 2 requirement since v0.3 but previously specified only in prose, is now a concrete validatable standard: a JSON-LD of:NamingProfile document served at /.well-known/obligation-first-naming-profile.jsonld (application/ld+json) and validated by schema/naming-profile.schema.json, with a flat text/plain provenance sidecar at /.well-known/obligation-first-naming-profile-manifest.txt. Adds the schema, a worked profile under examples/naming-profiles/, the void prefix and profile terms in the context, and a validate:naming-profile CI gate. Closes a v0.3 freeze gate. Additive and non-breaking to adopter records.

https://obligationfirst.org/releases/v0.3.1 2026-06-02T12:00:00Z 2026-06-02T12:00:00Z

v0.3.1 makes every surface reflect the @id-federation model: record @id values are adopter-local, opaque, and permanent; standard identifiers (ELI, ECLI, Akoma Ntoso, Wikidata) ride as typed crosswalks; jurisdiction is a typed ISO 3166 field. All four worked examples were realigned to a neutral example namespace with crosswalks, conformance Levels 2 and 3 were redefined, and the binding handoffs were reconciled to live adopter data. The -draft version suffix is dropped from this release forward. No schema migration is required for adopters.

https://obligationfirst.org/releases/v0.2.2-draft 2026-05-30T12:00:00Z 2026-05-30T12:00:00Z

Security hardening release for Obligation-First v0.2.2-draft. Shared graph validation now rejects unanchored administrative Determinations, CI runs the full local contract suite, release and content hashes are enforced, and focused hardening regressions cover the confirmed bypass and false-positive controls. No schema vocabulary migration is required for adopters.

https://obligationfirst.org/releases/v0.2.1-draft 2026-05-26T12:00:00Z 2026-05-26T12:00:00Z

Patch draft release package for Obligation-First v0.2.1-draft, including a machine-readable manifest and SHA-256 checksum index for core public spec, schema, agent, LLM, and GuideCheck artifacts. v0.1 adopter records remain valid without migration.

https://obligationfirst.org/releases/v0.2.0-draft 2026-05-26T00:00:00Z 2026-05-26T00:00:00Z

Binding-only refinement built on v0.1: Semantic Arts feedback (Dave McComb, 2026-05-26) absorbed for the of:Reparation gist binding (now the layered gist:Requirement + gist:Intention + gist:Event pattern) and the of:Allegation gist binding (now gist:Content + gist:Intention; gist defines no gist:Statement). Defeasibility sub-types of:rebuts and of:undercuts added as subproperties of of:defeats per LegalRuleML §7.4. of:violationOf added as the symmetric/inverse predicate of triggers_on_violation_of. of:Reparation class is preserved for LegalRuleML 1:1 alignment and SPARQL queryability; v0.1 adopter records require no migration.

https://obligationfirst.org/releases/guidecheck-level-4-assistant-guide 2026-05-24T00:00:00Z 2026-05-24T00:00:00Z

Published a GuideCheck Human-Verifiable Assistant Guide for assistant-assisted Obligation-First repository work, with a Level 4 sidecar manifest at https://obligationfirst.org/.well-known/assistant-guide-manifest.txt. Conformance is a form and provenance check, not a safety claim.

https://obligationfirst.org/releases/v0.1.0-draft 2026-05-04T00:00:00Z 2026-05-04T00:00:00Z

Initial draft of the Obligation-First v0.1 specification. Four-role spine (Authority / Instrument / Term / Obligation) plus proceeding strand (Proceeding / Allegation / Determination). Bound to Semantic Arts gist. Aligned with LegalRuleML 1.0 deontic operators. Three worked examples: Air Canada, Colorado SB 24-205, Utah JIA. Schema gaps surfaced by Colorado example resolved in v0.1: enforcement_status, supersedes, wouldSupersede.