Vault kernel and structural transforms

Status: open/draft

Goal

Land the vault plane: kernel (walk, guards, identity), reference graph, and the plan/execute transform engine — the PR #43 design dossier (migrated verbatim beside D-7VMX-markdown-ecosystem-strategy) implemented over the CST core, in this repo, as tier-4 incubation crates. The headline deliverable is vault reshape (TM-0025-vault-reshape): config-driven projection of source vault(s) into a target vault of a different shape, with in-place rename/move as degenerate cases. Consolidates the duplicated walk and path-guard code in solutions/determined while delivering the transform engine nothing in the fleet has today.

Success criteria

• Vault kernel with policy-parameterized walk replaces platform-core/src/vaultwalk.rs and the duplicated path-escape guards; the duplicates are deleted.
• Reference graph over wikilinks/embeds/anchors, resolved via path map with per-source link identity — never string guessing.
• Vault reshape works end-to-end: sources[] → target via glob map.rules[] and a collision-resolved PathMap; per-note transform plugins run in the transform stage; dry-run parity holds (execute re-verifies source hashes).
• Contract-pair gating: a reshape declaring source/target contracts validates inputs against the source contract and output against the target contract.
• Rename/move with backlink rewrite works plan-first as a degenerate reshape: dry-run plan is inspectable, execution applies minimal splice edits, link integrity and no-silent-overwrite invariants hold under test.
• The storage seam implements the four-operation write model: swap/splice/ canonical guarded by atomic+CAS, external observed with self-echo classification (write-hash journal) and vault-wide bulk invalidation.
• The seam’s backend is a trait: native fs and an in-memory/host-callback adapter both pass the same invariant suite, keeping the vault plane WASM-portable.
• rust-markdown is archived once its two live assets are home: the dossier migration (landed with D-7VMX-markdown-ecosystem-strategy) and the jsoncanvas crate relocation into this monorepo.
• A named consumer ships on it: a polish vault-repair operation or an sdlc entity-rename verb.

Deliverables

• Vault kernel + reference graph crate(s), incubating in this monorepo.
• Transform plan/execute engine implementing the migrated dossier design (pipeline stages, PathMap, plugin seam) with the invariant test suite.
• Consolidation PRs deleting the determined duplicates.
• jsoncanvas crate relocation + rust-markdown archive.

Risks / open questions

• Graph freshness vs. the index plane (M-N2HG-query-and-index-plane) — decide whether the reference graph is the first index consumer or a standalone structure.

---

← Back to Milestones