Skip to content

DIO/ODI Reference Model v0.6.0

Choose a tag to compare

@dan-beranek dan-beranek released this 05 Nov 00:27
· 395 commits to main since this release
2d68ec0

This release archives the accumulated DIO/ODI Reference Model repository state since v0.5.0, not only the newly added Agentic ER mapping. It includes intervening updates to existing RAG, HEM, and Commit-Boundary × Policy-as-Code mappings; metadata registries; vocabulary serializations and reference metadata; web frontends, indexes, and machine-readable discovery files.

Agentic ER Commit-Boundary Architecture Mapping v0.3.0

Aligned with production manuscript v55 (4 November 2026), prepared for arXiv v2.

  • 120 local architecture concepts.
  • 206 qualified relation assertions, each with source-section provenance, an interpretation note, and an epistemic status.
  • Markdown, JSON-LD, and Turtle/RDF representations.
  • HTML frontend and SVG architecture overview.
  • Explicit action classes: READ, STAGE_LOCAL, REVERSIBLE_WRITE, and IRREVERSIBLE_WRITE.
  • Action-specific version binding, staging isolation, atomic version comparison, and provisional shadow staging.
  • Separate mutation-independent evidence-admission and mutation-specific claim-conflict checks.
  • Versioned quarantine disposition, fresh admission before release, and restrictions on changes to authorization-eligibility metadata.

Architecture mapping: https://vocab.danielberanek.cz/mappings/agentic-er-architecture/

The mapping is a non-normative, derived analytical layer. It reuses canonical DIO/ODI identifiers while keeping paper-specific constructs in a separate namespace. It does not modify Reference Vocabulary v0.2.0 and does not claim implementation, formal proof, or empirical validation.

Version scope

  • Reference Model: v0.6.0
  • Agentic ER Architecture Mapping: v0.3.0
  • Canonical Reference Vocabulary: v0.2.0 (unchanged)
  • Previous archived Reference Model release: v0.5.0 — https://doi.org/10.5281/zenodo.23643845

Zenodo will assign a version-specific DOI when the GitHub release is archived. The live repository metadata will be synchronized with the minted DOI after the archive is created.