Edited and republished deliberately. A new revision changes later runs only.
- Identity
- wf_…
- Revision
- r03
- Lifetime
- Until replaced
Compose identity, age verification, attestation, and signing in the order your product needs. Publishing fixes the definition; every launch copies it into a new evidenced session.
A workflow contains intent: ordered primitives, parameters, route constraints, and launch mode. Every customer authors and publishes that path in the visual builder. It contains no signer, nonce, or mutable result; those belong to the session created from it.
Edited and republished deliberately. A new revision changes later runs only.
Copies the published revision, effective routes, and evidence boundary into one fresh case.
The entrance changes who may start the session and which run-specific inputs are permitted. It never changes the primitive contract or the evidence model.
Share one stable, unlisted workflow URL. Every explicit start creates a separate session.
An authorized workspace member creates each run, supplies its inputs, and shares the opaque session URL.
Your product launches the published workflow with its ID and optional case metadata, authenticated by its API key.
Technical and non-technical teams use the same workflow builder to choose primitives, order steps, configure parameters, and publish a revision. The API only launches that published definition; it cannot author or alter the path.
Canvas position is presentation. These fields are execution semantics, enter the definition hash, and are copied into every later session.
The exact published version
The semantic graph commitment
Every primitive in customer-selected order
Claims, threshold, terms, and document requirements
The eligible country, credential, and wallet set
Reusable link, one-time, or API-only
Choose the primitives, publish one fixed revision, then launch a fresh session whenever the next case begins.
Government-wallet proof, ready to repeat.
Start with Alentra