X. Pool Fixity

MINT has two submission modes because asset creation and asset servicing are different operations. At origination, the engine assigns a mint_invoice_id to each eligible receivable, locks the pool inside a mint_asset_id, and produces the asset itself. After that point, surveillance cannot redefine the pool. It can only update the status of invoices already admitted. Collections, aging migration, disputes, paydowns, and remaining balance move; pool membership does not. New invoices are rejected. Missing invoices are flagged. That boundary is load bearing. Investors are not buying a shifting spreadsheet. They are buying a fixed asset whose state can be measured over time.

Trigger 1 creates the asset. Trigger 2 reports on the asset.

The pool is fixed at origination. Surveillance is one directional and bounded by what origination already defined.