Bootstrap MNCDS as an independent specification repository

[epi13]

Summary

Establishes the new MNCDS repository as an independent companion specification project before extracting normative and implementation material from the historical combined MNCS repository.

This PR intentionally does not migrate or rewrite MNCDS 0.1-rc.1 yet. Instead it creates the repository contract that the later transfer can follow without accidentally changing normative meaning or re-coupling MNCDS to MNCS.

What this establishes

• independent MNCDS project identity, scope, versioning, governance, and release authority;
• explicit MNCS ↔ MNCDS interoperability rules rather than duplicated normative semantics;
• migration invariants and a machine-readable ownership/disposition inventory;
• agent guidance designed for provenance-preserving extraction;
• specification, schema, conformance, RFC, documentation, and migration directory contracts;
• phased roadmap that makes the new repo independently testable before cleaning MNCDS material out of MNCS;
• security, contribution, conduct, changelog, and PR-review scaffolding;
• dependency-free bootstrap CI and repository invariant checks.

Important boundary

MNCS remains authoritative for implementation-evidence semantics. MNCDS becomes authoritative for development-process semantics: generation, evaluation, selection, release, monitoring, regeneration, replacement, retirement, candidate lineage, partitions, reproducibility, process authority, and lifecycle records.

Neither project gains normative authority over the other through technical dependency.

Migration handoff

MIGRATION.md and migration/inventory.json give the follow-up agent explicit dispositions:

• MOVE
• KEEP_IN_MNCS
• SHARED_INTERFACE
• SPLIT
• REVIEW_REQUIRED

Clearly MNCDS-owned specs/schemas have target paths. Mixed validator code, shared conformance material, RFCs, docs, and case studies are deliberately not treated as blind-copy candidates.

The bootstrap inspection recorded MNCS source commit f0088c4d46dec84f289d9b4417eec32b0ac028e6, but the migration instructions explicitly require refreshing and pinning the actual source commit when extraction begins.

Change class

• Repository bootstrap
• Editorial / architecture documentation
• Migration planning
• CI/tooling scaffolding
• Governance setup
• MNCS interoperability definition
• Normative MNCDS semantic change
• MNCDS 0.1-rc.1 migration

Non-goals

• No claim that this repo currently supersedes the historical MNCDS source in the MNCS repo.
• No attempt to redesign MNCDS during extraction.
• No new dependency on Forge, RAVEL, Fabric, any model, or a particular orchestration system.
• No attempt to create independence, protected custody, or certification through repository structure alone.

Follow-up

After this is merged, the next agent can perform the provenance-preserving MNCDS extraction and validate equivalent pre/post-migration behavior. Only after MNCDS is independently testable should the sibling MNCS repository remove transferred source and simplify its mixed validator surfaces.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.