A city regression suite must fail builds when ordinance answers stop including required citation formatting. What testing practice enforces that standard?
Select an answer to reveal the explanation.
Short Explanation
If the ordinance bot forgets its footnotes, the build should fail like a broken unit test. Automated regression on citation format keeps civic answers accountable every release—not once a year in a binder.
Full Explanation
Regression tests that assert required citation formats (and related quality standards) on model outputs enforce the standard when a city suite must fail builds if ordinance answers stop including required citation formatting. Automated assertions on outputs make citation compliance a continuous release property instead of an occasional manual finding, catching prompt, model, or template regressions before production. That keeps civic answers accountable and auditable every build. Manual eyeballing once a year with no automated checks fails by concept: annual review cannot gate continuous delivery or catch interim regressions. Passing builds whenever the container image builds successfully, regardless of answer format, fails by concept—image build success says nothing about citation formatting in generated answers. Deleting citation requirements from the product spec to avoid test failures fails by concept and governance: removing the requirement to silence tests undermines transparency residents and auditors expect. Exam caveat: output-quality standards belong in automated regression gates, not annual eyeballs, infra-only green builds, or spec deletion. Operational check: encode citation-format checks in the CI regression suite against a fixed ordinance Q&A set, fail the build on missing or malformed citations, notify content owners, and prohibit removing citation requirements without governance approval.