Skip to content

Document the MNCS Harness repository rename #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
epi13 merged 1 commit into from
Aug 15, 2026
Merged

Document the MNCS Harness repository rename #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Expand Down
16 changes: 11 additions & 5 deletions docs/INTEGRATIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Expand Down Expand Up @@ -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.
Loading