Skip to content

Workflow Gate

The workflow gate runs taste gate run against changed files and returns an exit code based on the enforcement mode:

ModeBehaviorExit Code
advisoryReport verdicts, never blockAlways 0
warnReport verdicts, exit 1 only for contradictions0 or 1
requiredExit 1 for any verdict below mostly_aligned0 or 1

Each repo has a gate policy that controls enforcement per artifact type:

Terminal window
taste gate policy-init # Create default policy
taste gate policy-show # View current policy

The 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/**"] }
]
}
Terminal window
# Review all changed files (uses git diff)
taste gate run
# Review specific files
taste gate run --files path/to/artifact.md
# In CI
taste gate run || exit 1

The gate detects artifact types automatically and applies the matching policy mode.

When a required-mode artifact fails but must ship anyway, record an override:

Terminal window
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
Terminal window
taste gate report # Rollout report including override history

Repos typically start in advisory mode and promote surfaces to warn then required as canon matures:

  1. advisory — Run reviews, build confidence in canon quality
  2. warn — Block contradictions, let drift through with warnings
  3. 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)
Terminal window
taste gate report --dir /path/to/repo

Shows per-artifact-type breakdown:

  • Current enforcement mode
  • Review count and verdict distribution
  • Override count and rate
  • Promotion readiness assessment