Helix workflow engine

Helix runsany process.

Cendra understands the work. Helix routes agents, tools, approvals, and evidence through one governed workflow engine.

IntakeSOPs and ticketsModelprocess graphRouteagents and toolsExecutepolicy gatesProverun evidence

SOURCESWorkspace inputsIssues, repositories, and documentation enter the knowledge ingest path.ISSUE · REPO · DOCS

CORTEXRAG contextRetrieves ranked atoms and graph context with source provenance.VECTOR · GRAPH · CITE

CENDRAOperation modelReads the request, finds the real process, and frames what must be governed.INTENT · CONTEXT · GATE

HELIXWorkflow engineTurns the process model into a routed workflow for agents, tools, and people.PROCESS GRAPH · ROUTE · GATE

AGENT RUNTIMEGuarded executionRuns role instructions with policy, budget, tool, and loop controls.TOOLS · POLICY · CAP

RUN EVIDENCERun evidenceKeeps the run stream, test results, findings, approvals, and final outcome.EVENTS · TESTS · GATES

COCKPITFleet + run stateDisplays fleet KPIs, agent performance, live status, and run history.KPI · STATUS · HISTORY

sync → atomizeranked atoms + provenanceapproved process graphroute each work stepevents + tool resultsstatus + run recordagent events → reviewable atoms

CENDRA PROCESS MODEL

Cendra turns scattered work into a process model.

Not another canvas to maintain. Cortex preserves cited context; Cendra uses it to understand how work actually happens and what Helix must route.

CORTEX + CENDRAGround, understand, and shape

01DecomposeSplit incoming material into focused knowledge atoms Cendra can reason over.

02ProtectDeduplicate content and redact sensitive data before any plan.

03ResolveIdentify entities that represent the same system across tools.

04GroundAttach provenance and confidence before retrieval and routing.

AVAILABLE TO CENDRA + HELIX

Knowledge atomsSmall, focused facts with provenance and confidence.

Resolved entitiesCode, tickets, and runtime objects linked to the same system.

Grounded retrievalGraph and semantic context available when a run needs it.

HELIX WORKFLOW ENGINE

Helix runs any process as a governed workflow.

Once Cendra shapes the operation, Helix routes role agents, MCP tools, browser work, and human gates with scoped context and approved capabilities.

SPECIALIZED, NOT ISOLATED

One process. Many specialists.

Planners, coders, testers, reviewers, deployers, and analysts join only when the Cendra-shaped process needs them. Evidence carries forward throughout the run.

Shared run contextplan · policy · evidence

Plannerorders the work

Codercreates the change

Testerchecks behavior

Reviewerfinds risk

Deployermoves the release

Analystreads the outcome

in the app today

The app your team opens every day.

Five product surfaces drawn from the current app — where teams ground requests, approve plans, follow runs, inspect the fleet, and review changes.

DURABLE RUN RECORD

The operations record grows with the work.

Each checkpoint adds operation intent, routed steps, artifacts, tool events, tests, decisions, approvals, and outcome evidence.

RUN RECORDmodel -> route -> verify -> outcome

01Cendra

Model

Turn the messy operation into a scoped process model with approvals and proof requirements.

+ goal + constraints+ plan + gates

02Helix

Route

Run the workflow by routing role agents, MCP tools, and human gates with scoped capabilities.

+ artifacts+ tool events

03Review

Verify

Add tests, findings, policy decisions, and human approvals.

+ test evidence+ verdicts + approvals

04Cockpit

Close the loop

Expose the outcome and return its learning signal to future routing.

+ outcome+ learning signal

ACCUMULATED EVIDENCENothing is presented as proof until the run adds the evidence.

Explore Helix execution

GOVERNED EXECUTION

Controls sit inside the run.

Cendra sets boundaries before the run. Helix enforces access, approvals, isolation, and audit where the work happens.

Before execution

Inspect the plan first

Review cost, reversibility, confidence, and proposed steps before dispatch.

At every tool call

Scope capabilities

An agent receives the permitted tenant and tool capabilities—not blanket access.

At risk boundaries

Keep people in the path

Approval gates can stop plans, merges, deployments, and operations actions.

During execution

Isolate the workspace

Code and commands execute inside an isolated DevBox environment.

Across the run

Preserve the record

Transitions, decisions, tool events, artifacts, and approvals remain auditable.

YOUR STACK, CONNECTED

Connect without
replacing your stack.

Use managed connectors, MCP servers, A2A agents, and the outbound tunnel for systems inside your boundary.

Connects to everything you already use

155-connector catalog · MCP protocol · growing weekly

FAQ

Answers before the pilot call

Short context on how Cendriix runs agents with shared operating memory.

START WITH ONE REAL OPERATION

See your systems, agents,
controls, and evidence connected.

Bring one real operation. Cendra maps the steps, Helix routes the work, and Cockpit keeps the proof inside your boundaries.

Book a pilot Read the docs

accepting design partners