Import canonical MNCDS 0.1 material and standalone validator - #2
Merged
Conversation
Specification text, schemas, examples, RFC 0004, and the mncds CLI now live here, extracted from MNCS commit f0088c4d46dec84f289d9b4417eec32b0ac028e6. MNCDS is independently versioned and no longer a nested chapter of MNCS.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This was referenced Aug 15, 2026
The repository is now the canonical MNCDS home, so CI no longer requires the old bootstrap warning. Add a local normative-language note so 0.1-rc.1 does not depend on an MNCS checkout.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
This repository is now the canonical home of MNCDS 0.1.
Imported from MNCS commit
f0088c4d46dec84f289d9b4417eec32b0ac028e6:spec/MNCDS-v0.1-draft.mdspec/MNCDS-v0.1-rc.1.mdspec/MNCDS-v0.1-records-and-decisions.mdmncdsvalidator and testsArchitectural implications
MNCDS owns development-process semantics. MNCS owns implementation-evidence acceptance. Neither embeds the other's specification.
Tests
pytest tests: 9 passed afterpip install -e '.[dev]'Intentionally deferred
mncdsconsumer (kept as a shared interface)This is part of the coordinated 2026-08 MNCS family alignment:
Suggested merge order: MNCDS, then MNCS, then Harness + Control, then Atlas and remaining docs PRs. They can also merge independently.
Coordinated PRs