aeat.application package

Application layer orchestration boundary.

Application services coordinate domain authorities with adapters infrastructure and core primitives. This layer is allowed to wire concrete persistence, inbound, and outbound adapters; domain and core code must not depend back on it, and entrypoint modules should stay thin transports over the public application facades.

Regulatory formulas, schema authority, and legal classification stay in domain packages (especially domain.calculations.registry). Application services assemble inputs, persistence, readiness checks, and operator workflows around those authorities; they should not become parallel tax-law engines.

Public subpackage boundaries such as modelo and user_profile are the preferred import surfaces for cross-package consumers. Import from those package facades, not private _... implementation modules; the facade __all__ contract is the service boundary. The root package intentionally stays import-light so state-free CLI paths do not pay for registry, storage, browser, or workflow subtrees unless a specific command asks for them.

Operator state and readiness converge through state_projection: the OperatorStateProjection built by build_operator_state_projection() feeds overview status, auth status/test, and modelo readiness without giving those facades separate store-reading paths. Workflow orchestration remains in workflow; live AEAT access stays read-only under live; and diagnostics / repair surfaces stay in diagnostics and repair_integrity so operator health checks do not leak into domain authorities.

See also

modelo:

Modelo work-unit, calculation, verification, filing, export, and reconciliation facade.

filing:

Registry-backed local filing draft construction, review, export, and justificante import facade.

user_profile:

Lazy profile lifecycle, validation, storage-session, and projection facade.

workflow:

Workflow run, active-profile, bucket-discovery, and resume facade.

auth:

Operator auth configuration, status/test, session, and preflight facade.

overview:

Read-only operator dashboard projections built from state, deadlines, and filing evidence.

aggregation:

Calculation source mesh that supplies registry binding values from ledger, invoice, profile, relation, and carry inputs.

registry:

Read-only registry tree, corpus, manual, and filed-state verification services over validated registry authority.

operator_surface:

Backend-owned operator capability contract consumed by CLI adapters and automation surfaces.

ledger:

Bucket-scoped transaction lifecycle and ledger preflight facade used by modelo calculation readiness.

Subpackages

Submodules