Product

Projects and views

A project holds one building or scheme. A view is one camera angle of it, such as Front Exterior or Living Room, numbered like a drawing set: 01, 02, 03.

Each view has its own approved source and its own renders. The approved source is the baseline for every render of the view.

In the app’s Help: How project Views work

One clear request

A request has four parts: the change, what it applies to, what to make it, and what to keep. A clear request gives Ply less to guess and Vel a clear thing to check.

• Change: one kind, Material, Lighting, Landscape, Furniture or Clean-up.
• Applies to: the element as you would name it on a drawing, such as Main façade.
• Make it: the result, such as Warm limestone.
• Keep exactly: what must not move, such as Camera, Massing, Openings, Balconies and Roofline. May vary: what can change freely, such as Sky.

In the app’s Help: Writing a clear request

References and regions

A reference is an image that guides the render: a stone sample, a lighting mood, a planting palette. It never replaces the approved source.

Each reference serves the whole project or one view, and in each request it has a role and an optional note. The receipt lists the references used.

You can also mark regions on the approved source: a change region, or a protected one. Regions are PROVISIONAL. Plyvel records them with the request and lists them in its receipt. The render engine does not use them yet, and Vel does not check them yet. A result can still change outside a change region or inside a protected one.

In the app’s Help: How references work

Draft, Verified and Portfolio

A Ply Draft is for fast exploration, and a Targeted Edit for one defined local change. Neither is reviewed by Vel, and both are marked NOT VEL VERIFIED.

A Verified Render and a Portfolio Render are reviewed by Vel. When you like a draft, Create Verified version makes a new render from the approved source, with the draft as its visual direction.

Every completed render gets a signed Render Receipt. Prices are beta prices; the request form shows the price before you create a render.

In the app’s Help: Draft vs Verified vs Portfolio

Ply makes the render

Ply is the render agent. It reads your request and the elements you protected, and makes the render.

The elements you keep go to Ply with the request and are written on the receipt. Protection is a request and a check, not a promise: compare the result yourself before you use it.

In the app’s Help: How Ply protects architecture

Vel reviews it

On Verified and Portfolio renders, Vel compares the result with the approved source and your request. It does not edit the image. It answers PASS, FIX or UNCERTAIN.

On FIX, Ply corrects the render once against the approved source, at no extra cost, and Vel reviews again. Vel says what each answer leads to, and what Vel cannot certify.

In the app’s Help: Vel’s review and its outcomes

Branches

Each render remembers where it came from. Continue from here starts the next request from a result; Create Verified version makes a reviewed render from the approved source; Return to the approved source starts again.

Whatever you start from, the approved source stays the baseline: Vel checks against it, and corrections are made against it.

In the app’s Help: How branches work

The Render Receipt

Every completed render gets a Render Receipt: the state, the request, what was protected and what could vary, the references, Vel’s review, the attempts and when it was issued.

It is signed with Plyvel’s key. In the app, Check the signature confirms the receipt is unchanged, and Check the file confirms the file is the one the receipt names.

This receipt records Plyvel’s visual checks. It is not structural, engineering, building-code, construction, or dimensional certification.

In the app’s Help: Reading the Render Receipt

In the beta today

The beta is invite-only, in your browser. Email sign-in, projects and views, uploads, render requests and signed receipts work.

Ply’s render engine and Vel’s review are still being finished. Until they land, a render in the beta returns your source image unchanged, and Vel is a stand-in reviewer that answers from a fixed script: its decisions there say nothing about the image. Credits there are test credits.

• Buying credits is not open yet: credits are added by Plyvel during the beta.
• Regions are PROVISIONAL: the request and the receipt record them, but the render engine does not use them yet and Vel does not check them yet.
• Team workspaces and invitations work, and invitations go out by email.
• The receipt can be saved as JSON; there is no PDF version yet.

Known limits lists the rest.

In the app’s Help: Known limits of this beta