For: people changing workflows, actions, prompts, schemas, profiles, examples, documentation, or releases in the Control Repository.
Outcome: a change that preserves consumer compatibility, trust boundaries, and documentation contracts.
- Read the shared domain language.
- Read the decision map.
- Read the accepted distribution model.
- Read the documentation architecture.
- Identify whether the change affects a consumer interface, execution trust, Evaluation Result, Security Profile, or release graph.
- Run
bash scripts/check-docs.shfor documentation changes.
The G0 trustworthy-foundation gate is the required pre-v1 trust suite and maps each claim to a positive contract and rejecting fixture.
| Area | Owns |
|---|---|
actions/ |
Composite action inputs, outputs, and implementation |
.github/workflows/ |
Runners, permissions, secret plumbing, and reusable workflow contracts |
prompts/ |
Shared and Filecoin-specific AI review behavior |
examples/ |
Executable consumer contracts |
docs/ |
Consumer, maintainer, operator, and reference journeys |
scripts/ |
Local validation and development tooling |
- Treat workflow/action inputs, outputs, defaults, and completion behavior as versioned consumer contracts.
- Give every workflow explicit least privilege.
- Treat PR content, repository files, diffs, titles, and descriptions as untrusted.
- Do not execute project code merely to inspect it.
- Pin every external execution dependency immutably.
- Keep composite actions thin and put testable logic in scripts.
- Update or add an executable example when a consumer-facing capability changes.
- Update documentation in the same change; do not defer contract corrections.
Run the checks that currently exist:
bash scripts/check-docs.sh
bash scripts/check-release-graph.sh
bash scripts/check-fork-pr.sh
actionlint .github/workflows/*.yml examples/*.yml
shellcheck actions/**/scripts/*.sh scripts/*.sh
jq empty actions/**/scripts/*.jsonThe repository is still adding automated CI and adversarial fixtures. The verification-system ticket defines the complete target.
There is no stable v1. Do not introduce documentation that implies @v1
exists. The reviewed pilot pin is transitively immutable, but it remains a
pilot until later evaluation, governance, and release gates are complete.