Decide whether the only implemented workflow is correct, tested and has one canonical copy, so later milestones build on a sound base.
Decide whether the released code metrics workflow can be called with its documented defaults, and correct it if it cannot.
Decide whether a DevOps professional can onboard a repository, set up credentials, choose runners and diagnose a failed run from the documentation alone.
Decide whether a software engineer can run the same quality checks on any TirSystem project through a shared workflow.
Decide whether the wiki can be published by a reusable workflow that each repository calls, from docs/wiki/ (the location process/wiki.md of the framework prescribes), instead of a scoped workflow that runs in every repository of the organisation and reads wiki/.
Decide whether workflow updates can be released with a version and adopted safely, and whether a project can publish an artifact through a shared workflow.
Decide whether the scoped publish-wiki.yml can be removed: every repository that publishes its wiki through it has moved to docs/wiki/ and calls the reusable workflow publish-wiki-pages.yml, and ADR-0004 is superseded by ADR-0009. MIL-008 deprecated the scoped workflow and kept it because seven repositories still depended on it (checked on 2026-10-13).
Decide whether a reader can find the workflow documentation on the Gitea wiki in English, Danish and Bahasa Malaysia, and whether the wiki stays current because every pull request updates it.
Decide whether any repository on the instance can publish its own wiki from a wiki/ folder through one shared workflow, without a copy of the workflow and without risk to repositories that did not ask for it.
Decide whether a repository can show, as SVG badges, how many code files and how many lines of code (without comment and blank lines) it holds and how much of that code its tests cover, produced by one shared workflow of this repository, without a service outside the instance.