Authorization & approval
Examine the proposal and bind the approval to the intended action. Keep requester and approver responsibilities separate.
Public showcase · Governed AI Actions
Human approval. Durable execution. UNKNOWN-aware reconciliation. Auditable external actions.
This public showcase contains documentation and demos. The commercial implementation remains private and separately licensed.
Primary business story
A small factory moves from quotation to shipment. AI assistance proposes; approvals and role boundaries determine the next action.
Deterministic synthetic data and scripted AI assistance. No live ERP/MES or real customer; no commercial Framework execution proof. Human approval is a DEMO HUMAN APPROVAL SIMULATION.

Four control concerns
Examine the proposal and bind the approval to the intended action. Keep requester and approver responsibilities separate.
Record an intent and execution attempt before an external call, so an interrupted operation leaves evidence.
A lost response can leave an action UNKNOWN. An uncertain write must not be blindly repeated.
Keep decisions and observations inspectable. Approval-task chain verification has a specific scope.
Conceptual concerns illustrated by the technical refund demo; the manufacturing simulation shows business behavior and governance boundaries, not commercial execution.
Read about governed actions →Response lost. Two different questions.
Command truth
We never received a confirmation for the command.
External reconciliation verdict
A fresh, usable observation agrees with the intended change.
Reconciliation does not turn the command into SUCCESS. These are separate axes, not two names for completion.
Understand the lost-response case →Secondary technical demo
The Framework-backed refund demo uses synthetic data and simulated human approval; it contacts no live business system. Re-running it requires the separately licensed private Framework. The manufacturing simulation runs independently.
The technical demo substitutes the transport while exercising the licensed Framework's execution behavior. That scope does not apply to the manufacturing public simulation.
Explore the technical scenario and its limits →A map of the questions a governed action raises, rather than private internal modules.
Explore the concepts →Public documentation and demos are distinct from the privately licensed commercial Framework.
Read the public / commercial boundary →