The agent’s machine
Runs the confined agent and the controlled execution path. It checks policy and approval before minting an effect.
Explore by need
Give the agent a path.
For builders & operators
Give the agent a path.
Keep a gate in it.
Cippax places a controlled action path beneath an agent. The agent proposes a structured effect; separate checks decide whether that effect may be minted and executed.
Prototype architecture · integrations are scoped
SIMPLIFIED ACTION PATHCIPPAX / OS
01Agent proposalintent, not authority
02Policy + human approvalthe controlled door
03Committed effectonce, with an audit record
Every supported effect needs a closed path
The pieces around an action
Several hosts.
One boundary.
Authority is split on purpose. The hosted edge can route a request, but it cannot approve one.
The human’s approval
Holds the enrolled passkey. The person signs a specific request; the edge moves the bytes.
Judgment and witness
A separate model host can tighten a decision. An off-box witness checks the record and can withhold new leases.
Transport, not authority
The remote approval service routes sealed requests and decisions. The cell still verifies the signature before acting.
Integration shape
Make one path
complete.
Prototype work includes outbound HTTP, controlled workspace writes, and peer calls. A deployment supports a workflow only after every route to its effect is mapped, closed, or mediated and tested.
01 Define the exact action and what will be signed.
02 Map every socket, file, credential, device, and service that could cause the effect.
03 Route the permitted effect through the controlled door.
04 Test approval, denial, replay, audit failure, and witness failure.
Where this stands: This is a working prototype, not a drop-in SDK for arbitrary tools. Installation, pairing, workflow coverage, and customer-facing verification remain active work.
Build a bounded pilot