Validate artifact (schema gate)
The commons ships a deterministic schema validator. Run it; do not eyeball.
Procedure
Ensure the draft has complete YAML frontmatter (required:
id, type, title, status, sources, review, outputs, contributors, license).From the repo root, run the project's validator:
python scripts/validate_artifacts.py content/path/to/your-artifact.md(No args scans all of
content/andmissions/.)If marine-mcp is available, you can also self-check frontmatter via its
validate_artifacttool before touching the filesystem.
Interpreting results
OK <file>— passes the schema.FAIL <file>followed by- <field>: <message>— fix each before PR. Common causes: missingreviewblock, emptysources,idnot matching^[a-z0-9]+(-[a-z0-9]+)*$,species_groupvalue outside the enum.
The CI workflow validate-artifacts.yml runs this on every PR — a local failure is a guaranteed CI failure. Fix locally first.
Built on SIP · Blue Life Commons.