Skip to content
DeAlgoOpen workspace

resources / DeAlgo

A control layer between intent and action.

DeAlgo's architecture separates a request, the authority to act, and evidence of what happened.

Request

An authenticated, individually scoped agent sends exact financial terms. A stable request key identifies retries. A requested allowance is a proposal to an owner, not authority the agent grants itself.

Authority

The owner defines the policy boundary. DeAlgo checks identity, workspace, action, currency, counterparties, amount, budget, expiry, and pause state. A human approval applies to a particular stored request.

Execution boundary

The general commerce API currently stops at proposal approval. The separate Stripe test refund engine has an execution and reconciliation path. Connecting the two safely requires explicit authorization semantics; an APPROVED label must not be interpreted as a generic payment instruction.

Evidence

Records tie decisions to the request and actor. Provider observations are distinguished from agent assertions. Broader replay, independently verifiable receipts, and provider portability are development directions, not blanket guarantees of the customer API.

Current release: proposal controls and Stripe test refunds. General payment execution is disabled.