Workflow Gate
Enforcement Modes
Section titled “Enforcement Modes”The workflow gate runs taste gate run against changed files and returns an exit code based on the enforcement mode:
| Mode | Behavior | Exit Code |
|---|---|---|
| advisory | Report verdicts, never block | Always 0 |
| warn | Report verdicts, exit 1 only for contradictions | 0 or 1 |
| required | Exit 1 for any verdict below mostly_aligned | 0 or 1 |
Gate Policy
Section titled “Gate Policy”Each repo has a gate policy that controls enforcement per artifact type:
taste gate policy-init # Create default policytaste gate policy-show # View current policyThe policy file (.taste/gate-policy.json) maps artifact types to enforcement modes:
{ "default_mode": "advisory", "surfaces": [ { "artifact_type": "readme", "mode": "required", "globs": ["README.md"] }, { "artifact_type": "feature_brief", "mode": "warn", "globs": ["docs/briefs/**"] }, { "artifact_type": "architecture_note", "mode": "required", "globs": ["docs/arch/**"] } ]}Running the Gate
Section titled “Running the Gate”# Review all changed files (uses git diff)taste gate run
# Review specific filestaste gate run --files path/to/artifact.md
# In CItaste gate run || exit 1The gate detects artifact types automatically and applies the matching policy mode.
Override Receipts
Section titled “Override Receipts”When a required-mode artifact fails but must ship anyway, record an override:
taste gate override --artifact path/to/file.md --reason "Shipping for deadline, will fix in follow-up"Overrides create a receipt — a permanent record that includes:
- Who overrode
- When
- Why
- The verdict at time of override
taste gate report # Rollout report including override historyPromotion Doctrine
Section titled “Promotion Doctrine”Repos typically start in advisory mode and promote surfaces to warn then required as canon matures:
- advisory — Run reviews, build confidence in canon quality
- warn — Block contradictions, let drift through with warnings
- required — Full enforcement, overrides needed for exceptions
The promotion queue (in org mode) tracks which surfaces are ready for the next level based on:
- Canon confidence (enough curated statements)
- Review history (consistent verdicts)
- Override rate (low overrides = healthy canon)
Rollout Report
Section titled “Rollout Report”taste gate report --dir /path/to/repoShows per-artifact-type breakdown:
- Current enforcement mode
- Review count and verdict distribution
- Override count and rate
- Promotion readiness assessment