Platform

Low-risk changes run. Sensitive ones wait for a named person.

Dex, raising a card that asks for approval

Deixic classifies every change against the authority you grant. Policy is checked before a credential is resolved, and a named person approves sensitive changes, with a reason, in the app or Slack.

Request early accessHow approvals work

Approval before executionProduction change
  1. Requested
  2. Policy checked
  3. Decision
  4. Recorded

Terraform apply against production

coding-agent · Platform

Waiting on person
Production changesAllow this action against production/networking?
Agent
coding-agent
Target
production/networking
Action
terraform apply
Policy result
Human approval required

Evidence attached

  • Terraform plan
  • Rollback plan
Policy: Production changes
  • Four classes of action

    Observe runs. Change runs within the policy you grant. Sensitive waits for a named approver. Outside your authority is denied or sent to you as a decision.

  • Your rules, before the action

    Policy is checked before anything runs: allow it, deny it, or require approval.

  • Approval covers the exact request

    The approver gives a reason. An approval binds to the exact arguments, policy version, and requester, and any change means Dex asks again.

  • Approve where the work started

    In the app queue, or in the Slack thread. Each Slack approve button works once, for the named approver.

  • Guardrails in the terminal

    Signed organization policy for Deixic Code; publishing a policy with the kill switch set blocks the actions that policy gates.

  • A signed receipt for every action

    Each governed action leaves a signed receipt with the policy, approval, request, and result in a tamper-evident audit log.

From a proposed change to a receipt

How it works in detail

Shared by every surface.

Use it with Dex on every surface, alongside company context that existing agents read over MCP.