#root{display:none}.faq__panel{grid-template-rows:1fr!important;visibility:visible!important}[data-reveal]{opacity:1!important;transform:none!important}Skip to content

The method

What Plyvel does, what its receipt proves, and what stays with the architect.

Diagram, not a render. Plyvel renders every layer of the model. Here one changes, the light from day to dusk, and the rest stays as drawn.

What happens to an image

A project starts from a model, an image pair or the included example. Plyvel lays the result over the approved image, pixel for pixel.

Fixed checks measure whether the camera or the edges moved, whether light was blown out and, when masks are supplied, whether the building outline changed. Each shows its value and its limit, and says when a limit is not yet validated.

Openings, thin features and visual artefacts are not measured in this release; they show as not measurable and go to the reviewer. Signage, and the outline without masks, show as not applicable; the reviewer checks them by eye.

Dusk render of the example pavilion — **Colour difference, not geometry.** Where the light changed. At dusk the light changes almost everywhere, so the map is red almost everywhere. It shows changed pixels, not a moved design. (The audit’s colour-difference map of the example, over the daylight base in grey; the method is in the docs.)

Colour-difference map of the example over the daylight base in grey: most of the frame is marked red because the lighting changed almost everywhere — **Colour difference, not geometry.** Where the light changed. At dusk the light changes almost everywhere, so the map is red almost everywhere. It shows changed pixels, not a moved design. (The audit’s colour-difference map of the example, over the daylight base in grey; the method is in the docs.)

At dusk, dark areas go to a person

A dusk result is reviewed against the daylight base under the dusk review policy. New bright clipping above the limit blocks export. New darkness is never approved automatically; it is shown as dark areas needing review, and the raw detector result is kept as measured.

A person signs before export

Review opens only when no check failed. The reviewer confirms each group, writes a separate observation for it and signs with a name. Nothing is preselected and no note is copied between groups.

Plyvel then verifies the evidence again, signs the receipt and packages the archive. The download exists only after that succeeds.

What the receipt proves

Proves

Which approved image, result and rules were used, each fixed by its fingerprint (hash).
What each check measured, against which threshold, and which thresholds are still engineering hypotheses.
That a named reviewer confirmed each review group and wrote an observation for it.
That the exported archive has not been altered since it was signed.

Does not prove

That the building is dimensionally accurate, buildable or compliant.
That the reviewer is who they say they are.
That details it did not measure, such as windows and doors, are preserved.
That the image is a photograph. It is not.

Where it runs

Today everything runs on the architect’s own computer for a single user: no accounts, no sharing, no history beyond the project list. Uploads and projects stay in the local data folder.

See it on the example

Review the included example in your browser: compare the renders, read the measured checks and fill in the review. Nothing is saved or sent.

Try a review