Tagged: Data model
Data modeling, graph databases, consistency, and resilience
Pages with this tag
Knowledge organization
1How to organize framework knowledge in Obsidian — structural primitives, meta-frameworks, and the hierarchy vs. graph tension.
Tradeoffs
2Known tradeoffs in the current design and their justifications.
Challenge 01: Are the ontology diff primitives truly atomic?
3Critically assess whether our 9 atomic operations are the right decomposition. Find counterexamples, edge cases, or missing operations.
Challenge 06: Pairwise vs synthetic spine — architecture, resilience, and trustworthiness (archived)
4Investigate whether Crosswalker should architect cross-framework crosswalks through a canonical intermediate spine (hub-and-spoke) or continue with direct pairwise mappings. Go deep on long-term resilience and audit-grade trustworthiness of synthetic spines. RESOLVED 2026-05-01 — see callout.
Challenge 07: Link metadata / edge model for evidence mapping (archived)
5Design the edge metadata model for evidence→framework implementation links — the "other" edge type Crosswalker has to support that's NOT a crosswalk. Bases-compatible storage, custom or inherited schema, reviewer attribution, status transitions. RESOLVED 2026-04-10, archived 2026-05-01.
Challenge 09: UUID / CWUUID cross-cutting identifier strategy
6Where exactly does Crosswalker need persistent identifiers? Survey every place a UUID-class ID would matter (nodes, edges, junction notes, evidence notes, framework versions, spine snapshots, mapping authors, vault identity), evaluate options (UUIDv4/v7, ULID, content-addressed CID, OSCAL UUIDs, custom CW prefix), and recommend a minimum viable identifier scheme for Foundation.
KB population and ecosystem shift
7Incorporated Frameworker research, DFD cross-project learnings, and documented the Dataview → Bases → Datacore transition.
Why Obsidian, why files
8The foundational design decision — filesystem-first, not database-first. Why Obsidian over Notion, Airtable, or any no-code database.
Ontology evolution: first principles revisited
9Breaking down the ontology evolution problem from data structure primitives, not organizational conventions. Where we are, what we're deciding, and the paths forward.
Research: atomic operations on graphs — are the 13 primitives primitive enough?
10Literature survey of graph edit distance, ontology diff, tree-diff, schema evolution, and category theory to determine the provably complete set of atomic operations for describing structural changes.
How primitive are the primitives? Pluggable layers and open questions
11Questioning whether the 13 structural primitives are fundamental enough, exploring detection as pluggable logic, taxonomy-over-taxonomies for decisioning, custom transfer logic, and graph vs. hierarchy scope.
User-first ontology maintenance: what does the experience look like?
12Starting from the user (human or agent) and working backwards — what does it feel like to keep ontologies up to date? What does the system actually DO when frameworks change?