Add Holmes maturity manifest and validation gate#10
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
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.
Summary
Adds estate maturity metadata and validates it through the existing Holmes validation path.
This PR adds:
repo.maturity.yamlmarking Holmes as M2 with target M3.tools/validate_maturity.py, a dependency-free maturity manifest validator.validate-maturityMakefile target.make validatenow runs maturity validation before the existing Holmes contract and CLI checks.Maturity position
Holmes is marked M2, not M3, because CI exists and runs validation, but M3 still requires negative fixtures and a negative-fixture runner per
SocioProphet/functional-model-surfacesmaturity guidance.Validation
Expected:
Expected output includes: