Approvals

Activation status: Source-ready for exact recorded browser actions, with compatible Worker code deployed. Required production database activation and authenticated approval canaries remain pending. Do not call this mutation until Praxa confirms activation for your tenant.

​

Read the pending action

{
  "status": "awaiting_approval",
  "pendingApproval": {
    "approvalId": "approval:browser:1",
    "action_digest": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
    "summary": "Publish the reviewed release\nTarget: console.example.com"
  }
}

​

Approve or deny

POST /v1/runs/:id/approve
Authorization: Bearer praxa_sk_<64 lowercase hex characters>
Content-Type: application/json

{
  "action_digest": "<64 lowercase hex characters>",
  "decision": "approve"
}

​

What Praxa checks

1. The run is waiting for a pending approval with an approval reference and a 64-character action digest.
2. The executor is a browser action using browse_session_act.
3. The immutable executor request carries the same action digest.
4. The recorded instruction or steps, URL, and target host pass the strict browser-action schema and fit the public presentation unchanged.
5. The submitted digest still matches that exact pending presentation.