Changelog

Release v1.3.0, Specification reading path 1.0 2026-09-17

• GitHub Release v1.3.0 published on 17 September 2026 (2026-09-17T09:27:34Z) from an SSH-signed annotated tag on commit 8235b85, with three signed assets (OCOM-v1.3.0.zip, SHA256SUMS, SHA256SUMS.sig): Constitution 1.0.1, Core Vocabulary 0.1 (13 governed terms), Specification 1.0. It is the Release to cite.
• Specification reading path 1.0: the nine chapters recompiled on 17 September 2026 against the canonical documents as they stood that day, each with a Revision History and a Source line naming what changed. Chapter 1 carries Core/Manifest.md's sections verbatim, including the whole Normative Language section; Chapters 3 and 4 add Organization to the specializations of Object; Chapter 5 compiles the CAND-016 specialization sentence for Relationship; Chapter 6 is restated from its sources and no longer calls the Domains and Entities sections non-normative; Chapter 8's Purpose follows Language/Conformance.md. The 22 July 2026 Committee Review Package keeps its v0.2 record with a dated postscript.
• This site: the Specification pages, specification.md and specification.json are regenerated from the v1.0 chapters at commit 8235b85; the term-card projections are unchanged, since no Meta definition changed.
• Zenodo version DOI 10.5281/zenodo.22809694, under the concept DOI 10.5281/zenodo.21510450, minted by the Zenodo GitHub integration from the repository's .zenodo.json; the Release body is the record description.
• Correction, appended rather than edited: eight surfaces still described the reading path as v0.2 after this Release (home page, attribution, evolution, why, how-to-review, llms.txt, discovery.json, .well-known/ocom.json); they now say v1.0, and the evolution record carries the v1.0 entry from the canonical ROADMAP.md.

Release v1.2.0, the first content Release with signed assets 2026-09-16

• GitHub Release v1.2.0 published on 16 September 2026 from an SSH-signed annotated tag on commit e4a5a53: Constitution 1.0.1, Core Vocabulary 0.1 (13 governed terms), Specification 0.2. The first content Release over v1.1.1 and the first cut with a signed tag and three signed assets (OCOM-v1.2.0.zip, SHA256SUMS, SHA256SUMS.sig); verification commands are in the repository's SECURITY.md. It is the Release to cite.
• Zenodo version DOI 10.5281/zenodo.22807178, under the concept DOI 10.5281/zenodo.21510450, minted on 17 September 2026 by the Zenodo GitHub integration from the repository's .zenodo.json after the publication-day webhook deliveries failed on Zenodo's side and the release event was repeated by hand; resource type Standard, CC BY 4.0, author bound to ORCID, the Release body as the record description.
• Canonical repository since the last entry: the Master Architecture Backlog's Part 8 bar, OCOM Specification v1.0 Ready, met on its recorded terms on 16 September 2026. Terminology 0.2 restated as a verbatim index of canonical definitions; CAND-001 decided (the Context duplicate replaced with a pointer); every Entity document bridged to Memory and the Domains linkage dispositioned; CAND-016 decided (Meta/Relationship.md canonical, Models/Relationship.md its specialization for Entities); the reading path re-pointed to the Constitution and Chapter 4 completed with Organization; CAND-002 decided and integrated (Profile Conformance as a claimant's declaration); a Conformance Test Suite specification with the Requirement Register as a derived projection, 335 statements across the 22 documents Chapters 4 to 6 compile. AO-062 to AO-068 recorded; AO-001, AO-002, AO-065, AO-066 and OBS-001 closed. The Specification track label stays 0.2.
• Not in this Release: the World Model document (Layer 2 of CAND-014) and the AI/Knowledge rewrite, gated behind the Architecture Freeze pipeline; the Test Suite tooling and the profile declaration validator, specified and not built. The site's term-card projections are unchanged, since no Meta definition changed; the Specification reading-path pages are behind the repository for Chapters 0, 1, 4, 7 and 8 until regenerated.

Release v1.1.1, the first citable Release 2026-09-12

• GitHub Release v1.1.1 published on 12 September 2026 from an annotated tag on commit 91d40db: Constitution 1.0.1, Core Vocabulary 0.1 (13 governed terms), Specification 0.2. The first Release cut per Governance/Release-Workflow.md, with its Publication-Manifest.md entry recorded before the tag. It supersedes v1.0.0 in scope and is the Release to cite.
• Zenodo version DOI 10.5281/zenodo.22724309, under the concept DOI 10.5281/zenodo.21510450, minted by the Zenodo GitHub integration from the new .zenodo.json in the repository: resource type Standard, CC BY 4.0, author bound to ORCID, 14 subjects, the Release body as the record description. DataCite lists the record as findable.
• v1.1.0, published the same morning through the GitHub Release form, was rejected by Zenodo: CITATION.cff listed two licences where Zenodo's citation reader accepts one. It is recorded as Superseded in Publication-Manifest.md and carries no DOI; the tag and the release are left as published. CITATION.cff now names CC BY 4.0, the licence of the specification text; the repository outside docs/ stays Apache-2.0.
• Canonical repository since the last entry: Constitution 1.0.1 (Principles 9 and 11 transcribed from their recorded interpretations), CAND-014 and CAND-015 decided, AO-059 to AO-061 recorded from the first external practitioner review. The site's projections were unchanged by these; the Specification reading path stays at 0.2.

Projection fidelity: the graph, the resolver, the API contract 2026-09-07

• The JSON-LD graph was a lossy projection. It carried the 83 references between Core Vocabulary terms but dropped the aspect label on each, and it omitted the seven concepts the specification references and does not define as terms, so a machine reading only that endpoint saw a closed vocabulary with no gaps. It now carries the same 83 references as typed nodes with the aspect where the canonical source has one, and publishes the seven referenced concepts explicitly, each with where it is defined and a link to its resolver record.
• The Knowledge API states that every url and record value in v1 is absolute. The 39 explain records returned a relative url; they now return absolute values. The convention itself was over-stated: machineResources.source and machineResources.history point into the canonical repository on GitHub, and the manifest now says so instead of claiming every value is rooted at base.
• The Concept Candidate Queue was published at two URLs whose explanatory note disagreed, because a correction reached one representation and not the other. The api/v1 copy is rebuilt from the same record and now carries the corrected note and the ownership pointer.
• Three identifiers this site prints did not resolve: the Russian projection of the Reference Case, the Identifier Resolver registry itself, and the Specification reading-path record. All three are registered and answer on both resolver surfaces. The registry holds 79 identifiers.
• The published Resolver coverage check asserted that no identifier this site prints answers with not found, while testing only the identifiers already registered. The rule now states what it tests, and a second check was added that harvests the identifiers actually printed on the published surfaces and compares them against the registry.
• The Ownership coverage check claimed every governed record points at the Ownership assignment. 30 of 191 published JSON records carry the pointer. The rule now says that, rather than asserting a coverage the check does not measure.
• 22 pages did not state which Publication-Model tier they belong to. All 69 published pages now do.
• A client asking /explain for an unknown identifier received an HTML page, and the empty identifier returned an HTML page under an application/json content type. Both now answer with the API's own JSON error. An error body no longer says not found for a status that is not 404.
• The extensionless form of nine canonical records served neither the JSON charset nor the CORS header its .json twin served. Markdown projections and llms.txt, declared as machine peers, carried no CORS header. Both are corrected.
• The Russian projection of the Reference Case described it in its schema.org block as a fictional organization for illustration only, while its own visible text, its meta description, the English projection and the Evidence Register all state that the rollouts are real and were conducted under NDA with the organization and details changed. The machine-facing half was the wrong one, and it is corrected to match the record.
• The Observatory metric labelled Publication coverage measured the share of the 13 Core Vocabulary terms with all four projections, never the share of the specification that is published, and the label invited the wrong reading. It is renamed Core Vocabulary projection coverage on the page and coreVocabularyProjectionCoverage in health.json; the old key is retired with a note, the value and its definition are unchanged.
• Fourteen pages that carry noindex were also submitted in sitemap.xml. They are removed from the sitemap and remain listed in the machine discovery files.
• Found by pointing agents at the live endpoints rather than at the pages, before publication. Recorded here because a projection that silently loses data, and a check that asserts more than it tests, are the two failures this specification exists to name.
• Correction, appended rather than edited: the point above about /explain overstated the empty-identifier case. /explain/ redirects to the explain page rather than answering with the JSON error, and that redirect no longer carries a JSON content type; the unknown-identifier case answers with the JSON error as stated. Corrected the same evening: the /resolve page, llms.txt and the Observatory table had not been regenerated after the registry grew to 79 identifiers and the health rules were rewritten, so three human-facing surfaces printed 76, 152 and 29 against records saying 79, 158 and 30. They now render the records they name. The canonical repository was aligned with the published rendering of the Reference Case, the roadmap and the Executive Overview (commit 872f3c2): the site had corrected the provenance wording while the files it names as source still said fictionalized. The reading-path pages now say that dated editorial notes are marked as such rather than claiming the compilation is verbatim without qualification.

Dogfooding pass: the site applies its own rules to its own records 2026-09-06

• Correction, appended rather than merged, per Constitution Principle 4 (Memory is append-only; corrections are new entries, never modifications of historical records): the 21 July 2026 entry above was previously edited in place to describe the set as 13 terms. 12 terms were published on 21 July; Organization was added on 25 July 2026 per ADR CAND-005, bringing the set to 13. The 0.1 label did not change on either date, so it does not by itself distinguish the two sets, as Governance/Publication-Manifest.md records.

Reading frame, Evidence Register, concept coverage 2026-09-05

• How to Review page published at /specification/how-to-review: reading frame in English and Russian, nine review questions, and how to file an objection; the frame also opens llms.txt and the home page.
• Implementation Status restructured as the Evidence Register: verifiable, declared and absent evidence separated on a four-step ladder; /implementation-status redirects.
• Brand page reframed as Attribution and mark usage: citation guidance, and the badge becomes an attribution mark for published models that cite the vocabulary; /brand redirects.
• Roadmap page republished as the Evolution Record with its content unchanged; /roadmap redirects.
• Comparison matrices relabelled Concept coverage with a Covered / Partial / Out of scope scale; Master Data Management interoperability wording revised.
• Structured data: genre, open license and free access declared on the home page, Specification pages and term pages.
• Evidence Register: the count of organizations in evaluation removed as unverifiable. How to Review: reviewer guidance made descriptive rather than imperative, and the Architecture Committee disclosed as a review role held by the author at this stage.
• FAQ annex: 'What does adopting OCOM cost?' added, with the incremental adoption path from the Adoption guides; the Reference Case is described as distilled from real rollouts under NDA.
• Observatory: projection parity invariant added (HTML, JSON, JSON-LD and Markdown agree on version, identifiers and definitions), with explanations for the informational graph counts.
• Reading frame: the commercial exclusion shortened to one sentence on the home page, How to Review (EN and RU), llms.txt and the machine records; the home page notes where each of the four pillars is defined (AO-021, CAND-010).
• Comparisons index: method and coverage note (one structure by design; TOGAF, ITIL, ISO/IEC 42010 and event sourcing not yet compared). Implementation Case: the provenance paragraph now leads with the real rollouts under NDA. Governance roles (Chief Architect, CDKO, Architecture Committee) defined in the Governance Manifest and projected on How to Review.
• Machine records and Observatory clarified after an external logic audit: publication coverage defined as the 13 terms times four projections with the unprojected repository tiers listed; the unreproducible cycles count replaced by mutual reference pairs; Evidence described as reserved at the Memory tier; Governance named as the one candidate without a definition at any tier; the Knowledge API described as a publication interface; Chapter 1 source note and Chapter 8 editorial note (conformance adjectives) recompiled from the repository.
• Claim provenance pass: the Implementation Case machine records now carry the canonical sentence that the rollouts are real and conducted under NDA; the Governance gap cites AO-023 rather than a decided ADR Candidate; the definitions answer names both defining tiers; comparisons are described as site-published informative records rather than canonical ones, with Evidence, Governance and AI retrieval scored Partial and Workflow, Event and identity resolution no longer scored out of scope; term pages state which fields are projected and which are minted here; the release record names all four version tracks and the sole GitHub Release.

Specification rebuild, MDM comparison, JSON-LD cleanup 2026-09-04

• Specification pages rebuilt from the canonical nine-chapter v0.2 reading path (SPEC-00 to SPEC-08), compiled verbatim from docs/Specification/.
• Core Vocabulary term pages now carry the full canonical records, including the required/optional split of each term's characteristics where its record defines one.
• OCOM vs Master Data Management comparison (ninth); comparisons relabelled Informative.
• Graph JSON-LD context cleanup: references mapped to the OCOM vocabulary namespace, fully qualified types, validator-clean.
• Machine layer synchronized: resolver, discovery, Knowledge API records, sitemap.xml, llms.txt.

Public essay, Roadmap page, two comparisons 2026-09-02

• Essay "Your organization is not your software" published at /why.
• Roadmap page compiled from the canonical ROADMAP.md.
• ArchiMate and Domain-Driven Design comparisons (seventh and eighth).
• llms.txt expanded into a narrative entry point.

Adoption layer and Shape Check 2026-08-21

• Worked Example and First Pilot adoption pages (CAND-010, CAND-011, CAND-012).
• Shape Check concept-coverage tool published as a governed Consumer Tool (CAND-013).

Implementation Case and three comparisons 2026-08-12

• Implementation Reference Case published in English and Russian.
• Ontology, Data Model and Process Model comparisons (fourth to sixth).

Publication node ocom.uno 2026-08-03

• Specification reading path published as a projection of the canonical model (Executive, Normative, Informative Annexes), referencing the Vocabulary and defining nothing itself.
• Three structured Comparisons: Knowledge Graph, BPMN, Digital Twin.
• Knowledge Graph, Knowledge API, Retrieval Engine, Resolver, and the Knowledge Observatory (graph/publication health, map, inspectors).
• Machine-discovery layer: .well-known/ocom.json, discovery.json, knowledge-sitemap.json, graph.jsonld, sitemap.xml, robots.txt, llms.txt, URI and Citation registries.

Organization term (CAND-005) 2026-07-25

• Organization added to the Core Vocabulary as a first-class specialization of Object (ADR CAND-005, Option C); the vocabulary now has 13 terms.

Core Vocabulary v0.1 2026-07-21

• Initial public release of the OCOM Core Vocabulary: 12 governed terms, each a machine-authoritative record with HTML, JSON, JSON-LD and Markdown projections.