Tagged: Data model
Data modeling, graph databases, consistency, and resilience
Pages with this tag
Evidence-link edge model synthesis — junction notes as the committed architecture
13Distilling 2 research sessions directly targeted at Challenge 07 (the link metadata / edge model for evidence mapping). Both converge strongly on junction notes (edge-as-note reification) as the only architecture compatible with Obsidian Bases' flat-YAML constraint, with a concrete 13-field schema validated against 8 GRC tools and OSCAL round-trip.
Foundation research synthesis — testing our decisions against 4 parallel research sessions
14Distilling 4 parallel research sessions against Foundation-phase decisions. Convergences, challenges, new formal concepts, and the decisions this forces — with visual anchors for the math.
SEACOW + folder-tag-sync — prior-art the project owner built before Crosswalker
15Documenting two of the project owner's existing tools (SEACOW meta-framework in cyberbase, obsidian-folder-tag-sync plugin) as Foundation-phase prior-art that should inform Crosswalker's hierarchy-vs-graph decisions — and flagging a formal reuse investigation as a research item.
Foundation commitments and follow-on research — pairwise+pivot, junction-notes-by-tier, StewardshipProfile, meta-schema lifecycle
16Decisions made 2026-05-01 after re-reading the morning orientation log and the Challenge 06 research deliverable. Commits the pairwise + optional-pivot hybrid (Challenge 06 resolution); ties junction-note feasibility to tier; renames EvolutionPattern → StewardshipProfile; introduces the schema-marketplace direction; commits that every Crosswalker-internal schema is versioned and migration-aware (Crosswalker eats its own dog food); spins up three new research challenges (git-history audit-trail tenability, UUID/CWUUID strategy, graph→tabular bridging engine).
Foundation state of play — the web-of-webs and the open problems
17A re-orientation log after a 3-week gap. Frames ontology lifecycle management as structured webs connecting to structured webs (with optional intermediaries), then maps every open Foundation problem onto that picture with links to the roadmap, challenges, and prior research.
Direction — research wave (Challenges 08/09/10), critical gaps, and the roadmap reshape
18The direction log promised on 2026-05-01 §6. Three fresh-agent research deliverables landed for Challenges 08 (git audit-trail tenability), 09 (UUID/CWUUID strategy), and 10 (graph→tabular bridging engine). This log summarizes each, calls out substantive gaps in Challenge 10's tech-stack coverage, spins up three new research challenges (11/12/13) to fill those gaps, refreshes the Phase A/B/C/D plan, and translates yesterday's commitments into concrete roadmap deltas.
Obsidian metadata ecosystem
19Properties, Dataview, Bases, and Datacore — the evolving landscape of structured metadata in Obsidian and what it means for Crosswalker.
Ontology lifecycle
20The lifecycle of an ontology within the Crosswalker ecosystem — from acquisition through import, enrichment, maintenance, and sharing.
Terminology
21Key terms and concepts used throughout Crosswalker — with a visual at-a-glance of the two committed edge models (crosswalks and evidence links) at the top.
Glossary
22Verbose definitions of every term used across the Crosswalker knowledge base. One page per concept for deep reference.
Unified risk model (for risk & GRC teams)
23A recommended implementation for risk/GRC/audit/compliance teams — a shared data model (ontology) they operate on together, with CRI Profile as the authority-of-record and every other framework crosswalked to it. The "assess once, comply many" backbone Crosswalker (or any related tool) can implement. A domain-specific application, not a universal Crosswalker concept.