Built · control planeSchema 1.0
Concepts
Twelve terms that explain everything else in these docs.
- Protected account
- The address whose transactions PALISEC governs. Today it is the agent's own account; with enforcement it becomes a smart account.
- Smart accounts
- Agent
- A registered caller bound to one account, one chain and one policy. It can be paused or revoked without touching the policy.
- Keys
- Scoped key
- An API key for one agent, limited to named scopes such as operations:write or mcp. Shown once, stored only as a hash.
- Keys
- Policy
- One JSON document per account: limits, cooldowns, allowed contracts and methods, deny rules and the approval threshold.
- Policy schema
- Policy version
- An immutable, hash-bound copy of a policy. Every decision records the version it used, so later edits never change history.
- Policy schema
- Operation
- One proposed transaction and its outcome. The request ID makes it idempotent: sending it again returns the same answer.
- REST API
- Decision
- ALLOW, DENY or REQUIRES_HUMAN_SIGNATURE, with a stable reason code and the result of every check.
- Errors
- Reservation
- The budget an allowed or pending operation holds. Taken atomically, so two requests at once can never overspend.
- Architecture
- Approval
- An EIP-712 signature by a member's own wallet over the exact operation and policy version. It expires.
- Smart accounts
- Authorization
- Proof that PALISEC allowed one exact payload on one chain under one policy version, valid for a short window.
- Smart accounts
- Audit event
- An append-only record of every decision and change, written in the same statement as the change itself.
- Security model
- Emergency stop
- One switch that denies every new operation in the organization until a member lifts it.
- Errors
An operation's life
Every call to POST /v1/operations becomes one row in the ledger. That row is the decision, the budget reservation and the approval record at once, so they can never disagree.
requestauthorized
denied
pending_approval
approvedrejectedcancelledexpired
Units
| Quantity | Unit | Example |
|---|---|---|
| Native value | wei, as a decimal string | "40000000000000000" (0.04 ETH) |
| Budgets and thresholds | USD micros, as a decimal string | "150000000" ($150) |
| Cooldowns and windows | whole seconds | 60 |
| Deadlines | Unix seconds | 1795132800 |
Integers only. A float in a money field is rejected, so rounding can never move a budget.
Three rules that never bend
- Unknown means deny.A missing price, fee, policy or state is never treated as zero.
- Same request, same answer.A repeated request ID returns the original decision; it is never evaluated twice.
- No model decides.The PALISEC Agent explains decisions. Only the deterministic engines make them.