Markdown ecosystem core
State: open/building · Kind: system · Audience: system
Summary
Section titled “Summary”- One Rust markdown core built around a single lossless CST, with contract/validation, transformation, and query as derived planes over that one tree — no plane re-parses.
- Canonical home is the
markdown-contractrepo; this monorepo pins a vendored tarball (vendor/markdown-contract-0.2.1.tgz) and incubates fleet-specific crates that graduate upstream. - TypeScript consumers reach Rust through per-crate bindings where they pay; TypeScript owns the query plane.
Statement
Section titled “Statement”The fleet treats markdown + frontmatter on disk as its data substrate, but the
capability to read, validate, transform, and query that substrate grew as per-app
implementations — five frontmatter parsers, three wikilink resolvers, two vault walks.
This umbrella capability names the target: one core that owns parsing and fidelity, a
set of planes that own semantics, and a binding per crate where a consumer language
needs one. Child
capabilities define each plane; D-7VMX-markdown-ecosystem-strategy fixes the
architecture and sequencing.
What it provides
Section titled “What it provides”- A lossless CST substrate every other plane derives from (C-N6RH-lossless-roundtrip-io).
- Contract-driven validation and typed reads (C-K3TQ-markdown-contract-and-validation).
- Vault-level modeling and structural transforms (C-T9GW-vault-model-and-transforms).
- Incremental indexing and Bases-style queries (C-V5JD-vault-query-and-index).
- Per-crate WASM/TS bindings (C-X2PB-wasm-ts-surface).
- An extension seam for embedded peer content (C-Z7LN-embedded-peer-content).
Children carry parent_key pointing here; the tree is the capability map of the
strategy. Consumers today: sdlc entity tooling, polish, the determined suite, ontogen’s
markdown-store, the Astro doc sites.