Live in this page: the composition planner, and the lineage floor — the weakest link, the binding jurisdiction, the agent-versus-person axis, the staleness window, and where the decision goes when a precondition is not met. Those are computed by 26-settlement/lib/lineage.js and lib/plan.js, the same bytes the Node suite pins, bundled at 52115 bytes.
Not in this page: the settlement gate itself — the four-operand commitment, the attestation reader, the no-egress store, the octet comparison and the transparency structure. They compute digests and verify signatures and they run where the keys are. A browser copy would be a weaker copy demonstrating something the product does not do.
The rows below are a worked example, not your record. They are here so the page is legible before anybody types anything. Replace them with your own values, or empty the form and start from nothing.
One row per upstream link. Everything below is what a sealed receipt already carries; nothing here is invented by this page.
3 · The instruments in force
PaymentVerification — lineage finding
This sheet is the finding and the inputs it was computed from. The form that produced it is on screen and is deliberately not printed: everything it contained is restated below, so this page can be checked without it. Nothing here is sealed and nothing here is legal advice.
The finding
PaymentVerification · standalone install · one product · built by 27-console/build-console.js from the register, not typed.
This page loads nothing from another origin, makes no request at run time, and touches no browser storage. It works from a file on disk with no server.