Skip to content
sdlc

One contract layer across the fleet

Status: open/planned

Goal

Section titled “Goal”

Every contract in the fleet speaks markdown-contract’s mcVersion-2 JSON-Schema vocabulary, and parallel contract engines converge or are scheduled for deletion. Today determined-contracts maintains its own zod-projection + .contract.yaml engine pinned to golden output; sdlc entities use the TS engine directly; polish joins via M-3PVK. This milestone makes the vocabulary and the finding model singular, and absorbs the open body-structure-validation ideas (B-8FL9, B-RX2K) into the one contract layer.

Success criteria

Section titled “Success criteria”
  • determined-contracts validates via the mcVersion-2 declarative engine (or is verified byte-parity-equivalent and documented as a temporary vendored fork with a convergence date).
  • SDLC entity contracts and determined vault contracts express body structure in the same vocabulary; no third dialect exists.
  • B-8FL9 and B-RX2K are closed pointing at D-7VMX-markdown-ecosystem-strategy.
  • Vocabulary gaps found during convergence are filed upstream in markdown-contract’s planning corpus, not patched locally: cross-field rules, cron wording, Schematter’s token budgets, and mdschema’s image-leaf, heading-integrity, heading↔filename expr, and link-domain-policy ideas.
  • The vendored .tgz consumption is replaced by a versioned publish→bump flow (registry or git tag), exercised at least once.

Deliverables

Section titled “Deliverables”
  • Convergence audit: every contract artifact in the monorepo, its dialect, its target state.
  • determined-contracts convergence PR(s).
  • Upstream vocabulary proposals for gaps.
  • Backlog closures and P-0007-long-lived-data-formats fleshed out from stub.

Out of scope

Section titled “Out of scope”

← Back to Milestones