cadrumo.application.ledger.invoice_extraction_authority module¶

Resolve the regulatory values an invoice-reading prompt enumerates.

The reading prompt names Spanish IVA rates, statutory retención rates, the categories of document that print no tax at all, and the regime mentions an issuer is obliged to print. Every one of those is a regulatory value, so aeat-registry-authority-flow puts its home in the registry rather than in the module that happens to consume it – they are versioned by filing year, and a copy taken anywhere else bakes one year’s law into that call site.

Why the resolution lives HERE and not beside the prompt. The prompt is rendered in the llm package, which is an adapter over a model transport. An adapter that reaches into iva and transactions to look up a rate has made itself a second consumer of the calculation authorities, and the hexagonal direction this project keeps says the application layer resolves and the adapter receives. So the resolution is done once here and handed down as ONE typed value object; the renderer substitutes what it is given and can no longer reach an authority at all.

That is a stronger guarantee than “we remembered not to write 21”. A literal in a prompt is the least-audited literal in the codebase – nothing type-checks it, no gate reads it, and a stale rate keeps steering a reading model silently. Removing the renderer’s access to the authorities means the only rate it can print is one this function resolved.

Every overlapping record, not the one in force on a chosen day. A period is a span, and RD-ley 4/2024 stepped part of the reducido and super-reducido tiers mid-year. Reading the table on one date inside such a period would omit a rate that documents dated inside the same period genuinely print, and the prompt would then be telling a model that a rate it can see on the page is not registered.