cadrumo.application.filing.errors module

Typed terminal-refusal transport for application.filing.

The domain filing package owns record, import, export, amendment, and builder error taxonomy. This application boundary owns the operator-facing outcome of its own refusals: every reachable application refusal carries the shared typed precondition record and a fact-only, explicitly non-actionable disposition. The classes below still inherit their corresponding domain error, preserving the established catch boundary without making the domain import application or CLI authority.

See also

domain.filing.errors

Domain filing error hierarchy raised by draft, import, and export records.

class FilingPreconditionCondition(*values)[source]

Bases: StrEnum

Application-owned failed conditions for filing-boundary refusals.

OPERATION_ADMISSIBLE
filing_no_recovery_verdict(condition, *, facts, outcome=NoRecoveryOutcome.OPERATOR_DECISION)[source]

Return the terminal, fact-only outcome for one filing refusal.

Filing can identify the rejected record, receipt, or configuration fact, but none of these direct application services owns a safely executable recovery command. The operator-surface resolver therefore receives an explicit no-recovery outcome instead of an application-authored command.

Return type:

PreconditionVerdict

Parameters:
exception ModeloApplicationError(message=None, *, context=None, translated_message=None, precondition_verdict=None)[source]

Bases: _FilingTerminalErrorMixin, ModeloBuilderError, ModeloImportError, FilingExportError

Base class for errors raised by the filing application layer.

The class remains an instance of the domain builder, import, and export catch families. Those direct application boundaries share one registered error envelope, and changing their concrete type must not discard a caller’s established domain catch while adding terminal transport.

Parameters:
Return type:

None

precondition_condition: ClassVar[FilingPreconditionCondition]
code