alfiz-verify checks at build time and the rule that makes Alfiz’s convention document reliable for both human reviewers and coding agents. Skipping any one point leaves a real gap: a user can reach the page but not load it, or load it but submit a hidden form, or navigate without seeing the item but still hit the API directly. All four must hold together.
The four points
Complete example: a document editor
The following shows all four points implemented for a single document-editor feature.Scoped forms
All four points accept ascope argument wherever a concrete resource instance is available:
For surfaces that operate globally (admin dashboards, org-level settings), omit the scope argument, because a global grant satisfies every scoped check by definition.
alfiz-verify does not have a rule per point. What it enforces is Point 3 directly: ungated-action fires on an exported async function in a server file with no gate, plus visibility-as-gate anywhere in a server file, unknown-pattern at every literal call site, and unreferenced-leaf across the catalog. Points 1 and 4 have no dedicated rule: a page or a button with no check is caught indirectly, as the unreferenced-leaf warning on the key nothing references. See Static Verification.