106  Build, Tooling, Versioning, and Release

107 Build, Tooling, Versioning, and Release

Range: 1064-1139.

107.1 Completion

Status	Count
authored	76

Use the summary table for scanning. Each row links to the detailed anchored entry below.

Sigil	Term	Completion	Semantic	Summary
1064	artifact	authored	reviewed	A produced thing you can store, ship, or compare.
1065	assemble {Forge}	authored	generated_draft	assemble in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the assemble obligation named before work proceeds.
1066	baseline {Forge}	authored	generated_draft	baseline in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the baseline obligation named before work proceeds.
1067	binary	authored	generated_draft	binary is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the binary obligation named before work proceeds.
1068	branch {Forge}	authored	reviewed	A line of history where change can proceed without touching the main trunk.
1069	build	authored	reviewed	Turn source into a runnable or shippable artifact.
1070	build cache	authored	generated_draft	build cache is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the build cache obligation named before work proceeds.
1071	build graph	authored	generated_draft	build graph is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the build graph obligation named before work proceeds.
1072	bundle	authored	generated_draft	bundle is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the bundle obligation named before work proceeds.
1073	canary	authored	reviewed	A deliberately limited release whose job is to discover whether production reality agrees with the story told in staging.
1074	changelog	authored	generated_draft	changelog is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the changelog obligation named before work proceeds.
1075	cherry-pick	authored	generated_draft	cherry-pick is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the cherry-pick obligation named before work proceeds.
1076	CI	authored	reviewed	Continuous integration: change is merged only after automated checks speak.
1077	codegen	authored	generated_draft	codegen is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the codegen obligation named before work proceeds.
1078	commit {Forge}	authored	reviewed	Record a change as one named point in history.
1079	compile {Forge}	authored	generated_draft	compile in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the compile obligation named before work proceeds.
1080	container {Forge}	authored	generated_draft	container in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the container obligation named before work proceeds.
1081	container image	authored	generated_draft	container image is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the container image obligation named before work proceeds.
1082	continuous delivery	authored	generated_draft	continuous delivery is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the continuous delivery obligation named before work proceeds.
1083	continuous integration	authored	generated_draft	continuous integration is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the continuous integration obligation named before work proceeds.
1084	dependency	authored	reviewed	Something your code needs in order to build or run.
1085	dependency graph	authored	generated_draft	dependency graph is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the dependency graph obligation named before work proceeds.
1086	deploy	authored	reviewed	The crossing from forge to world. Many good ideas become bad facts only after they are actually shipped.
1087	deployment ring	authored	generated_draft	deployment ring is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the deployment ring obligation named before work proceeds.
1088	diff {Forge}	authored	reviewed	A visible account of what changed between one state and another. Good diffs make review local; bad diffs turn truth into fog.
1089	distribution	authored	generated_draft	distribution is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the distribution obligation named before work proceeds.
1090	Dockerfile	authored	generated_draft	Dockerfile is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the Dockerfile obligation named before work proceeds.
1091	downgrade	authored	generated_draft	downgrade is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the downgrade obligation named before work proceeds.
1092	environment	authored	generated_draft	environment is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the environment obligation named before work proceeds.
1093	feature flag	authored	reviewed	A runtime switch that separates deploy from release.
1094	formatter	authored	generated_draft	formatter is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the formatter obligation named before work proceeds.
1095	hermetic build	authored	generated_draft	hermetic build is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the hermetic build obligation named before work proceeds.
1096	install	authored	generated_draft	install is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the install obligation named before work proceeds.
1097	installer	authored	generated_draft	installer is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the installer obligation named before work proceeds.
1098	issue tracker	authored	generated_draft	issue tracker is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the issue tracker obligation named before work proceeds.
1099	job runner	authored	generated_draft	job runner is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the job runner obligation named before work proceeds.
1100	label {Forge}	authored	generated_draft	label in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the label obligation named before work proceeds.
1101	lint	authored	generated_draft	lint is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the lint obligation named before work proceeds.
1102	lockfile	authored	reviewed	The file that freezes dependency resolution into repeatable history.
1103	manifest	authored	generated_draft	manifest is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the manifest obligation named before work proceeds.
1104	merge {Forge}	authored	reviewed	Reconcile divergent lines of history into one.
1105	migration script	authored	generated_draft	migration script is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the migration script obligation named before work proceeds.
1106	minifier	authored	generated_draft	minifier is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the minifier obligation named before work proceeds.
1107	package {Forge}	authored	generated_draft	package in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the package obligation named before work proceeds.
1108	package manager	authored	generated_draft	package manager is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the package manager obligation named before work proceeds.
1109	patch release	authored	generated_draft	patch release is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the patch release obligation named before work proceeds.
1110	pin	authored	generated_draft	pin is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the pin obligation named before work proceeds.
1111	pipeline {Forge}	authored	reviewed	The ordered automation that turns edit into tested artifact.
1112	precommit hook	authored	generated_draft	precommit hook is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the precommit hook obligation named before work proceeds.
1113	preview environment	authored	generated_draft	preview environment is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the preview environment obligation named before work proceeds.
1114	promote	authored	generated_draft	promote is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the promote obligation named before work proceeds.
1115	publish	authored	generated_draft	publish is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the publish obligation named before work proceeds.
1116	rebase	authored	generated_draft	rebase is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the rebase obligation named before work proceeds.
1117	release	authored	reviewed	A named version intended for actual users.
1118	release candidate	authored	generated_draft	release candidate is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the release candidate obligation named before work proceeds.
1119	repository {Forge}	authored	generated_draft	repository in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the repository obligation named before work proceeds.
1120	reproducible build	authored	reviewed	A build that can be rebuilt into the same bits again.
1121	restore {Forge}	authored	generated_draft	restore in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the restore obligation named before work proceeds.
1122	revision {Forge}	authored	generated_draft	revision in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the revision obligation named before work proceeds.
1123	rollback {Forge}	authored	reviewed	Operational permission to retreat after release.
1124	rollout	authored	generated_draft	rollout is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the rollout obligation named before work proceeds.
1125	scaffold {Forge}	authored	generated_draft	scaffold in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the scaffold obligation named before work proceeds.
1126	semantic version	authored	generated_draft	semantic version is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the semantic version obligation named before work proceeds.
1127	ship	authored	generated_draft	ship is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the ship obligation named before work proceeds.
1128	source map	authored	generated_draft	source map is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the source map obligation named before work proceeds.
1129	staging	authored	generated_draft	staging is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the staging obligation named before work proceeds.
1130	static analysis	authored	generated_draft	static analysis is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the static analysis obligation named before work proceeds.
1131	tag	authored	generated_draft	tag is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the tag obligation named before work proceeds.
1132	template {Forge}	authored	generated_draft	template in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the template obligation named before work proceeds.
1133	test gate	authored	generated_draft	test gate is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the test gate obligation named before work proceeds.
1134	toolchain	authored	generated_draft	toolchain is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the toolchain obligation named before work proceeds.
1135	transitive dependency	authored	generated_draft	transitive dependency is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the transitive dependency obligation named before work proceeds.
1136	upgrade	authored	generated_draft	upgrade is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the upgrade obligation named before work proceeds.
1137	version	authored	generated_draft	version is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the version obligation named before work proceeds.
1138	version pin	authored	generated_draft	version pin is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the version pin obligation named before work proceeds.
1139	workspace	authored	generated_draft	workspace is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the workspace obligation named before work proceeds.

107.2 Entries

107.2.1 [1064] artifact

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A produced thing you can store, ship, or compare.

Shadow: misusing artifact at rune 1064 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name artifact when the prompt needs this obligation made explicit: A produced thing you can store, ship, or compare.
• Ask the assistant to state the artifact shadow before proposing changes.

Example clause:

Before editing, state the artifact obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A produced thing you can store, ship, or compare.

107.2.2 [1065] assemble {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: assemble in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the assemble obligation named before work proceeds.

Shadow: misusing assemble at rune 1065 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name assemble when the prompt needs this obligation made explicit: assemble in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the assemble obligation named before work proceeds.
• Ask the assistant to state the assemble shadow before proposing changes.

Example clause:

Before editing, state the assemble obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.3 [1066] baseline {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: baseline in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the baseline obligation named before work proceeds.

Shadow: misusing baseline at rune 1066 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name baseline when the prompt needs this obligation made explicit: baseline in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the baseline obligation named before work proceeds.
• Ask the assistant to state the baseline shadow before proposing changes.

Example clause:

Before editing, state the baseline obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.4 [1067] binary

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: binary is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the binary obligation named before work proceeds.

Shadow: misusing binary at rune 1067 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name binary when the prompt needs this obligation made explicit: binary is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the binary obligation named before work proceeds.
• Ask the assistant to state the binary shadow before proposing changes.

Example clause:

Before editing, state the binary obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.5 [1068] branch {Forge}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A line of history where change can proceed without touching the main trunk.

Shadow: misusing branch at rune 1068 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name branch when the prompt needs this obligation made explicit: A line of history where change can proceed without touching the main trunk.
• Ask the assistant to state the branch shadow before proposing changes.

Example clause:

Before editing, state the branch obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A line of history where change can proceed without touching the main trunk.

107.2.6 [1069] build

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Turn source into a runnable or shippable artifact.

Shadow: misusing build at rune 1069 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name build when the prompt needs this obligation made explicit: Turn source into a runnable or shippable artifact.
• Ask the assistant to state the build shadow before proposing changes.

Example clause:

Before editing, state the build obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Turn source into a runnable or shippable artifact.

107.2.7 [1070] build cache

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: build cache is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the build cache obligation named before work proceeds.

Shadow: misusing build cache at rune 1070 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name build cache when the prompt needs this obligation made explicit: build cache is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the build cache obligation named before work proceeds.
• Ask the assistant to state the build cache shadow before proposing changes.

Example clause:

Before editing, state the build cache obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.8 [1071] build graph

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: build graph is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the build graph obligation named before work proceeds.

Shadow: misusing build graph at rune 1071 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name build graph when the prompt needs this obligation made explicit: build graph is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the build graph obligation named before work proceeds.
• Ask the assistant to state the build graph shadow before proposing changes.

Example clause:

Before editing, state the build graph obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.9 [1072] bundle

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: bundle is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the bundle obligation named before work proceeds.

Shadow: misusing bundle at rune 1072 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name bundle when the prompt needs this obligation made explicit: bundle is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the bundle obligation named before work proceeds.
• Ask the assistant to state the bundle shadow before proposing changes.

Example clause:

Before editing, state the bundle obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.10 [1073] canary

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A deliberately limited release whose job is to discover whether production reality agrees with the story told in staging.

Shadow: when the canary is too narrow to detect the failure the full population will hit.

Prompt uses:

• Name canary when the prompt needs this obligation made explicit: A deliberately limited release whose job is to discover whether production reality agrees with the story told in staging.
• Ask the assistant to state the canary shadow before proposing changes.

Example clause:

Before editing, state the canary obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A small production release meant to detect reality before full rollout.

107.2.11 [1074] changelog

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: changelog is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the changelog obligation named before work proceeds.

Shadow: misusing changelog at rune 1074 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name changelog when the prompt needs this obligation made explicit: changelog is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the changelog obligation named before work proceeds.
• Ask the assistant to state the changelog shadow before proposing changes.

Example clause:

Before editing, state the changelog obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.12 [1075] cherry-pick

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: cherry-pick is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the cherry-pick obligation named before work proceeds.

Shadow: misusing cherry-pick at rune 1075 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name cherry-pick when the prompt needs this obligation made explicit: cherry-pick is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the cherry-pick obligation named before work proceeds.
• Ask the assistant to state the cherry-pick shadow before proposing changes.

Example clause:

Before editing, state the cherry-pick obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.13 [1076] CI

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Continuous integration: change is merged only after automated checks speak.

Shadow: misusing CI at rune 1076 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name CI when the prompt needs this obligation made explicit: Continuous integration: change is merged only after automated checks speak.
• Ask the assistant to state the CI shadow before proposing changes.

Example clause:

Before editing, state the CI obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Continuous integration: change is merged only after automated checks speak.

107.2.14 [1077] codegen

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: codegen is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the codegen obligation named before work proceeds.

Shadow: misusing codegen at rune 1077 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name codegen when the prompt needs this obligation made explicit: codegen is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the codegen obligation named before work proceeds.
• Ask the assistant to state the codegen shadow before proposing changes.

Example clause:

Before editing, state the codegen obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.15 [1078] commit {Forge}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Record a change as one named point in history.

Shadow: misusing commit at rune 1078 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name commit when the prompt needs this obligation made explicit: Record a change as one named point in history.
• Ask the assistant to state the commit shadow before proposing changes.

Example clause:

Before editing, state the commit obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Record a change as one named point in history.

107.2.16 [1079] compile {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: compile in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the compile obligation named before work proceeds.

Shadow: misusing compile at rune 1079 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name compile when the prompt needs this obligation made explicit: compile in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the compile obligation named before work proceeds.
• Ask the assistant to state the compile shadow before proposing changes.

Example clause:

Before editing, state the compile obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.17 [1080] container {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: container in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the container obligation named before work proceeds.

Shadow: misusing container at rune 1080 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name container when the prompt needs this obligation made explicit: container in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the container obligation named before work proceeds.
• Ask the assistant to state the container shadow before proposing changes.

Example clause:

Before editing, state the container obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.18 [1081] container image

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: container image is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the container image obligation named before work proceeds.

Shadow: misusing container image at rune 1081 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name container image when the prompt needs this obligation made explicit: container image is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the container image obligation named before work proceeds.
• Ask the assistant to state the container image shadow before proposing changes.

Example clause:

Before editing, state the container image obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.19 [1082] continuous delivery

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: continuous delivery is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the continuous delivery obligation named before work proceeds.

Shadow: misusing continuous delivery at rune 1082 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name continuous delivery when the prompt needs this obligation made explicit: continuous delivery is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the continuous delivery obligation named before work proceeds.
• Ask the assistant to state the continuous delivery shadow before proposing changes.

Example clause:

Before editing, state the continuous delivery obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.20 [1083] continuous integration

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: continuous integration is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the continuous integration obligation named before work proceeds.

Shadow: misusing continuous integration at rune 1083 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name continuous integration when the prompt needs this obligation made explicit: continuous integration is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the continuous integration obligation named before work proceeds.
• Ask the assistant to state the continuous integration shadow before proposing changes.

Example clause:

Before editing, state the continuous integration obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.21 [1084] dependency

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Something your code needs in order to build or run.

Shadow: misusing dependency at rune 1084 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name dependency when the prompt needs this obligation made explicit: Something your code needs in order to build or run.
• Ask the assistant to state the dependency shadow before proposing changes.

Example clause:

Before editing, state the dependency obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Something your code needs in order to build or run.

107.2.22 [1085] dependency graph

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: dependency graph is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the dependency graph obligation named before work proceeds.

Shadow: misusing dependency graph at rune 1085 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name dependency graph when the prompt needs this obligation made explicit: dependency graph is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the dependency graph obligation named before work proceeds.
• Ask the assistant to state the dependency graph shadow before proposing changes.

Example clause:

Before editing, state the dependency graph obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.23 [1086] deploy

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: The crossing from forge to world. Many good ideas become bad facts only after they are actually shipped.

Shadow: when deployment is treated as success before runtime behavior and rollback are observed.

Prompt uses:

• Name deploy when the prompt needs this obligation made explicit: The crossing from forge to world. Many good ideas become bad facts only after they are actually shipped.
• Ask the assistant to state the deploy shadow before proposing changes.

Example clause:

Before editing, state the deploy obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Cross the line from forge to world.

107.2.24 [1087] deployment ring

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: deployment ring is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the deployment ring obligation named before work proceeds.

Shadow: misusing deployment ring at rune 1087 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name deployment ring when the prompt needs this obligation made explicit: deployment ring is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the deployment ring obligation named before work proceeds.
• Ask the assistant to state the deployment ring shadow before proposing changes.

Example clause:

Before editing, state the deployment ring obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.25 [1088] diff {Forge}

Status: canonical (major canon, pocket canon)

Completion: authored

Semantic status: reviewed

Force: A visible account of what changed between one state and another. Good diffs make review local; bad diffs turn truth into fog.

Shadow: when a small diff hides a large semantic, data, or operational change.

Prompt uses:

• Name diff when the prompt needs this obligation made explicit: A visible account of what changed between one state and another. Good diffs make review local; bad diffs turn truth into fog.
• Ask the assistant to state the diff shadow before proposing changes.

Example clause:

Before editing, state the diff obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A visible account of what changed between states.

107.2.26 [1089] distribution

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: distribution is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the distribution obligation named before work proceeds.

Shadow: misusing distribution at rune 1089 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name distribution when the prompt needs this obligation made explicit: distribution is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the distribution obligation named before work proceeds.
• Ask the assistant to state the distribution shadow before proposing changes.

Example clause:

Before editing, state the distribution obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.27 [1090] Dockerfile

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: Dockerfile is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the Dockerfile obligation named before work proceeds.

Shadow: misusing Dockerfile at rune 1090 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name Dockerfile when the prompt needs this obligation made explicit: Dockerfile is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the Dockerfile obligation named before work proceeds.
• Ask the assistant to state the Dockerfile shadow before proposing changes.

Example clause:

Before editing, state the Dockerfile obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.28 [1091] downgrade

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: downgrade is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the downgrade obligation named before work proceeds.

Shadow: misusing downgrade at rune 1091 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name downgrade when the prompt needs this obligation made explicit: downgrade is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the downgrade obligation named before work proceeds.
• Ask the assistant to state the downgrade shadow before proposing changes.

Example clause:

Before editing, state the downgrade obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.29 [1092] environment

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: environment is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the environment obligation named before work proceeds.

Shadow: misusing environment at rune 1092 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name environment when the prompt needs this obligation made explicit: environment is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the environment obligation named before work proceeds.
• Ask the assistant to state the environment shadow before proposing changes.

Example clause:

Before editing, state the environment obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.30 [1093] feature flag

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A runtime switch that separates deploy from release.

Shadow: misusing feature flag at rune 1093 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name feature flag when the prompt needs this obligation made explicit: A runtime switch that separates deploy from release.
• Ask the assistant to state the feature flag shadow before proposing changes.

Example clause:

Before editing, state the feature flag obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A runtime switch that separates deploy from release.

107.2.31 [1094] formatter

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: formatter is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the formatter obligation named before work proceeds.

Shadow: misusing formatter at rune 1094 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name formatter when the prompt needs this obligation made explicit: formatter is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the formatter obligation named before work proceeds.
• Ask the assistant to state the formatter shadow before proposing changes.

Example clause:

Before editing, state the formatter obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.32 [1095] hermetic build

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: hermetic build is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the hermetic build obligation named before work proceeds.

Shadow: misusing hermetic build at rune 1095 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name hermetic build when the prompt needs this obligation made explicit: hermetic build is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the hermetic build obligation named before work proceeds.
• Ask the assistant to state the hermetic build shadow before proposing changes.

Example clause:

Before editing, state the hermetic build obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.33 [1096] install

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: install is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the install obligation named before work proceeds.

Shadow: misusing install at rune 1096 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name install when the prompt needs this obligation made explicit: install is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the install obligation named before work proceeds.
• Ask the assistant to state the install shadow before proposing changes.

Example clause:

Before editing, state the install obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.34 [1097] installer

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: installer is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the installer obligation named before work proceeds.

Shadow: misusing installer at rune 1097 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name installer when the prompt needs this obligation made explicit: installer is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the installer obligation named before work proceeds.
• Ask the assistant to state the installer shadow before proposing changes.

Example clause:

Before editing, state the installer obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.35 [1098] issue tracker

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: issue tracker is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the issue tracker obligation named before work proceeds.

Shadow: misusing issue tracker at rune 1098 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name issue tracker when the prompt needs this obligation made explicit: issue tracker is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the issue tracker obligation named before work proceeds.
• Ask the assistant to state the issue tracker shadow before proposing changes.

Example clause:

Before editing, state the issue tracker obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.36 [1099] job runner

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: job runner is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the job runner obligation named before work proceeds.

Shadow: misusing job runner at rune 1099 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name job runner when the prompt needs this obligation made explicit: job runner is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the job runner obligation named before work proceeds.
• Ask the assistant to state the job runner shadow before proposing changes.

Example clause:

Before editing, state the job runner obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.37 [1100] label {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: label in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the label obligation named before work proceeds.

Shadow: misusing label at rune 1100 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name label when the prompt needs this obligation made explicit: label in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the label obligation named before work proceeds.
• Ask the assistant to state the label shadow before proposing changes.

Example clause:

Before editing, state the label obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.38 [1101] lint

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: lint is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the lint obligation named before work proceeds.

Shadow: misusing lint at rune 1101 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name lint when the prompt needs this obligation made explicit: lint is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the lint obligation named before work proceeds.
• Ask the assistant to state the lint shadow before proposing changes.

Example clause:

Before editing, state the lint obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.39 [1102] lockfile

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The file that freezes dependency resolution into repeatable history.

Shadow: misusing lockfile at rune 1102 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name lockfile when the prompt needs this obligation made explicit: The file that freezes dependency resolution into repeatable history.
• Ask the assistant to state the lockfile shadow before proposing changes.

Example clause:

Before editing, state the lockfile obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: The file that freezes dependency resolution into repeatable history.

107.2.40 [1103] manifest

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: manifest is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the manifest obligation named before work proceeds.

Shadow: misusing manifest at rune 1103 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name manifest when the prompt needs this obligation made explicit: manifest is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the manifest obligation named before work proceeds.
• Ask the assistant to state the manifest shadow before proposing changes.

Example clause:

Before editing, state the manifest obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.41 [1104] merge {Forge}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Reconcile divergent lines of history into one.

Shadow: misusing merge at rune 1104 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name merge when the prompt needs this obligation made explicit: Reconcile divergent lines of history into one.
• Ask the assistant to state the merge shadow before proposing changes.

Example clause:

Before editing, state the merge obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Reconcile divergent lines of history into one.

107.2.42 [1105] migration script

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: migration script is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the migration script obligation named before work proceeds.

Shadow: misusing migration script at rune 1105 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name migration script when the prompt needs this obligation made explicit: migration script is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the migration script obligation named before work proceeds.
• Ask the assistant to state the migration script shadow before proposing changes.

Example clause:

Before editing, state the migration script obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.43 [1106] minifier

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: minifier is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the minifier obligation named before work proceeds.

Shadow: misusing minifier at rune 1106 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name minifier when the prompt needs this obligation made explicit: minifier is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the minifier obligation named before work proceeds.
• Ask the assistant to state the minifier shadow before proposing changes.

Example clause:

Before editing, state the minifier obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.44 [1107] package {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: package in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the package obligation named before work proceeds.

Shadow: misusing package at rune 1107 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name package when the prompt needs this obligation made explicit: package in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the package obligation named before work proceeds.
• Ask the assistant to state the package shadow before proposing changes.

Example clause:

Before editing, state the package obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.45 [1108] package manager

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: package manager is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the package manager obligation named before work proceeds.

Shadow: misusing package manager at rune 1108 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name package manager when the prompt needs this obligation made explicit: package manager is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the package manager obligation named before work proceeds.
• Ask the assistant to state the package manager shadow before proposing changes.

Example clause:

Before editing, state the package manager obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.46 [1109] patch release

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: patch release is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the patch release obligation named before work proceeds.

Shadow: misusing patch release at rune 1109 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name patch release when the prompt needs this obligation made explicit: patch release is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the patch release obligation named before work proceeds.
• Ask the assistant to state the patch release shadow before proposing changes.

Example clause:

Before editing, state the patch release obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.47 [1110] pin

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: pin is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the pin obligation named before work proceeds.

Shadow: misusing pin at rune 1110 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name pin when the prompt needs this obligation made explicit: pin is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the pin obligation named before work proceeds.
• Ask the assistant to state the pin shadow before proposing changes.

Example clause:

Before editing, state the pin obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.48 [1111] pipeline {Forge}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: The ordered automation that turns edit into tested artifact.

Shadow: misusing pipeline at rune 1111 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name pipeline when the prompt needs this obligation made explicit: The ordered automation that turns edit into tested artifact.
• Ask the assistant to state the pipeline shadow before proposing changes.

Example clause:

Before editing, state the pipeline obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: The ordered automation that turns edit into tested artifact.

107.2.49 [1112] precommit hook

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: precommit hook is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the precommit hook obligation named before work proceeds.

Shadow: misusing precommit hook at rune 1112 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name precommit hook when the prompt needs this obligation made explicit: precommit hook is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the precommit hook obligation named before work proceeds.
• Ask the assistant to state the precommit hook shadow before proposing changes.

Example clause:

Before editing, state the precommit hook obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.50 [1113] preview environment

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: preview environment is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the preview environment obligation named before work proceeds.

Shadow: misusing preview environment at rune 1113 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name preview environment when the prompt needs this obligation made explicit: preview environment is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the preview environment obligation named before work proceeds.
• Ask the assistant to state the preview environment shadow before proposing changes.

Example clause:

Before editing, state the preview environment obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.51 [1114] promote

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: promote is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the promote obligation named before work proceeds.

Shadow: misusing promote at rune 1114 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name promote when the prompt needs this obligation made explicit: promote is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the promote obligation named before work proceeds.
• Ask the assistant to state the promote shadow before proposing changes.

Example clause:

Before editing, state the promote obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.52 [1115] publish

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: publish is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the publish obligation named before work proceeds.

Shadow: misusing publish at rune 1115 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name publish when the prompt needs this obligation made explicit: publish is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the publish obligation named before work proceeds.
• Ask the assistant to state the publish shadow before proposing changes.

Example clause:

Before editing, state the publish obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.53 [1116] rebase

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: rebase is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the rebase obligation named before work proceeds.

Shadow: misusing rebase at rune 1116 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name rebase when the prompt needs this obligation made explicit: rebase is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the rebase obligation named before work proceeds.
• Ask the assistant to state the rebase shadow before proposing changes.

Example clause:

Before editing, state the rebase obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.54 [1117] release

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A named version intended for actual users.

Shadow: misusing release at rune 1117 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name release when the prompt needs this obligation made explicit: A named version intended for actual users.
• Ask the assistant to state the release shadow before proposing changes.

Example clause:

Before editing, state the release obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A named version intended for actual users.

107.2.55 [1118] release candidate

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: release candidate is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the release candidate obligation named before work proceeds.

Shadow: misusing release candidate at rune 1118 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name release candidate when the prompt needs this obligation made explicit: release candidate is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the release candidate obligation named before work proceeds.
• Ask the assistant to state the release candidate shadow before proposing changes.

Example clause:

Before editing, state the release candidate obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.56 [1119] repository {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: repository in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the repository obligation named before work proceeds.

Shadow: misusing repository at rune 1119 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name repository when the prompt needs this obligation made explicit: repository in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the repository obligation named before work proceeds.
• Ask the assistant to state the repository shadow before proposing changes.

Example clause:

Before editing, state the repository obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.57 [1120] reproducible build

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: A build that can be rebuilt into the same bits again.

Shadow: misusing reproducible build at rune 1120 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name reproducible build when the prompt needs this obligation made explicit: A build that can be rebuilt into the same bits again.
• Ask the assistant to state the reproducible build shadow before proposing changes.

Example clause:

Before editing, state the reproducible build obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: A build that can be rebuilt into the same bits again.

107.2.58 [1121] restore {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: restore in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the restore obligation named before work proceeds.

Shadow: misusing restore at rune 1121 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name restore when the prompt needs this obligation made explicit: restore in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the restore obligation named before work proceeds.
• Ask the assistant to state the restore shadow before proposing changes.

Example clause:

Before editing, state the restore obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.59 [1122] revision {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: revision in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the revision obligation named before work proceeds.

Shadow: misusing revision at rune 1122 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name revision when the prompt needs this obligation made explicit: revision in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the revision obligation named before work proceeds.
• Ask the assistant to state the revision shadow before proposing changes.

Example clause:

Before editing, state the revision obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.60 [1123] rollback {Forge}

Status: canonical (pocket canon)

Completion: authored

Semantic status: reviewed

Force: Operational permission to retreat after release.

Shadow: misusing rollback at rune 1123 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name rollback when the prompt needs this obligation made explicit: Operational permission to retreat after release.
• Ask the assistant to state the rollback shadow before proposing changes.

Example clause:

Before editing, state the rollback obligation, the evidence that satisfies it, and the failure mode if it is missing.

Pocket gloss: Operational permission to retreat after release.

107.2.61 [1124] rollout

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: rollout is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the rollout obligation named before work proceeds.

Shadow: misusing rollout at rune 1124 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name rollout when the prompt needs this obligation made explicit: rollout is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the rollout obligation named before work proceeds.
• Ask the assistant to state the rollout shadow before proposing changes.

Example clause:

Before editing, state the rollout obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.62 [1125] scaffold {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: scaffold in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the scaffold obligation named before work proceeds.

Shadow: misusing scaffold at rune 1125 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name scaffold when the prompt needs this obligation made explicit: scaffold in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the scaffold obligation named before work proceeds.
• Ask the assistant to state the scaffold shadow before proposing changes.

Example clause:

Before editing, state the scaffold obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.63 [1126] semantic version

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: semantic version is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the semantic version obligation named before work proceeds.

Shadow: misusing semantic version at rune 1126 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name semantic version when the prompt needs this obligation made explicit: semantic version is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the semantic version obligation named before work proceeds.
• Ask the assistant to state the semantic version shadow before proposing changes.

Example clause:

Before editing, state the semantic version obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.64 [1127] ship

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: ship is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the ship obligation named before work proceeds.

Shadow: misusing ship at rune 1127 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name ship when the prompt needs this obligation made explicit: ship is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the ship obligation named before work proceeds.
• Ask the assistant to state the ship shadow before proposing changes.

Example clause:

Before editing, state the ship obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.65 [1128] source map

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: source map is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the source map obligation named before work proceeds.

Shadow: misusing source map at rune 1128 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name source map when the prompt needs this obligation made explicit: source map is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the source map obligation named before work proceeds.
• Ask the assistant to state the source map shadow before proposing changes.

Example clause:

Before editing, state the source map obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.66 [1129] staging

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: staging is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the staging obligation named before work proceeds.

Shadow: misusing staging at rune 1129 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name staging when the prompt needs this obligation made explicit: staging is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the staging obligation named before work proceeds.
• Ask the assistant to state the staging shadow before proposing changes.

Example clause:

Before editing, state the staging obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.67 [1130] static analysis

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: static analysis is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the static analysis obligation named before work proceeds.

Shadow: misusing static analysis at rune 1130 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name static analysis when the prompt needs this obligation made explicit: static analysis is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the static analysis obligation named before work proceeds.
• Ask the assistant to state the static analysis shadow before proposing changes.

Example clause:

Before editing, state the static analysis obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.68 [1131] tag

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: tag is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the tag obligation named before work proceeds.

Shadow: misusing tag at rune 1131 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name tag when the prompt needs this obligation made explicit: tag is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the tag obligation named before work proceeds.
• Ask the assistant to state the tag shadow before proposing changes.

Example clause:

Before editing, state the tag obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.69 [1132] template {Forge}

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: template in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the template obligation named before work proceeds.

Shadow: misusing template at rune 1132 in the Forge lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name template when the prompt needs this obligation made explicit: template in its Forge sense is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the template obligation named before work proceeds.
• Ask the assistant to state the template shadow before proposing changes.

Example clause:

Before editing, state the template obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.70 [1133] test gate

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: test gate is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the test gate obligation named before work proceeds.

Shadow: misusing test gate at rune 1133 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name test gate when the prompt needs this obligation made explicit: test gate is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the test gate obligation named before work proceeds.
• Ask the assistant to state the test gate shadow before proposing changes.

Example clause:

Before editing, state the test gate obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.71 [1134] toolchain

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: toolchain is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the toolchain obligation named before work proceeds.

Shadow: misusing toolchain at rune 1134 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name toolchain when the prompt needs this obligation made explicit: toolchain is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the toolchain obligation named before work proceeds.
• Ask the assistant to state the toolchain shadow before proposing changes.

Example clause:

Before editing, state the toolchain obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.72 [1135] transitive dependency

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: transitive dependency is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the transitive dependency obligation named before work proceeds.

Shadow: misusing transitive dependency at rune 1135 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name transitive dependency when the prompt needs this obligation made explicit: transitive dependency is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the transitive dependency obligation named before work proceeds.
• Ask the assistant to state the transitive dependency shadow before proposing changes.

Example clause:

Before editing, state the transitive dependency obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.73 [1136] upgrade

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: upgrade is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the upgrade obligation named before work proceeds.

Shadow: misusing upgrade at rune 1136 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name upgrade when the prompt needs this obligation made explicit: upgrade is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the upgrade obligation named before work proceeds.
• Ask the assistant to state the upgrade shadow before proposing changes.

Example clause:

Before editing, state the upgrade obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.74 [1137] version

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: version is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the version obligation named before work proceeds.

Shadow: misusing version at rune 1137 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name version when the prompt needs this obligation made explicit: version is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the version obligation named before work proceeds.
• Ask the assistant to state the version shadow before proposing changes.

Example clause:

Before editing, state the version obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.75 [1138] version pin

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: version pin is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the version pin obligation named before work proceeds.

Shadow: misusing version pin at rune 1138 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name version pin when the prompt needs this obligation made explicit: version pin is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the version pin obligation named before work proceeds.
• Ask the assistant to state the version pin shadow before proposing changes.

Example clause:

Before editing, state the version pin obligation, the evidence that satisfies it, and the failure mode if it is missing.

107.2.76 [1139] workspace

Status: canonical

Completion: authored

Semantic status: generated_draft

Force: workspace is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the workspace obligation named before work proceeds.

Shadow: misusing workspace at rune 1139 in the release lane can let automation can ship drift faster than people can inspect it; verify by requiring the caster to state artifact identity, gate, rollout, and rollback evidence.

Prompt uses:

• Name workspace when the prompt needs this obligation made explicit: workspace is a build, tooling, and release rune for make version, artifact, deployment, and rollback surfaces explicit; use it when the artifact needs the workspace obligation named before work proceeds.
• Ask the assistant to state the workspace shadow before proposing changes.

Example clause:

Before editing, state the workspace obligation, the evidence that satisfies it, and the failure mode if it is missing.