Parent: corpus
The pillar's class diagrams live on the design pages they belong to; this page is the coverage gate.
| type / area | diagrammed at | verified |
|---|---|---|
| ExportDeps / WriteZip / ImportVault / SaveWriting / refreshCrossLinks | writings-import-export | ✓ code |
the one corpus_notes table (genre column: raw/wiki/output/subjectivity/writing) + note_refs / writing_refs + assets / asset_references | ER on corpus | ✓ schema (backend/db/schema.sql:189, re-verified 2026-09-07) |
sync pipeline (SyncVault: classify → tree → ambiguity check → reconcile → resolve-links → prune) | flowchart on obsidian-sync-mechanism | ✓ flowchart (vs backend/internal/corpus/obsidian/sync.go, 2026-09-07) |
| derived-path builder types | derived-path-corpus-as-filesystem (prose) | ☐ no class diagram |
| backlink rebuild (note_refs writer) | backlinks-as-rebuilt-edge-tables (prose) | ☐ no class diagram |
retrieval usecases (Meili FTS + corpus_links 1-hop over note_refs) | corpus-retrieval (design) | ☐ no class diagram |
| render pipeline components (markdown.tsx overrides) | rendering-engines (prose) | ☐ no class diagram |
The centerpiece is the sync flowchart (the flagship corpus-as-vault flow, verified against backend/internal/corpus/obsidian/sync.go — the package moved out of usecases/ on 2026-07-29, 9f1ffcf13). The remaining ☐ rows are lower-value class-diagram debt — promote by adding the class view on the owning page and updating this table.