Module engine 

The behavioral capability model engine (docs/design/behavioral-taxonomy-v1.4.md).

facet is the capability vocabulary (v1.4 §2), level the predicate language (§4.1), authoring compiles the level TOML, resolve turns a command into a profile, and bridge runs the engine AUTHORITATIVELY: leaf_verdict uses engine_verdict(tokens).unwrap_or(legacy), so for every command the engine can resolve, its verdict wins — the legacy classifier is only the fallback. See the behavioral-taxonomy-engine annex.

Modules

archetype

Static capability archetypes (docs/design/behavioral-taxonomy-archetypes.md). The recurring facet profiles the Phase-1 subcommand surface classifies against. Each archetype is a fixed Capability declared in archetypes.toml; a subcommand references one by name (profile = "remote-mutate") and the resolver emits that capability directly (a static profile — the sub’s facets don’t depend on its arguments, unlike the operand-role commands of Phase 0).

authoring

Compiling level TOML into Level values (v1.4 §4.1) — the analogue of build_command for the level language.

bridge

Engine bridge (v1.4 §4.5; annex …-engine §4). Projects a resolved capability profile back to a legacy Verdict so the existing ceiling gate (main::run_cli) keeps working unchanged. The engine is authoritative for every command it can resolve (resolve::resolve → Some); the legacy classifier handles the rest. There is no opt-out — cst::check::leaf_verdict calls engine_verdict(tokens).unwrap_or(legacy).

facet

The capability vocabulary — the 12 facets of v1.4 §2.

level

Safety levels as predicates over profiles (v1.4 §4.1).

resolve

The profile resolver — turning a parsed command into its behavior profile (annex behavioral-taxonomy-engine). Runs via engine::bridge, which is AUTHORITATIVE for every command it can resolve (engine_verdict(tokens).unwrap_or(legacy) in cst::check::leaf_verdict) — there is no opt-out.