Tagged: Architecture
System design, architecture decisions, and data flow
Pages with this tag
SEACOW + folder-tag-sync — prior-art the project owner built before Crosswalker
37Documenting 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.
Consistency models
38ACID, CAP theorem, eventual consistency, and BASE — applied to Obsidian vaults and Crosswalker imports.
File-based graph databases
39How markdown vaults function as property graph databases — formal model, trade-offs, and patterns for storing structured relationships in files.
Institutional landscape
40The entities, relationships, and dynamics of who creates, maintains, maps, mandates, and consumes structured ontologies — the human side of ontology management.
Ontology lifecycle
41The lifecycle of an ontology within the Crosswalker ecosystem — from acquisition through import, enrichment, maintenance, and sharing.
Operational landscape
42Who does what work across the ontology ecosystem — institutions × components × resources. The combined view of effort, ownership, and sustainability.
What makes Crosswalker unique
43The core differentiators and novel contributions — why this isn't just another importer, and what the short vs long term vision looks like.
Architecture
44Core components, data flow, and system design.
Config selection
45How Crosswalker matches and suggests saved configurations.
Transformation system
46How source data is transformed into Obsidian notes.
Config system
47Save, load, and match import configurations.
Generation engine
48How Crosswalker creates folders and notes from your data.