Operating Specifications
Portable, versioned definitions of how AI-enabled work should operate across signals, context, decisions, governance, execution, evidence, and outcomes.
Developers
Build the capabilities that make governed Operating Paths deployable.
Aegora gives developers a model for building capabilities, operating assets, and runtime integrations that can be governed, tested, versioned, simulated, reused, and deployed across enterprise environments.
The goal is not to replace full software-development environments. The goal is to let developers use Codex, Claude, IDE agents, APIs, and Helix against one Aegora operating layer while preserving a durable contract for how governed work should run.
Developer Surfaces
Use the AI environment you already work in. Add Aegora.
Aegora treats Codex and Claude as developer and FDE surfaces over the same governed artifacts and runtime boundaries that Helix uses. MCP, APIs, and reusable skills make those surfaces interchangeable without moving Aegora business logic into each client.
Developer Motion
What developers build in Aegora.
The platform focuses on governed operating assets rather than generic coding surfaces or one-off integrations.
Codex and Claude as first-class Aegora surfaces
MCP, APIs, and skills over one canonical agent interface
Capability contracts for abstract enterprise actions
Operating Specification authoring and validation
Simulation mocks and local proof
Capability packaging and testability
Portable runtime deployment
Governed execution contracts
Exchange-ready reusable assets
API and SDK integration points
Core Artifacts
Three reusable artifacts define the builder experience.
These artifacts connect design, simulation, build, deployment, runtime, and Exchange distribution.
Capability Packages
Reusable governed execution units with manifests, schemas, security expectations, runtime requirements, tests, and marketplace metadata.
Operating Paths
Governed runtime assets that bind enterprise context, policy, approvals, capabilities, humans, and systems into one accountable execution model.
Builder Principles
Treat integrations, models, and execution code as governed participants.
Connectors, APIs, LLMs, scripts, human tasks, and enterprise systems should participate through explicit contracts, permissions, evidence rules, and policy controls rather than bypassing the operating model.
Developer Kit
Download the Codex developer kit for the current install-and-build path.
The developer kit packages the current plugin scaffold, install scripts, MCP integration docs, Operating Path example material, and TypeScript action example package into one download surface.
Developer Next Step
Go from governed design into simulation-ready and runtime-ready execution assets.
Use Helix, Codex, Claude, or direct APIs to define the path, package execution units through Developer Studio, and operate them in Runtime under policy and evidence controls.