aeat.core._capabilities module¶

Closed set of operator-selectable service capabilities.

A capability is a per-profile opt-in/opt-out of an external service the app can use. It is operator intent, distinct from (a) the global safety posture (gestor mode, the secure-storage invariant) and (b) dependency availability (is Ollama running?). The three axes are ANDed at the gate, and a capability may only NARROW the global safety floor, never widen it (service-capabilities ADR).

The set is declared here in core/ — the innermost hexagonal ring — per aeat-schema-central-config and aeat-architecture-boundaries so the Typer boundary renders the accepted-value Choice([...]) from the enum, production code routes on members, and the profile schema / resolver / doctor share one authority for the capability identifiers.

The ServiceCapability members are consumed by resolve_capability(), resolve_active_capability(), and by the setup wizard’s capability questions. The product doctor renders those same members beside DependencyStatus rows from probe_ollama_vision(), probe_subprocess_providers(), and probe_optional_extras(), keeping operator intent separate from dependency availability.

This enum is deliberately separate from domain.calculations.registry.ModeloDefinition.capabilities and domain.calculations.registry.ModeloFilingCapability. Registry capabilities describe which workflows a modelo definition supports; service capabilities describe what an active profile permits the app to use.

class ServiceCapability(*values)[source]¶

Bases: StrEnum

The closed set of external-service capabilities a profile can opt into.

Each value is the dotted profile-schema field leaf under the capabilities section (capabilities.<value>) so the enum, the schema fact path, and the resolver agree on one identifier. Optional package availability is modeled separately through OptionalExtra and require_optional_extra(); a capability records whether the profile permits the service, not whether its import/runtime dependency is installed.