Default exit-condition library
The default library is the curated set of exit conditions Akka Specify starts from, organized by Definition-of-Done type. It is what makes the definition of done rich by default instead of empty. See Exit conditions and Definition of Done for the model.
Two kinds of default
| Provenance | Behavior |
|---|---|
|
Guarantees the Akka platform provides — observability, resilience, scalability. Always on, asserted green, and never authored or disabled by a developer. They document what Akka covers in the rollup ("Resilience: covered by Akka") and lighten how much a developer has to define. |
|
Best-practice conditions the tooling proposes for a feature. On by default; a developer can strike any that do not apply. |
Default-rich, opt-out
The library is deliberately rich, and the developer strikes what is inapplicable — it is never sparse-by-default with conditions you must remember to add. The asymmetry justifies it: the cost of a wrong default is one recorded strike, while the cost of a missing opt-in is shipping without a condition nobody remembered.
Strikes are:
-
Bounded — a developer cannot strike an organization-locked condition.
-
Recorded — every strike is captured in the conformance receipt with its reason.
-
Grouped — related conditions strike together. Declaring a service headless or API-only strikes the whole Experience cluster (accessibility, page performance, responsive layout) in one gesture.
During the DEFINE step the engine proactively suggests a strike when it is confident one applies (for example, no UI framework or routes are present), but still requires explicit confirmation.
Library conditions and their ids
Every library condition has a stable id. That id is the registry key: a policy names it in a ref: field to adopt and govern the condition (see Policies), and the tooling resolves the id back to the condition’s type, invariant, and pass predicate. The library supplies the exit condition; its covering auditor is one of the three auditor kinds. Akka ships a small set of built-in introspective auditors (for example mvn compile, git-secrets, and vale); the rest are authored per ecosystem, provisioned as a harness asset, or delegated to an attestation. The complete shipped library:
| Id | Type | Governance level | What it checks |
|---|---|---|---|
|
Operability |
|
Distributed tracing and observability, provided by the platform (akka-intrinsic, asserted). |
|
Reliability |
|
Supervision and recovery, provided by the platform (akka-intrinsic, asserted). |
|
Reliability |
|
Cluster sharding and scale-out, provided by the platform (akka-intrinsic, asserted). |
|
Functional |
|
The test suite passes ( |
|
Data Integrity |
|
Entity invariants hold against a running service. |
|
Security & Compliance |
|
Authorization is enforced against a running service. |
|
Operability |
|
The service compiles ( |
|
Performance |
|
Core Web Vitals and a bundle-size budget (UI-only). |
|
Experience |
|
WCAG 2.1 AA accessibility (UI-only, human sign-off). |
|
Pipeline & Scanning |
|
Prior commits passed CI. |
|
Pipeline & Scanning |
|
Static analysis (SAST) reports no findings. |
|
Pipeline & Scanning |
|
Prohibition. No secrets are committed to source or history ( |
|
Repository Hygiene |
|
Clean git tree, rebased on base, no orphaned code. |
|
Repository Hygiene |
|
Prohibition. No build output ( |
|
Code & Test Health |
|
Line/branch coverage at or above a threshold. |
|
Documentation & Training |
|
Architecture decision records are present (human sign-off). |
|
Environment & Dependencies |
|
The project’s environment setup is current. |
|
Environment & Dependencies |
|
Declared dependencies resolve ( |
|
Environment & Dependencies |
|
Prohibition. No dependency is unpinned; a lockfile or |
|
Content & Brand Governance |
|
Prohibition, off by default. Prose passes the content class’s Vale configuration ( |
|
Content & Brand Governance |
|
Off by default. Prose passes an attested tone judge (delegated). |
|
Process Integrity |
|
API usage is cited to official documentation; invented APIs are caught under coverage. |
|
Process Integrity |
|
Every material build surface has a covering auditor (the coverage gate). |
|
Process Integrity |
|
A fresh adequacy review covers every active auditor. |
|
Build Efficiency |
|
The build stays within its time budget (human sign-off). |
|
Four library conditions are prohibitions — a prohibition must never become true, and an unaudited prohibition is red rather than open: |
Some conditions are UI-only and apply only when a feature has a user interface; for a headless Akka service they are struck as a group. The catalog of further candidates to consider is in the exit condition catalog.
Organization control
An organization can promote a recommended default to a locked, mandatory condition, or disable one across the whole organization, through its governance policy. See Policies.