Run governed verification packets for claims, invariants, contracts, or evidence.
npx skills add https://github.com/apply-the/canon --skill canon-verification
Please help me install this Agent Skill. Skill: canon-verification Source: https://github.com/apply-the/canon/tree/main/.agents/skills/canon-verification Command: npx skills add https://github.com/apply-the/canon --skill canon-verification
The Canon verification workflow provides a formal, governed mechanism to challenge claims, invariants, contracts, and evidence directly from within a repository.
Start a governed verification by providing risk, zone, and at least one authored input; Canon will guide the creation, validation, and persistence of the verification packet.
High-intent search queries and answers about installing and using this skill.
To run governed verification, you must provide a valid risk, zone, and at least one authored input to generate a file-backed verification packet. Preflight checks then validate Canon installation and your project's directory before processing the claims.
A Canon verification packet is a formal, file-backed mechanism used to challenge claims, contracts, and evidence within a repository. You need it when requiring governed validation of project invariants or authored inputs directly from your AI assistant.
You validate evidence by starting a governed verification workflow that requires a risk level, zone, and inline note or authored input. The process applies preflight checks to ensure your project environment is correctly configured before validating the evidence.
Yes, your project must contain a .canon/ directory and have Canon installed to challenge repository claims. Preflight checks verify this ownership and directory structure, along with your input requirements, before invoking the verification process.
File-backed verification packets require strict preflight compliance, meaning the process will not proceed without a valid risk, zone, and authored input. Verification is limited to repositories with Canon installed and a properly configured .canon/ directory structure.
Yes, you can use an inline note as a valid substitute for authored inputs when testing invariants. The verification process requires at least one authored input or inline note alongside a valid risk and zone to proceed with the challenge.
apply-theCreate a local .canon directory for Canon runtime state.
tizeeRequire fresh verification evidence before declaring code, tests, builds, or tasks complete.
vTRKAGenerate proof-backed Remotion or browser-recording video plans with provenance and accessibility fallbacks.
santosomarInfer loop invariants and function contracts from execution traces.
