docs(adr): 0004-octad-ontology — concerns octad is canonical#92
Merged
Conversation
Closes #19. Two different "octads" lived in the repo: the **modalities octad** (graph/vector/tensor/…) in the README, and the **concerns octad** (data/metadata/provenance/…) in code, manifest, CLI, and ADR-0003. A reader couldn't answer "what does an octad-augmented entity look like?" without picking one. Both had Temporal and Provenance entries with different meanings. ADR-0004 picks the **concerns** octad as canonical: Data · Metadata · Provenance · Lineage · Constraints · AccessControl · Temporal · Simulation Rationale: 1. The codebase has already committed to it across `abi::`, `manifest::`, `codegen::`, `tier1::`, CLI, manifest schema, and ADR-0003's drift categories. Reversing would touch every module. 2. Each concern is a question the system answers ("when did this change?", "who saw this?"). Modalities answer the same questions only obliquely. 3. ADR-0003's drift categories are themselves concerns-shaped — structural/semantic/statistical/referential drift are violations of the *Constraints* concern across modalities. Inverting the relationship makes the catalogue harder to motivate. The modalities octad isn't deleted — it's demoted to Tier 2 *overlays* (`Tier2Config { graph, vector, tensor, semantic, document, spatial }`). Storage shapes you can additionally project into; not the top-level identity. Also updates README's "Eight Modalities" primary table to the concerns octad with explanatory pointer to the ADR. The earlier section's broader rewrite (recasting the eight drift categories as symptoms-of-Constraints-violation) is left to V-L1-A2 (#20). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per V-L1-A1: two octads with the same name lived in the repo (modalities in README, concerns in code). ADR-0004 picks concerns as canonical — Data · Metadata · Provenance · Lineage · Constraints · AccessControl · Temporal · Simulation.
Rationale:
abi::,manifest::,codegen::,tier1::, CLI, manifest schema, ADR-0003 drift categories.Modalities aren't deleted — they're demoted to Tier 2 overlays (
Tier2Config { graph, vector, tensor, semantic, document, spatial }). Storage shapes you can project into; not the top-level identity.README's "Eight Modalities" primary table is updated to the concerns octad in this PR, with a pointer to ADR-0004 and a note that modalities live as Tier 2. The broader README rewrite (recasting the eight drift categories as Constraints-violations-across-modalities) is left to V-L1-A2 (#20), which this ADR unblocks.
Closes
Test plan
docs/decisions/0004-octad-ontology.adocwith status / context / decision / alternatives considered / consequences / follow-ups / cross-referencesDoc-only; no code changes.