Exit condition catalog

An extensive, browsable catalog of candidate exit conditions to consider for a project, organized by Definition-of-Done type. The shipped default library is deliberately small; this catalog is for inspiration — browse it and adopt the conditions that fit your project.

Each entry pairs a stable id with a one-line description of what it checks.

Adopting a condition

To add a catalog condition to a project, reference it by its id:

  • In a policy — an organization adds the id under exit_conditions in its governance policy, so every project it governs inherits the condition. See Policies.

  • In your project — ask your AI coding assistant to add the condition to your definition of done during /akka:specify, naming the id.

Whether an id ships in the default library or not, adopting it requires a covering auditor for the surface it checks. Akka ships a small set of built-in introspective auditors (for example mvn compile, git-secrets, and vale); beyond those, an auditor is authored per ecosystem as an inline command, provisioned as a harness asset, or delegated to a recorded attestation. There is no large, closed catalog of checks you pick from by id. Ids present in the default library arrive with their condition already defined; adopting any catalog id means authoring or wiring the covering auditor — one of the three kinds — that decides its invariant.

Point your assistant at this catalog

Paste this into your AI coding assistant to have it mine the catalog for conditions that apply to what you are building:

Review the Akka exit condition catalog at
https://doc.akka.io/reference/specify/catalog/ and, for the feature I am
building, propose the exit conditions that apply. List them by id, grouped by
Definition-of-Done type, and add the ones I approve to my definition of done.

Catalogs by type

Product — does the software work?

Project — is the codebase healthy and standards-compliant?

Process — did the AI build stay honest and efficient?

Related