Guide · Control
Review the output and the evidence together.
Approvals should show the exact artifact and action being authorised. Logs should explain what entered the system, what ran and what came back.
Approval lifecycle
01
Prepared
The agent creates the final artifact and action payload, then records the target account, intended time and relevant dependencies.
02
Awaiting review
The Founder Inbox shows the media or document itself, platform-specific copy and the exact external action.
03
Approved or rejected
The decision is attached to a fixed version of the payload. A later revision requires a new approval.
04
Executed and reconciled
After the provider call, Ekvaar records the provider ID or receipt and reconciles it against the requested action.
What a useful log contains
Timestamp in organisation timezone
Actor and organisation
Task and workflow identifiers
Input summary
Provider and model route
Tool or node action
Artifact references
Error and retry detail
Approval state change
External provider receipt
How to investigate a failure
Start from the task timeline, identify the first transition to Blocked or Failed, then inspect that action’s request, response status and provider. Search logs using the task or run ID so retries remain grouped with the original request.
Do not approve around a missing dependency
If the media asset, connected identity or provider receipt is missing, fix the dependency and create a revision. Approval should not convert an incomplete payload into a publishable one.