[zxv]

A recursive invoice can omit surrendered helper credit or belong to a different recipe with the same histogram. This adds a reusable independent checker that extracts the paid/target invoice from the literal native word, ownership contract and p16/a7 caller before pricing.

The checker ignores author pricing functions and declared invoice tables. It checks exact symbolic borrowed endpoints, owned erasure, zero retags, native frame transports and independently derived paid ranks. It executes the caller’s boundary programs and Laurent events, derives its diagonal, and multiplies each local contribution by its actual call sites. Fixed main port/endpoint checks prevent a changed native boundary from inheriting the p16 tariff.

The output includes a source-bound claim, an invoice compatible with #5397, and an event ledger with explicit surrendered targets. It precedes the evidence-compatibility oracle in #5391 by @Clear1nsight.

On the actual #5383 and #5387 words, it independently reconstructs 64,148 paid calls and 10,800 productive targets, including all 128 surrendered H9 credits. Their backward scalar allowances remain distinct: 158,744 versus 158,776. An equal histogram cannot transfer a claim between their different source bindings.

Validation

Normal and optimized registered checks pass for three complete source recipes and 24 controls, including actual source mutations, false zero retags, native residuals, changed main endpoints, omitted target/query/idle charges and stale source bindings. Full CLI output, signed-preflight compatibility, committed bytes, export integrity and optimized Git-free replay pass.

Scope and credit

Only research/source-invoice-conformance/ is added. The result establishes symbolic source-protocol and recursive-invoice conformance. Physical fresh-stage/coordinate embedding, absolute phase, precision/tape implementation, ordinary-work funding, compiler and analytic recovery remain separate obligations. The selected frontier is unchanged; full source-history checking is unavailable in the shallow checkout.

Credit @intqwq's selected word, @aliromman's owned-relation construction, @Dugongue's successor and the retained caller/native/analytic lineage. Substantial OpenAI Codex assistance in implementation, source interpretation and assisted review; predecessor attribution is preserved.