Tagged: Architecture
System design, architecture decisions, and data flow
Pages with this tag
System architecture — components, tiers, and data flow
73One-page canonical view of Crosswalker's architecture. Three storage tiers (source, canonical Markdown, derived SQLite); six logical layers (import, storage, projection, query, export, audit); the components inside each layer; what reads what; where to look in code + docs. Simplified TL;DR up front, progressively more detail below.
System model — the whole thing, in pictures
74The illustrative, high-level map of Crosswalker: how source data becomes a canonical Markdown vault and then queryable answers, the three storage tiers, the producers, the render() coupling point, and the query/output layers — each piece linked to its deep page. Start here for the big picture, then follow any thread.
What makes Crosswalker unique
75The core differentiators and novel contributions — why this isn't just another importer, and what the short vs long term vision looks like.
Architecture
76Core components, data flow, and system design.
Config selection
77How Crosswalker matches and suggests saved configurations.
Transformation system
78How source data is transformed into Obsidian notes.
Config system
79Save, load, match, and share your import configurations.
Generation engine
80How Crosswalker creates folders and notes from your data.
OSCAL
81Open Security Controls Assessment Language — NIST's machine-readable format for security controls with SemVer versioning.
Roadmap
82Named phases from architecture-first research through community ecosystem — each decision logged with rationale.