mode

User Input

You MUST consider the user input before proceeding (if not empty).

Purpose

/akka:mode shows the project's conformance mode, or sets it. The mode is recorded in .akka/exit-conditions.yaml and controls exactly one thing: whether unmet exit conditions block shipping.

• À la carte — the default. The exit-condition set is dormant until the developer asks for it: only the Akka-intrinsic baseline resolves, no auditors are created, and nothing is captured. Once asked for, conditions are checked and shown but never block /akka:ship, which proceeds with an explicit override.
• Enforced — the full set applies from the start. /akka:ship refuses to release until every applicable condition is green and not stale, or covered by an effective waiver. You use sign-off, strike, and waive to resolve each open or red condition first.

Every Specify command is available in both modes; the mode changes what the engine does on its own, not the command set. In Enforced mode the process gates PROC-AUDITOR-COVERAGE and PROC-ADEQUACY-REVIEWED apply as usual. While the set is dormant they do not resolve at all — there is nothing yet to have covered or reviewed.

The organization can constrain this. A policy may set a different default and lock it; when the mode is locked, only the org-allowed mode(s) may be set. A locked Enforced mode cannot be dropped to À la carte to bypass the ship gate.

Outline

1. Parse the argument from the user's request. Three cases:

   • Empty — this is a query. Skip to step 2 with no argument.
   • enforced or a-la-carte — pass through unchanged.
   • A recognizable spelling of à la carte — the documentation renders the mode as "À la carte", so accept alacarte, a la carte, à-la-carte, and à la carte and normalize them to a-la-carte before calling the CLI. The CLI accepts only the two canonical spellings.

   Anything else: stop and tell the user "/akka:mode takes enforced or a-la-carte, or no argument to show the current mode." Do not call the CLI.