Work ledger
Backlog, sprints and tasks, the single source of truth that Forge Studio renders.
Delivery · AEGIS Conductor
Requirements in. Proven software out
Conductor turns a requirement into a governed Plan, runs AEGIS agents against it and keeps the evidence for every change. It is the system of record for the work, and the only caller of models inside AEGIS.
- 01LawThe rules an agent works under, written down and versioned.
- 02GateA check that must pass before work moves on: tests, policy, a human approval.
- 03PlanThe scoped work an agent may do, and nothing outside it.
- 04ReceiptA signed record of what happened, anchored so it cannot be quietly changed.
- 05ClaimA statement about the work, bound to its evidence or marked unverified.
What Conductor owns
The work, the rules and the record.
Plans and agents
Each task becomes a scoped Plan. Agents act inside it, with durable execution that survives restarts.
Governance engine
Evaluates every Gate deterministically. A model can propose; only the engine lets work move on.
Evidence vault
Keeps the inputs, outputs and approvals behind each change, in the tenant’s region.
Receipts
Issues a signed receipt at each Gate and release, anchored so it cannot be quietly changed.
AEGIS Models only
Every model call goes to AEGIS Models through Dynamis. Nothing is sent to a third-party model.
Agents with identities
Every agent is accountable.
Agents hold a service identity scoped to the customer’s tenancy. They work in remote workspaces, change code only through Stele and change environments only through Helix pipelines.
Their commits are signed as agent commits, separate from human ones, and an agent’s pull request cannot merge without a senior engineer’s approval.
Talk to us about your deployment.
Tell us what you need to build and where it must run. A member of the team replies within two business days.