Repository navigation
chore(models): retain scoped evidence with pinned simulation inputs - #23
Merged
Merged
Conversation
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
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.
Complete the modbus-models-v2 consumer lock with the exact L2 product record and its data-owned machine schema, in addition to the fixed TMs and scenarios. Prepared local examples retain inspectable proof/limits alongside their input hashes; no model interpretation or public application dependency changes.
Validation: all nine locked files prepared and verified from the immutable db8cf19 data commit; 5 consumer tests passed. Candidate and released-runtime catalog CI rerun independently, including the real public clients and wrong-byte-order counterexample. This closes the simulator side of M2's product-evidence handoff.