CAPA CERO · INVESTOR CONTROL PLANE
Capa Cero is building the authority layer between AI agents and state-changing actions. Capa Cero can evaluate the authority context for a state-changing operation — identity, permissions, policy, evidence and approvals — produce a decision and preserve an attributable record.
Capability is not authority.
WHY NOW · STATE-CHANGING AI
AI systems are moving from generating answers to changing state. Every state-changing action creates an authority question: who is acting, on whose behalf, within which scope, under which policy, with what evidence and approval?
Should this system be allowed to perform this action, under what authority, and how can that decision be reconstructed?
FOUNDERS · COMPLEMENTARY PATHS
Two complementary roles focused on making runtime authority understandable and usable.
Co-Founder & CEO · Product, Systems & Operations
15 years inside banking operations shaped a first-hand view of authorization, accountability and operational control. Agustín leads Capa Cero's product, system design and operations, using an AI-native development process to turn that operating insight into software.
Co-Founder · Brand & Communications
Three years inside the same financial institution add direct operational context to her work leading Capa Cero's brand, visual identity and communications. Her focus is turning complex infrastructure into a clear product narrative for teams and markets.
INITIAL WEDGE
Start with one bounded operation in one authorized environment. Capa Cero receives the action request, assembles its authority context, evaluates the decision and preserves the attributable result.
REFERENCE ACTION
AI agent requests an allowed-field update on a CRM record.
PRODUCT · RUNTIME AUTHORITY
Capa Cero is building an authority layer for the path between an AI agent and a state-changing operation. The product can assemble the relevant authority context, produce a decision and preserve an attributable record. Universal external interposition remains to be proven.
Receives the proposed state-changing operation.
Connects principal, agent, resource, action and scope.
Evaluates rules and conditions for the operation.
Attaches the evidence required by the decision context.
Routes actions that require human authority.
ALLOW · REQUIRE APPROVAL · DENY
The bounded operation continues according to the decision.
Preserves the context behind the decision and result.
The interface used to inspect, configure and reconstruct authority decisions.
Principal → Delegation → Agent → Task → Resource → Action → Result
Permissions describe access. Authority describes why this actor can perform this exact action, on this resource, under this context, at this moment.
EXPANSION PATH
Begin with one bounded action, then extend the same authority context across workflows, teams, organizations and connected systems.
NEXT MILESTONE · EXTERNAL WORKFLOW
Connect one authorized external environment, govern one bounded state-changing action and measure integration time, review time, evidence completeness and repeated use.
Authorized environment + bounded scope.
One state-changing operation through the authority context.
Integration time, review time, evidence completeness and repeated use.
Action → workflow → team → organization.
CURRENT FOUNDATION
INTERNAL OPERATING ENVIRONMENT
8 software products and 42 registered capabilities/surfaces inside our own portfolio were used to expose and model the authority problem.
The portfolio became Capa Cero's first operating environment: a way to map dependencies, authority requirements, evidence and decision context across multiple software surfaces.
