Capability Factory by Joel Jeon
Capability resolution becomes part of the work, not a separate integration ticket.
Capability Factory demonstrates a new capability-resolution loop. While pursuing an ordinary goal, an agent can recognize a missing ability, reuse or acquire the smallest permission-bounded capability, verify the real external outcome independently, and resume the work it was originally asked to complete.
The control loop is the product. Each part exists to preserve authority, evidence and the original goal.
Capability Factory sits behind an existing agent through an embedded software development kit or customer-local sidecar. The customer describes the result they need. They should not have to diagnose which integration is missing first.
The system identifies the required action, target, inputs and observable completion criteria. The current system does this inside a trusted customer-local scope, rather than pretending to understand every possible business environment.
A missing technical route is different from a missing credential, permission, approval, target detail or human judgement. Capability Factory may acquire the route. It must request missing authority precisely instead of manufacturing it.
The order is retained capability, trusted existing source, bounded composition, smallest built manifest, isolated residual route, then bounded delegation. Existing tools should be reused when they fit. Rebuilding everything would make the system slower and less trustworthy.
A capability is more than generated code. Its bundle binds trusted runtime software, a constrained manifest, target, permissions, approvals, pre-use verification, external-outcome verification, recovery rules, provenance, scope and version. Customer credentials and payloads are not retained inside it.
A candidate receives a bounded no-action or disposable-state probe. Unsafe, malformed or weakly observable routes fail closed before they are allowed to affect business state.
Trusted runtime code, not the language model, enforces which target, action, risk, approval and secret boundaries apply. A technically possible action still cannot exceed the authority the customer granted.
An executor saying success is not proof. Separate read-only logic checks whether the intended business state actually exists. When several capabilities contribute to one goal, an additional aggregate check must prove the parent outcome.
A write may commit even when its response is lost. Before retrying, the system reads the external state. Completed work is not repeated. Partial, incorrect and unknown results stay explicit, and risky capabilities can be quarantined.
The climax is not capability creation. It is completing the original goal. A proven capability is retained with its scope and evidence so a fresh process can reuse it later.
A frozen local development gate exercised all eight enabled routes, and the wider repository contains hundreds of automated local checks. The evidence is fictional and disposable, not a customer deployment or production-reliability result.
Five development days separated the initial thesis from the first end-to-end constrained local loop. The constrained-HTTP application milestone followed on calendar day six.
A deliberately lost response left a write uncertain. The local system checked real state before retry, discovered the committed result, avoided a duplicate and continued.
HTTP has the pilot-MVP label. Browser, file/EDI, signed message, pinned document, reviewed database, WebAssembly and signed delegation routes remain bounded experimental local systems.
Existing platforms already solve important pieces, and Capability Factory should reuse them when they fit. Its different thesis is the complete ordinary-goal loop around those pieces.
Scoped agent access, authentication and integration functions.
Official source ↗Pipedream ConnectManaged authentication and a large catalogue of agent tools.
Official source ↗ComposioTool discovery, execution, authentication and session context.
Official source ↗RizaIsolated runtimes for code execution and tool creation.
Official source ↗Capability Factory joins diagnosis, reuse or acquisition, exact authority, independent outcome verification, safe recovery, retention and original-goal resumption. In current research, I have not found public evidence of another company demonstrating that same specific end-to-end loop.
This is strong local evidence for a new capability-resolution architecture, not yet evidence of customer compatibility, production reliability or effective universality.
Visit Capability Factory ↗