Tagged: Architecture
System design, architecture decisions, and data flow
Pages with this tag
Vision alignment decisions
25Key architectural and strategic decisions from roadmap planning Q&A — the philosophical foundation for Crosswalker's direction.
Why Obsidian, why files
26The foundational design decision — filesystem-first, not database-first. Why Obsidian over Notion, Airtable, or any no-code database.
Institutional landscape decisions
27Decisions on how to document the institutional ontology landscape — layout, structure, tech approach, and scope.
Obsidian app internals — research needed
28High-level logic flow, rendering loops, and constraints of the Obsidian app that will limit Crosswalker's plugin capabilities.
Volatility property and entity registry
29Introducing formal content volatility tracking and a registry of institutional actors — building toward the marketplace.
Homepage navigation and site identity decision
30Should the docs sidebar be accessible from the homepage? Is the docs site also the marketing site?
Ontology evolution: first principles revisited
31Breaking 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?
32Literature 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
33Questioning 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?
34Starting 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?
Evidence-link edge model synthesis — junction notes as the committed architecture
35Distilling 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
36Distilling 4 parallel research sessions against Foundation-phase decisions. Convergences, challenges, new formal concepts, and the decisions this forces — with visual anchors for the math.