Add artifact validator layer - #48
Open
Permea-lab-admin wants to merge 1 commit into
Open
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.
Summary
This PR adds the first public artifact validator layer for Permea Core.
It adds:
scripts/permea_check.pyfor checking public example artifactspermea_core.validatormoduledocs/specs/VALIDATION.mdScope
This PR lets researchers and developers check current public example artifact families against public Permea artifact standards.
Supported families:
The validator is intentionally lightweight and dependency-minimal. It checks file presence, known families, required schema concepts, claim-boundary language, public/private boundary hygiene, credential-like signatures, and deterministic report status.
Claim boundaries
This PR keeps claims bounded to local public artifact checking and metadata/spec conformance checks.
It does not claim:
Public/private boundary
The added files were reviewed to avoid private program, resource, workflow, prompt, credential, local path, or infrastructure context.
Validation
git diff --checkpython3 scripts/permea_check.py --allpython3 scripts/permea_check.py --family dataset_cardpython3 scripts/permea_check.py --family benchmark_cardpython3 scripts/permea_check.py --family evidence_cardpython3 scripts/permea_check.py --family run_manifestpython3 scripts/permea_check.py --family output_packagepython3 scripts/permea_specs.pypython3 scripts/permea_evaluate.pypython3 scripts/permea_reproduce.pypython3 scripts/permea_validate.pypython3 scripts/generate_evidence_surface.pypython3 scripts/generate_demo_packet.pypython3 scripts/generate_artifact_index.pypython3 scripts/generate_evidence_matrix.pypython3 scripts/run_permea_dry_run.pypython3 scripts/generate_permea_artifacts.pypython3 scripts/validate_permea_artifacts.pypython3 -m pytest tests/test_artifact_validator.py tests/test_artifact_specs.py tests/test_evaluation_bundle.py tests/test_reproducibility_bundle.py tests/test_evidence_surface.py tests/test_demo_packet.py tests/test_artifact_index.py tests/test_evidence_matrix.py tests/test_permea_dry_run.py tests/test_generate_permea_artifacts.py tests/test_validate_permea_artifacts.py