# closure — the proof that what was rendered is what was planned
A plan is written before anything exists.
A rendering is what a renderer actually produced.
This home is where the two meet, and it does not ask the renderer whether it obeyed.
## A reconstruction, not an assertion
The membership is REBUILT out of the rendered units, seat by seat, by reading each unit's own answers, and the rebuild is then compared against the membership the plan declared.
Every disagreement is a typed issue that names its seat where it is about one, while disagreements about the reconstruction or a delivery remain whole rather than being assigned to a seat nobody established.
The last comparison is made over the whole set rather than seat by seat, because a walk comparing one member per seat would agree about two memberships that differ in their second.
## One emission per delivery
An expansion does not hand a compiler one stream.
Material compiled at the declaration site, deferred to another target, or written to an address occupies a distinct delivery posture, and every seat names exactly one of them.
So a closure does not join a rendering; it PARTITIONS one, and each joined delivery is built by walking the rendered units in roster order and reading the delivery each unit's seat declares.
Artifacts are never joined: two artifacts are two addresses, and one stream claiming to be both is what the address check refuses.
A join that outgrows the token magnitude names the delivery it overran at, because each joined delivery is its own byte stream and a caller cutting another one has repaired nothing.
The emission claims nothing about the vehicles.
Whether a carrier's shell has been rendered, what it is named, and whether any target invokes it are the consumption side's facts; whether a publication ever wrote an artifact is the publication road's.
## The emission is inside the proof
The closure builds every joined delivery itself, keeps them, and commits to their digests inside its own identity.
So the exact byte stream each build receives is part of what was proved rather than something assembled afterwards, and a rendering that moved one member to another delivery is a different closure rather than the same one emitted differently.
Holding a closure is the proof; there is no partial closure and no closure with a warning attached.
The road from a proof to its emissions is crate-internal.
Tokens are reached through the expansion that binds this proof to the plan it was proved against and the explanation answered over the two — a road out of here would be a road to emission that skips the binding, which is the same as no binding.
## How it says no
Closure issues are independent and co-establishable, so a refusal carries every issue its pass established rather than electing a primary one.
A body that fills its bound keeps what fits and counts the rest, which is a different statement from "no further disagreements exist".
The refusal is an ordinary error: it prints, it is a `core::error::Error`, and it projects into a diagnostic through the one contract every refusing step implements.
## Ownership
This home owns the closure issues, the independent reading of rendered units, the reconstructed membership, the partition by declared delivery, the exact joined bytes, and the identity and diagnostic contracts over those facts.
It does not own rendering policy, delivery vehicles, target invocation, or publication; a closure proves only the material it reconstructed and retained.