A curated, append-only record of documented changes to the conceptual model, vocabulary, mappings, provenance, and archived reference artifacts. Each record states what changed, what was preserved, why the date is used, and where the evidence comes from.
44documented records · v0.1.0
25 Mar 2026earliest Changelog milestone
07 Nov 2026latest publication represented
Read the feed
The feed covers the complete dated Changelog on the DIO/ODI Hub and extends the chronology with later Reference Model, vocabulary, and mapping milestones. It is not a Git commit log: Hub Changelog dates, activity periods, first archival inclusion, publication dates, and archive dates are explicitly distinguished.
Showing 44 of 44 records
SCF-2026-044
The DIO-to-DIO portfolio adds its eleventh model-specific analysis by Claude Sonnet
Distribution
The public portfolio expands from ten to eleven author-led analyses with Claude Sonnet 5.5 (Extra Effort). The report examines reconstruction resilience across web, archival, machine-readable, multilingual, and identity-linked representations. Its section on strains and materiality distinguishes structural susceptibilities and documented state differences from demonstrated reconstruction failures; these remain Claude's model-specific analytical findings, not harmonized portfolio conclusions or authoritative historical evidence.
DateChange publishedDate basis publication date
ScopeDIO-to-DIO research portfolio — Claude analysis
Previous state
The public portfolio contained ten author-led, model-specific reconstruction analyses, as recorded at its initial publication milestone in SCF-2026-042.
Resulting state
Eleven analyses are publicly available. The Claude Sonnet 5.5 report is listed with its Markdown and PDF source files and a generated HTML representation; its observation snapshot is 6–7 November 2026.
Preserved invariants
SCF-2026-042 remains the accurate record of the portfolio's initial publication with ten analyses on 6 November 2026; this event appends the subsequent expansion and does not rewrite that history.
The portfolio remains author-led: the author defines and directs the research, while each model contributes a distinct analytical reading.
The reports remain model-specific and are not harmonized, ranked, or synthesized; Claude's materiality judgments and graph results are not promoted to portfolio-wide conclusions.
The report's observation snapshot (6–7 November 2026) is distinct from the portfolio publication/deployment date (7 November 2026).
The report's observations are discovery and interpretation material, not primary historical authority; claims adopted as SCF history require verification against primary publications, registries, release records, or archives.
The portfolio addition does not modify the canonical Reference Vocabulary, Application Mappings, or archived Reference Model releases.
Impact distribution · distribution only This is a portfolio distribution update. The report's section 8 provides a model-specific, task-relative materiality assessment and explicitly reports no established realized reconstruction failure or measured observer outcome within its inspected evidence.
Date is the successful GitHub Pages deployment on 7 November 2026 (workflow run 42414438200). The Claude report records an observation snapshot of 6–7 November 2026; that snapshot is not used as the portfolio publication date.
SCF-2026-043
Reference Model v0.7.0 preserves the updated reference-system snapshot
Artifact
Reference Model v0.7.0 is archived with Reference Vocabulary v0.2.1 and Agentic ER mapping v0.3.1.
DateChange archivedDate basis archive publication date
ScopeReference Model v0.7.0
Previous state
The preceding archived package was v0.6.0, containing vocabulary v0.2.0 and Agentic ER mapping v0.3.0.
Resulting state
A new immutable package snapshot records vocabulary v0.2.1 and Agentic ER mapping v0.3.1.
Preserved invariants
Earlier releases remain immutable and identifiable; the archive alone is not evidence of a new theoretical claim.
Impact archive · archive only The component-level changes are separately recorded in their own events.
Date is the recorded publication date of Reference Model v0.7.0 in the Corpus Metadata Registry and public release history. This event is not part of the Hub Changelog, which ends on 25 October 2026.
SCF-2026-042
The DIO-to-DIO research portfolio publishes ten model-specific reconstruction analyses
Distribution
The public DIO to DIO portfolio brings together ten author-led analyses of how different LLMs reconstruct and examine the DIO/ODI ecosystem. The reports retain model-specific observation boundaries, interpretations, graph models, and conclusions; the portfolio does not harmonize, rank, or synthesize them. The public site exposes the original Markdown and PDF reports alongside generated HTML representations.
DateChange publishedDate basis publication date
ScopeDIO-to-DIO research portfolio
Previous state
The analyses existed as individually produced model-specific research reports but had not yet been published together through a common public portfolio.
Resulting state
Ten reports by Brave AI, ChatGPT, DeepSeek, Gemini Deep Research, Gemini Pro Latest, Leo AI, Lumo, Mistral, Qwen, and Grok are available through a common public catalogue.
Preserved invariants
The project is author-led: the author defines and directs the research; the models contribute distinct analytical readings.
The reports are not harmonized, ranked, or synthesized; their observation boundaries, graph approaches, and conclusions remain report-specific.
The public deployment date is not treated as the generation or observation date of every report; the catalogue retains each report's own observation snapshot.
The portfolio does not modify the canonical Reference Vocabulary or validate the historical claims made in an individual report.
Impact distribution · distribution only This is a public research and distribution milestone. Individual model analyses are treated as discovery and interpretation sources; historical claims adopted by the SCF must be verified against primary publications, registries, release records, or archives.
Date is the successful public GitHub Pages deployment date (6 November 2026). Individual reports have their own observation snapshots, mostly 30 October 2026 and, for Grok, early November; those dates are not replaced by the portfolio publication date.
SCF-2026-041
Agentic ER mapping v0.3.1 synchronizes provenance with arXiv v2
Provenance
The live Agentic ER Architecture Mapping synchronizes provenance and source anchors to public arXiv v2. The mapping's local concept and relation inventories remain unchanged.
DateChange synchronizedDate basis first archival inclusion
ScopeAgentic ER Architecture Mapping v0.3.1
Previous state
Mapping v0.3.0 was aligned to production manuscript v55 and archived in Reference Model v0.6.0.
Resulting state
Mapping v0.3.1 synchronizes provenance to public arXiv v2 and is included in Reference Model v0.7.0.
Preserved invariants
120 local architecture concepts are retained.
206 qualified relation assertions are retained.
The mapping remains derived and non-normative; canonical vocabulary is unchanged.
Impact mapping · provenance only This is a provenance-only synchronization, not a change to the architecture's concept or relation inventory.
Date marks first archival inclusion of mapping v0.3.1 in Reference Model v0.7.0 on 6 November 2026. The archived v0.7.0 JSON-LD declares schema:dateModified as 2026-11-06. The arXiv v2 publication date is 5 November and is recorded separately; no exact source-edit time is asserted.
SCF-2026-040
Reference Model v0.6.0 preserves the mapping v0.3.0 archive state
Artifact
Reference Model v0.6.0 is archived as the package snapshot containing Agentic ER mapping v0.3.0 and Reference Vocabulary v0.2.0.
DateChange archivedDate basis archive publication date
ScopeReference Model v0.6.0
Previous state
The preceding archived package was v0.5.0.
Resulting state
The v0.6.0 archive captures the coordinated architecture mapping v0.3.0 and vocabulary v0.2.0 state.
Preserved invariants
The later live mapping v0.3.1 and vocabulary v0.2.1 do not rewrite this immutable package snapshot.
Impact archive · archive only The archive is a package snapshot; its component versions are distinct from later live versions.
Date is the recorded publication date of Reference Model v0.6.0 in the Corpus Metadata Registry and public release history. This event is not part of the Hub Changelog, which ends on 25 October 2026.
SCF-2026-039
Agentic ER Architecture Mapping v0.3.0 formalizes the Commit-Boundary architecture
Mapping
The first archived version of the DIO/ODI-informed Agentic Entity Resolution Commit-Boundary Architecture Mapping formalizes the architecture's internal conceptual and functional relations in a derived, non-normative layer. The v0.3.0 snapshot contains 120 local architecture concepts and 206 qualified relation assertions and is included in Reference Model v0.6.0.
DateChange introducedDate basis first archival inclusion
ScopeAgentic ER Architecture Mapping v0.3.0
Previous state
The Commit-Boundary paper had proposed the authorization guardrail, but the coordinated machine-readable relational mapping had not yet appeared in an archived Reference Model package.
Resulting state
Mapping v0.3.0 provides the first archived formalization of the paper's internal conceptual and functional relations and is included in Reference Model v0.6.0.
Preserved invariants
The mapping is derived and non-normative; it does not modify the canonical Reference Vocabulary.
Its 120 local concepts and 206 qualified relations describe the paper-specific architecture rather than adding canonical DIO/ODI concepts.
The existence of the mapping does not establish implementation, formal proof, or empirical validation.
Impact mapping · non normative derived layer This records the first archival inclusion of the mapping. Its metadata declares a creation date of 3 November 2026; the exact source-edit timestamp is not asserted.
Date marks first public archival inclusion in Reference Model v0.6.0 on 5 November. The archived v0.6.0 mapping JSON-LD separately declares schema:dateCreated as 3 November 2026; the date of first inclusion is not treated as the exact creation timestamp.
SCF-2026-038
Constraining the Commit Boundary v2 is published on arXiv
Artifact
The second version of the commit-boundary paper is made publicly available on arXiv. The Corpus Metadata Registry records v2 as the current arXiv version and retains the Zenodo version-1 record.
DateChange publishedDate basis version publication date
ScopeConstraining the Commit Boundary — arXiv v2
Previous state
The paper's Zenodo version 1 record was available as the first archived publication state.
Resulting state
arXiv v2 becomes the current public arXiv version; the Zenodo v1 record remains identifiable as an earlier version.
Preserved invariants
The work identity remains the same across the versioned publication records.
The commit-boundary architecture remains a conceptual authorization guardrail; publication alone does not assert implementation or empirical validation.
Impact provenance · provenance only This is a publication-version and distribution milestone. The mapping synchronization is recorded as a separate event.
Vocabulary v0.2.1 synchronizes creator identity, Dublin Core and namespace metadata, and DCAT/Schema.org descriptions across representations.
DateChange synchronizedDate basis version publication date
ScopeReference Vocabulary v0.2.1
Previous state
Vocabulary v0.2.0 carried the preceding metadata graph and representation state.
Resulting state
Vocabulary v0.2.1 uses the canonical Person URI and synchronized creator, license, issue/modification, language, namespace, FOAF, DCAT 3, and Schema.org Dataset metadata.
Preserved invariants
All 40 SKOS concepts, URIs, labels, definitions, notes, hierarchy, and provenance statements are preserved.
The historical status of Entity Resolution Anomaly is unchanged.
Archived Reference Model v0.6.0 remains an immutable snapshot containing vocabulary v0.2.0.
Impact metadata · metadata only The release notes explicitly identify v0.2.1 as metadata-only; no concept-level semantic change is claimed.
Date is the recorded release date of Reference Vocabulary v0.2.1 in its release notes and the Corpus Metadata Registry. It is not a Hub Changelog date.
SCF-2026-036
Reference Model v0.5.0 archives vocabulary v0.2.0 and the expanded mapping set
Artifact
Reference Model v0.5.0 is archived with Reference Vocabulary v0.2.0 and the expanded Application Mappings state. The preceding v0.4.0 archive preserves vocabulary v0.1.0.
DateChange archivedDate basis Hub Changelog date
ScopeReference Model v0.5.0
Previous state
The prior v0.4.0 package preserved the earlier vocabulary v0.1.0 state.
Resulting state
The v0.5.0 archive captures vocabulary v0.2.0 and the updated derived mapping package.
Preserved invariants
The archived v0.4.0 remains immutable and identifiable as the earlier vocabulary state.
Impact archive · archive only This is a package archival milestone and must not be confused with the concept introduction itself.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-035
Reference Vocabulary v0.2.0 introduces the plural Identity-Preserving Constraints concept
Conceptual
Vocabulary v0.2.0 introduces a distinct canonical plural concept Identity-Preserving Constraints and retains the singular Identity-Preserving Constraint as a historical entry.
DateChange introducedDate basis Hub Changelog date
ScopeIdentity-Preserving Constraints
Previous state
The prior vocabulary included the singular Identity-Preserving Constraint entry.
Resulting state
A distinct plural concept is introduced with its own URI; the singular entry is retained for historical traceability.
Preserved invariants
Earlier singular URIs are not retroactively migrated, and no semantic relation between singular and plural concepts is asserted.
Impact vocabulary · model level This is the date stated by the Changelog. The previous draft incorrectly assigned this event to 10 October.
Date is the recorded publication date in the Corpus Metadata Registry.
SCF-2026-033
The RAG Application Mapping gains an iterative evidence-acquisition extension
Mapping
The RAG mapping is extended with iterative, hypothesis-conditioned evidence acquisition; this extension is first included in archived Reference Model v0.4.0.
DateChange extendedDate basis first archival inclusion
Date identifies the first archival inclusion in Reference Model v0.4.0; the exact source-edit timestamp is not asserted.
SCF-2026-032
The Commit-Boundary Contract is mapped to Policy-as-Code authorization
Mapping
A new Application Mapping connects authorization commitments in Constraining the Commit Boundary with the capabilities and limits of OPA/Rego and Cedar.
DateChange introducedDate basis Hub Changelog date
The paper had specified the authorization architecture without this dedicated Policy-as-Code comparison.
Resulting state
The mapping relates the authorization decision to evidence validation, persistent-write enforcement, policy freshness, state consistency, and auditability.
Preserved invariants
The mapping does not claim that OPA or Cedar independently implements the complete contract; it does not extend the canonical vocabulary.
Impact mapping · non normative derived layer This is an application mapping, not an implementation report.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-031
Constraining the Commit Boundary introduces a DIO/ODI-informed authorization guardrail
Theoretical
The paper develops a conceptual architecture for authorization of persistent identity changes in Agentic Entity Resolution, separating evidence available for agent reasoning from evidence eligible to authorize a specific identity or continuity claim.
DateChange introducedDate basis Hub Changelog date
ScopeConstraining the Commit Boundary
Previous state
DIO/ODI had application mappings for RAG and HEM but had not yet published this commit-boundary authorization architecture.
Resulting state
A commit-time authorization guardrail is specified with operational scope and current state/policy conditions.
Preserved invariants
The paper is a conceptual architecture; publication does not imply implementation, formal proof, or empirical validation.
Impact conceptual model · model level The wider hypothesis-conditioned agentic cascade is explicitly left as future research.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-030
Reference Model v0.3.2 preserves the new corpus metadata infrastructure
Artifact
Reference Model v0.3.2 is published as a versioned package snapshot containing the Corpus Metadata Registry, ordered keyword grammar, and expanded publication and distribution metadata.
DateChange archivedDate basis version publication date
ScopeReference Model v0.3.2
Previous state
Reference Model v0.3.1 preserved the expanded Application Mappings representation layer.
Resulting state
The v0.3.2 package preserves the subsequent corpus-metadata and ordered-keyword infrastructure while retaining the Reference Vocabulary at v0.1.0.
Preserved invariants
The archived package is an immutable snapshot.
The Reference Vocabulary remains v0.1.0; the registry does not silently alter its concept definitions or relations.
Impact archive · archive only The archive preserves the package state in which the metadata registry and keyword grammar were introduced.
Date follows the public v0.3.2 release record; the Zenodo DOI identifies its versioned package snapshot.
SCF-2026-029
Reference Model v0.3.2 introduces the Corpus Metadata Registry and ordered keyword grammar
Provenance
Version 0.3.2 introduces a canonical corpus-level metadata registry for works, relations, references, and distribution representations, together with an ordered C0–C6 keyword grammar. It also expands structured Zenodo metadata and normalizes verified distribution relations, making the DIO/ODI corpus and its distribution relationships explicitly reconstructable.
DateChange introducedDate basis version publication date
ScopeCorpus Metadata Registry and keyword grammar
Previous state
The Reference Model contained the canonical vocabulary and derived Application Mappings, but did not yet expose the later consolidated registry for work identities, inter-work relations, references, and distribution representations.
Resulting state
The repository includes a dedicated operational metadata layer and a canonical ordered keyword grammar, separate from the Reference Vocabulary.
Preserved invariants
The canonical Reference Vocabulary remains at v0.1.0; registry metadata does not redefine SKOS concepts.
Typed distribution and inter-work relations preserve distinctions between versions, concept identifiers, canonical works, and distribution copies.
The registry is an operational metadata layer, not a replacement for the canonical vocabulary.
Impact metadata · metadata only This is an infrastructure and provenance milestone; the canonical vocabulary's concepts and semantic relations are not changed by the registry.
Date is the public Reference Model v0.3.2 release date. The versioned release and registry documentation establish the metadata-infrastructure milestone.
SCF-2026-028
Reference Model v0.3.1 preserves the expanded machine-readable mapping layer
Artifact
Reference Model v0.3.1 is published as a versioned package snapshot containing the enriched Application Mappings representations and qualified mapping assertions.
DateChange archivedDate basis version publication date
ScopeReference Model v0.3.1
Previous state
Reference Model v0.3.0 had established the Application Mappings layer with the first RAG and HEM mappings.
Resulting state
The v0.3.1 package preserves the subsequent RDF/JSON-LD representation and qualified-assertion state.
Preserved invariants
The package is an immutable versioned snapshot and does not replace the maintained repository.
The Reference Vocabulary remains v0.1.0 in this release.
Impact archive · archive only The archive fixes a package state; the mapping-layer extension itself is recorded separately.
Date follows the public v0.3.1 release record. The Zenodo DOI identifies the corresponding versioned package; no source-control commit time is inferred.
SCF-2026-027
Reference Model v0.3.1 enriches the machine-readable Application Mappings layer
Mapping
The v0.3.1 release extends the existing RAG × DIO and HEM × DIO mappings with qualified MappingAssertion resources, explicit skos:definition and skos:scopeNote descriptions, and non-deterministic relation types. It adds Turtle/RDF representations for both mappings and a JSON-LD representation for RAG, improving machine-readable interpretation without changing the canonical vocabulary.
DateChange extendedDate basis version publication date
ScopeApplication Mappings v0.3.1
Previous state
The v0.3.0 layer had introduced the RAG and HEM mappings and their human-readable representations, but not the full qualified assertion and RDF/JSON-LD representation set recorded in v0.3.1.
Resulting state
The mapping layer exposes qualified analytical assertions and additional machine-readable serializations, while explicitly avoiding deterministic causal or taxonomic-equivalence claims.
Preserved invariants
The canonical Reference Vocabulary remains at v0.1.0.
Mapping relations do not assert deterministic causality, entailment, or taxonomic equivalence.
Impact mapping · non normative derived layer A representational and interoperability extension to existing mappings; it does not add canonical vocabulary concepts.
Date is the public Reference Model v0.3.1 release date. The associated archived package is identified by its version-specific Zenodo DOI.
SCF-2026-026
The DIO Conceptual Framework is revised and republished as v1.1.0
Artifact
Version 1.1.0 provides a revised academic presentation of the paper first published on 7 August 2026. The conceptual argument and substantive claims remain unchanged; the revision adds complete author and affiliation metadata, ORCID, contact and publication details, canonical keywords, a table of contents, pagination, and standardized academic formatting, and replaces a non-verifiable reference with a verifiable source.
DateChange publishedDate basis version publication date
ScopeDIO Conceptual Framework v1.1.0
Previous state
The first public version (v1) had been published on 7 August 2026.
Resulting state
A versioned academic presentation v1.1.0 is published on 11 October 2026, with improved bibliographic and publication metadata while retaining the substantive conceptual argument.
Preserved invariants
The conceptual argument and substantive claims remain unchanged from the original paper.
The 7 August 2026 date identifies the original work; it is not the publication date of version 1.1.0.
Impact provenance · provenance only A publication-version and bibliographic-quality update, not a new conceptual formulation of DIO.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-024
The Application Mappings layer expands with HEM × DIO
Mapping
Reference Model v0.3.0 adds a distinct Application Mappings layer, including the Heterogeneous Entity Matching taxonomy × DIO Reconstruction Consequences mapping and human-readable frontends.
DateChange introducedDate basis Hub Changelog date
ScopeApplication Mappings layer and HEM × DIO mapping
Previous state
The repository had an initial RAG mapping but not the separately identified HEM × DIO mapping and broader Application Mappings index.
Resulting state
The derived Application Mappings layer expands to include HEM × DIO and its frontend representations.
Preserved invariants
Application mappings remain derived and non-normative; the HEM and DIO taxonomies are not treated as equivalent.
Impact mapping · non normative derived layer The HEM × DIO relation is analytical and many-to-many, not a claim of taxonomy equivalence.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-022
The first RAG Pipeline Application Mapping is created
Mapping
The first derived Application Mapping projects Reconstruction Failure Modes into a generic RAG pipeline while explicitly remaining separate from the canonical vocabulary.
DateChange introducedDate basis Hub Changelog date
The Reference Vocabulary and taxonomy existed without this published RAG application projection.
Resulting state
The first RAG mapping projects taxonomy concepts to RAG pipeline locations and diagnostic consequences.
Preserved invariants
The mapping is non-normative and does not redefine DIO as a RAG framework or modify canonical vocabulary concepts.
Impact mapping · non normative derived layer This corrects the prior draft's conflation of the initial 10 October mapping with a later iterative evidence-acquisition extension.
Date is the recorded publication date in the Corpus Metadata Registry.
SCF-2026-020
Reference Vocabulary v0.1.0 establishes the SKOS-first semantic layer
Artifact
The first Reference Vocabulary release establishes stable concept URIs, explicit definitions, conceptual relations, provenance, Turtle/RDF and JSON-LD representations, and a concept map.
DateChange publishedDate basis Hub Changelog date
ScopeReference Vocabulary v0.1.0
Previous state
The conceptual system was described in publications and prose without the first published SKOS-first reference layer.
Resulting state
A machine-readable SKOS-first vocabulary is published with stable identifiers and explicit semantic relations.
Preserved invariants
The vocabulary is the canonical semantic layer; later Application Mappings remain derived and separate.
Impact vocabulary · model level The Changelog date identifies the publication milestone for vocabulary v0.1.0.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-019
The Taxonomic Note reorganizes anomalies into Reconstruction Failure Modes
Structural
The Taxonomic Note reorganizes the original Entity Resolution Anomalies into a multi-level diagnostic taxonomy with Referential Reconstruction, Semantic Coherence, Temporal Reconstruction, and Contextual Adequacy branches.
DateChange reclassifiedDate basis Hub Changelog date
ScopeReconstruction Failure Modes taxonomy
Previous state
The initial Crisis paper used a four-anomaly framing.
Resulting state
A multi-level Reconstruction Failure Modes taxonomy is published; Identity Collapse remains outside it and Semantic Vulnerability is treated as a robustness-related property rather than a realized failure mode.
Preserved invariants
The taxonomy remains distinct from Identity Collapse.
Semantic Vulnerability is not classified as a realized failure mode.
Impact taxonomy · model level This is the formal taxonomic revision, not merely a visualization update.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-018
MVDIO introduces adversarial reduction and clarifies its relationship to the Semantic Connectome
Conceptual
MVDIO reduces DIO to a minimum analytical model, refines reconstruction-failure distinctions, reclassifies Semantic Vulnerability toward robustness/risk, and clarifies the relation between its coarse-grained minimum and the finer-grained Semantic Connectome.
DateChange refinedDate basis Hub Changelog date
ScopeMVDIO
Previous state
The Crisis-era account used a four-anomaly framing and had not yet made the relation between MVDIO's minimum analytical model and the Semantic Connectome explicit.
Resulting state
MVDIO provides an adversarially reduced analytical model and clarifies the relationship between its coarse-grained minimum and the finer-grained Semantic Connectome, while moving Semantic Vulnerability toward robustness/risk.
Preserved invariants
The Semantic Connectome is treated as a finer-grained candidate model, not as a logical consequence of MVDIO.
Impact conceptual model · model level This event captures the compound conceptual development as described in the MVDIO Changelog entry.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-017
The Crisis v1.1.0 record gains four supplementary visualizations
Artifact
The Crisis record is updated with four standalone visualizations corresponding to Identity Collapse, Semantic Fragmentation, Temporal Discontinuity, and Semantic Vulnerability.
DateChange extendedDate basis Hub Changelog date
ScopeThe Crisis of Entity Resolution v1.1.0
Previous state
The v1.0.0 primary text was published without these four supplementary visualizations.
Resulting state
The v1.1.0 record adds four conceptual visualizations as supplementary material.
Preserved invariants
The primary PDF text remains unchanged; the visualizations do not establish Semantic Vulnerability as a realized failure mode.
Impact metadata · archive only This is a supplementary representation update, not a claim that all four items belong to one final failure-mode taxonomy.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-016
The Crisis of Entity Resolution paper introduces four initial anomalies
Conceptual
The Crisis paper analyzes Entity Resolution in heterogeneous AI environments and identifies Identity Collapse, Semantic Fragmentation, Temporal Discontinuity, and Semantic Vulnerability.
DateChange introducedDate basis Hub Changelog date
ScopeThe Crisis of Entity Resolution
Previous state
The corpus had developed DIO/ODI and its first standalone conceptual paper but had not yet published this focused Entity Resolution analysis.
Resulting state
The Crisis paper publishes an initial four-part anomaly framing for Entity Resolution.
Preserved invariants
The four-item Crisis framing is a historical state; later publications refine the classification and separate Semantic Vulnerability from realized failure modes.
Impact conceptual model · model level The paper publishes an initial four-part anomaly framing. This is the historical starting classification; later publications refine it and separate Semantic Vulnerability from realized failure modes.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-015
DIO scoping defines its primary domain and exclusions
Conceptual
A scoping note defines DIO's primary concern as the semantic, representational, and relational aspects of digital identity, while naming domains outside its primary scope.
DateChange introducedDate basis Hub Changelog date
ScopeManifest hub — DIO scoping
Previous state
The primary subject and exclusions had not yet been explicitly recorded in a dedicated scoping note on the hub.
Resulting state
The scope note delineates the primary domain and explicitly excludes several adjacent identity domains from the primary object of DIO.
Preserved invariants
The scope note defines primary focus; it does not claim those excluded domains are unrelated to digital identity in general.
Impact conceptual model · model level A scope-boundary event, distinct from the provenance/methodology note on the same date.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-014
The Geneze DIO a ODI note articulates the framework's ex-post origin
Theoretical
A methodological note describes DIO/ODI as ex-post articulation of accumulated practice and operations formed during the creation of a multimodal E-E-A-T object.
DateChange documentedDate basis Hub Changelog date
ScopeManifest hub — Geneze DIO a ODI
Previous state
The Changelog had not yet explicitly documented the ex-post character of the framework's emergence.
Resulting state
The methodology note states the reflexive and ex-post origin of DIO/ODI and their openness to independent validation, falsification, and application.
Preserved invariants
This is a methodological articulation of genesis, not retrospective proof of validity.
Impact conceptual model · model level The record concerns explicit methodological framing as dated in the Changelog.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-012
Manifest v2 introduces the Semantic Connectome visualization and semantic-field analogy
Conceptual
The Czech and English Manifest v2 editions add a visualization of the Semantic Connectome as a complete graph K6 and interpret its relational structure through the working analogy of a semantic field. The Changelog also records a shift away from linear or sequential readings toward simultaneous interaction.
DateChange refinedDate basis Hub Changelog date
ScopeManifest v2 — semantic connectome and semantic-field analogy
Previous state
The earlier Manifest representation did not yet include the v2 connectome visualization and its interpretive supplement.
Resulting state
The Semantic Connectome is visualized as a complete graph K6 and supplemented by a working analogy of a semantic field; the account rejects a linear or sequential reading of the invariant and methodology.
Preserved invariants
The semantic-field analogy is identified as a working analogy, not a physical field or an asserted mathematical proof.
K6 names the explicit graph-theoretic representation (the complete graph on six vertices), not the general Semantic Connectome concept.
Impact conceptual model · model level The Changelog specifies Czech and English v2 editions; it does not assert that every language edition changed on this date.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-011
The first standalone DIO conceptual framework paper is published (v1)
Artifact
The first public version (v1) of the standalone DIO conceptual framework paper is published. The work is subsequently revised as v1.1.0 on 11 October 2026; that later version preserves the original conceptual argument and substantive claims.
DateChange publishedDate basis Hub Changelog date
ScopeDIO Conceptual Framework
Previous state
DIO had been articulated in the Manifest but had not yet been presented in this standalone conceptual paper.
Resulting state
A separate research paper systematizes DIO for publication and citation.
Preserved invariants
The paper is a distinct publication artifact and does not replace the Manifest.
Impact conceptual model · not assessed This event records publication and systematization; it does not assert empirical validation.
The Changelog gives a bounded activity period, not a single publication or edit timestamp.
SCF-2026-004
Ontology of Digital Identity is articulated as a broader theoretical layer
Theoretical
The Changelog records the articulation of a more general theoretical level, distinguished from DIO's applied optimization focus, as Ontology of Digital Identity (ODI).
DateChange introducedDate basis Hub Changelog date
ScopeOntology of Digital Identity
Previous state
DIO was framed around practical optimization of digital identity.
Resulting state
ODI is articulated as the broader theoretical layer concerned with digital identity and its conditions of being.
Preserved invariants
DIO's applied orientation and ODI's broader theoretical scope are distinguished rather than collapsed.
Impact conceptual model · model level The record captures the Changelog's conceptual distinction; later scoping and methodological notes elaborate it.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-002
Digital Identity Optimization is articulated
Conceptual
The Changelog identifies 21 May as the point at which a newly recognized dimension and possibility for optimizing and viewing digital identity was articulated as Digital Identity Optimization.
DateChange introducedDate basis Hub Changelog date
ScopeDigital Identity Optimization
Previous state
The latent space had been recognized but did not yet have the DIO designation.
Resulting state
The concept is explicitly articulated as Digital Identity Optimization (DIO).
Preserved invariants
This records the Changelog's stated articulation date; it does not claim that every later DIO construct was already defined.
Impact conceptual model · model level Initial articulation of DIO; later publications refine and formalize the framework.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
SCF-2026-001
Initial work on the text exposes a latent semantic space
ResearchProcess
The Changelog records the start of work on the professional-ethnography text and the emergence of a previously unnamed latent space. This is the project-origin milestone, not yet the formal naming of DIO.
DateChange documentedDate basis Hub Changelog date
ScopeProject genesis
Previous state
The work had not yet been explicitly articulated as DIO/ODI.
Resulting state
A latent semantic space is recorded as having emerged during the writing process.
Preserved invariants
This date marks the beginning of the documented writing process, not the formal articulation of DIO.
Impact cross layer · not assessed Project-origin milestone; it records the start of the documented writing process and the emergence of a latent semantic space, not a fully specified theoretical proposition.
Date is transcribed from the author-maintained DIO/ODI Hub Changelog; it is not automatically asserted as a Git commit timestamp.
No records match the current filters.
Record structure and governance
01 · Change
Previous and resulting state
Every event describes the documented transition without inventing a precise diff where the source does not provide one.
02 · Preservation
Preserved invariants
Records explicitly state what remains stable: identity, URI continuity, hierarchy, relations, or a mapping boundary.
03 · Evidence
Provenance and temporal basis
Primary publications, release notes, registries, and archival records are distinguished. A publication date is not silently treated as an edit timestamp.
04 · Lineage
Change relations
Events can be related, superseded, or corrected. Published identifiers are not silently rewritten.
Machine-readable access
Use the JSON feed for automated processing and the JSON Schema to validate event records. The register covers every dated entry in the DIO/ODI Hub Changelog from 25 March to 25 October 2026, with later source-backed vocabulary, mapping, and Reference Model release events through 6 November 2026.