aeat.application.operator_surface package

Public re-export boundary for the backend-owned operator surface.

The package collects the application-layer command-shape declarations from application.operator_surface._contract, application.operator_surface._models, application.operator_surface._help, application.operator_surface._crud_contract, application.operator_surface._crud_registry, and application.operator_surface._errors. Command adapters consume this surface as data and render it; they do not define a second contract.

Root-surface declarations flow through get_operator_surface_contract(), ACCEPTED_ROOTS, MOUNTED_COMMAND_FAMILIES, and OperatorSurfaceContract. Source-kind aliases remain parser-only SourceKindAlias records that resolve through resolve_source_kind_alias() to canonical core.BindingSourceKind members. No operator-specific source-kind taxonomy is introduced here.

The CRUD vocabulary is exposed through CrudVerb, CANONICAL_CRUD_VERBS, MutatingNounGroupContract, CrudContractCatalogue, and get_builtin_catalogue(). Help and landing surfaces are exposed through build_help_document(), build_root_landing_report(), HelpDocument, and RootLandingReport. Refused surfaces use the registered OperatorSurfaceContractError path shared with require_accepted_root().

The agent-facing capability manifest is assembled by build_operator_surface_manifest() from the cached OperatorSurfaceContract plus CLI-owned JSON schema references. The application layer owns the command contract and mutability taxonomy; entrypoint adapters own rendering, command-tree traversal, and schema-registry enumeration.

See also

aeat app contract

Command adapter that emits the OperatorSurfaceManifest through the CLI envelope.

entrypoints.mcp

Tool-exposure entrypoint that consumes the same manifest without duplicating the operator-surface contract.

core.json_contract

CLI result-schema registry supplied to the manifest by entrypoint adapters.

Submodules