Point development-process authority at the independent MNCDS repository

[epi13]

What changed

Reference-studies docs now treat MNCDS as an independent sibling specification rather than a chapter of the MNCS repository.

This is part of the coordinated 2026-08 MNCS family alignment:

• MNCDS becomes the canonical development-specification home
• MNCS Harness is the public identity of the former epi13-local-harness repository
• public docs describe reusable operator infrastructure, not a particular laboratory
• Harness / Control / Fabric / Commons / Forge remain non-normative relative to MNCS

Suggested merge order: MNCDS, then MNCS, then Harness + Control, then Atlas and remaining docs PRs. They can also merge independently.

Coordinated PRs

• Import canonical MNCDS 0.1 material and standalone validator machine-native-complexity-development-specification#2
• Relocate MNCDS specification authority to the MNCDS repository machine-native-complexity-standard#64
• Identify the project as MNCS Harness with compatibility aliases mncs-harness#40
• Discover MNCS Harness first and sanitize operator examples mncs-control-mcp#20
• Split MNCS/MNCDS and document MNCS Harness as operator infrastructure mncs-atlas#5
• Use MNCS Harness naming and generic worker examples mncs-fabric#45
• Refer to MNCS Harness as the operator routing layer MNCS-Commons#16
• Document the MNCS Harness repository rename Machine-Native-Experimental-Learning#11
• Point development-process authority at the independent MNCDS repository #4

[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.