Add DSH-derived adapter admission discipline and egress tripwire - #38
Merged
Merged
Conversation
Record four adapter admission rules in adapter-seam.md (boot-declared manifest validated before state, registrations as effects with reverse order disposers, provider-visible implies activity-logged, typed errors across the seam), adapted from DeepSeek Harness's plugin discipline, and sharpen the rule 3 trigger: machinery is justified by a second party extending nanodot, not by swappability, which the fakes already prove. Add the egress tripwire test asserting every provider-visible field is reconstructable from the activity log and that the StateChange surface stays exactly the documented whitelist. Ignore run-logs/ and the tool-local .zcodeignore. Ref: #37
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
docs/design/adapter-seam.md: new Adapter admission discipline section — four rules adapted from DeepSeek Harness (DSH)'s plugin discipline, adopting the discipline without the machinery:
Also sharpens the rule 3 trigger: swappability alone never justifies machinery (the fakes already substitute every port); the machinery-grade trigger is a second party extending nanodot without forking it.
tests/test_inference.py: egress tripwire — every provider-visible
StateChangemust be reconstructable from the activity log viastate_change_from_event, and theStateChangesurface must stay exactlySUMMARIZE_FIELDS. Widening the egress surface now fails here until it is whitelisted in docs/design/egress.md..gitignore: ignore
run-logs/and the tool-local.zcodeignore.Why
Follow-up from the DSH plugin-mechanism study (DSH is a candidate adapter under rule 3): adopt its proven engineering discipline now, while the adapter machinery itself stays gated until a demonstrated native-runner limitation.
Tests
Full offline suite (dead-proxy environment per README), including the new tripwire test.