From 3b4bea9527ea2f80f8ebaa63b067c900b1d63bfa Mon Sep 17 00:00:00 2001 From: epi13 Date: Fri, 14 Aug 2026 17:23:05 -0800 Subject: [PATCH] Document the MNCS Harness repository rename in family integrations. --- README.md | 2 +- docs/INTEGRATIONS.md | 16 +++++++++++----- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 99dd8ff..17ff4dc 100644 --- a/README.md +++ b/README.md @@ -84,7 +84,7 @@ surfaces. | Project | MNEL role | |---|---| -| `MNEL-local-harness` | Routes work across local models and exposes bounded tools to investigator roles | +| MNCS Harness | Optional sibling that routes work across local models and exposes bounded tools to investigator roles | | MNCS Forge | Supplies provider-neutral micro-verifiers, diagnostic probes, snapshots, and counterfactual witnesses | | MNCS Fabric | Executes and reconciles content-addressed experiments across machines | | RAVEL | Supplies the adaptive mechanism and consumes governed experience or candidate proposals | diff --git a/docs/INTEGRATIONS.md b/docs/INTEGRATIONS.md index b90fe61..e701aab 100644 --- a/docs/INTEGRATIONS.md +++ b/docs/INTEGRATIONS.md @@ -1,9 +1,13 @@ # Project-family integrations -## epi13-local-harness +## MNCS Harness -The local harness is the intended model-routing and bounded-tool substrate. MNEL's -`LocalHarnessAdapter` sends the sibling JSON-line `chat/start` protocol with a role +The former `epi13-local-harness` repository is now +[MNCS Harness](https://github.com/epi13/mncs-harness). Checkout directories named +`mncs-harness` replace the old `epi13-local-harness` path. Harness is an optional +sibling routing and tool substrate, not a normative MNCS or MNEL requirement. + +MNEL's `LocalHarnessAdapter` still sends the sibling JSON-line `chat/start` protocol with a role contract, eligible-context identity and record identities, runtime identity envelope, task prompt, allowed tools, and a detached proposal workspace. The command is an explicit argument vector (`shell=False`), and the adapter enforces a timeout and output ceiling. @@ -86,5 +90,7 @@ or an external candidate lifecycle evaluates it transactionally. ## MNCDS and MNCS MNCDS records development evidence, feedback eligibility, lineage, and same-epoch repair -restrictions. MNCS evaluates a frozen implementation claim. MNEL should export eligible -records to those protocols rather than inventing a second conformance authority. +restrictions. MNCS evaluates a frozen implementation claim. MNCDS is maintained as the +sibling [Machine-Native Complexity Development Specification](https://github.com/epi13/machine-native-complexity-development-specification); +it is not a submodule of MNCS. MNEL should export eligible records to those protocols +rather than inventing a second conformance authority.