artefact-discipline-checklisted

# Artefact and Branch Discipline: Check ## Overview Two related disciplines protect a project's audit trail: generated artefacts are read-only (the generator is the canonical statement of how the artefact derives from the source), and protected branches are append-only (the branch is the canonical statement of what the project's history looks like). This skill runs the routing workflow from the canonical rule [`governance/artefact-and-branch-discipline.md`](../../governance/artefact-and-branch-discipline.md) so a change about to take the forbidden path (hand-edit the artefact; force-push past the check) is caught and redirected at the moment of decision. The rule is the source of truth for normative content (what counts as generated, what counts as protected, what the exception paths look like, framework alignment). This skill is the workflow wrapper: identify the trigger, classify the artefact or branch, route to the correct action. ## When to Use - Before opening an editor on a file at the top of which sits a "Do not hand-edit; regenerate via X" notice, or any file your project's `## Boundaries` section names as generated. - Before running `git push` directly to the default branch, a release branch, or a long-lived integration branch the project treats as protected. - Before running `git push --force` or `--force-with-lease` against any shared branch. - Before running `git reset --hard` over uncommitted work, especially work that did not originate with you. - Before me