Modules / Validation
Ask for the decision once, and keep every version of the answer.
Send any asset to a colleague: a visual, a text, a video, a file. They get a card on their board and a mail. They validate or send it back with a comment. You answer with a new version on the same thread. Nothing is ever deleted.
Demo workspace. Invented brand and figures.
Send, card, decide, again.
Send
Any asset, to any colleague
Something made in the product, a file from your desk, a text, or an address. A title, a note, one validator.
Card
A task on their board
Created in To Do, assigned to the validator, named after the asset and its version. Mail goes out in their language.
Decide
Validate, or send back
A comment is required to send back. The status follows the current version.
Again
A new version, same thread
A rejection is answered with version two on the same thread. The card reopens. Nothing from version one is lost.
Two queues on one page: what waits for you, and what you asked for. A third tab shows everything in the organization. Each row carries its type, its version, its status, who asked, and who decides.
The current version, the earlier ones, the thread, the decision.
The asset page renders the current version inline when it can: a text, an image, a video. Earlier versions sit under it. The thread runs down the side. The decision box shows the actions for whoever is looking: validate or send back for the validator, submit a new version for the requester.
The six kinds an asset can be.
Four things that never disappear.
Every version records who submitted it, the note, who decided, when, and the decision comment. The history is the point.
The thread holds comments, submissions, validations, rejections, and reassignments, in order.
A single colleague per asset. Reassign, and the card moves with it.
Request, decision, and comment mails, in the interface language of whoever acted, dressed in the brand when the asset carries one. Mail and the board card are best effort: they can never turn a submission into an error.
The same data, one door over.
Nothing here is an integration. These run on the same account, the same brand, the same ledger, so a finding on one page becomes work on the next.
Not built yet, said first
- One validator per asset. No approval chains and no parallel sign-off.
- No due dates or escalation on a validation.
- Validators are colleagues in the same organization. No guest validators yet.
The catalog lists every agent as built, partial, or not built. Checked against the product on September 3, 2026.
Usage is metered in tokens from a prepaid wallet, with no seat fee. The rates are on thepricing page.
The first decision takes a minute. The trail lasts as long as the asset.
Validation is on for every organization. Open an asset, name a colleague, and the card is on their board before you have closed the dialog.
No subscription. No seat fee. No card needed to request an account.