OrbitForge Ecosystem

Design full agent lifecycles with drag, drop, sync, export, and one-click launch.

OrbitForge Ecosystem Studio is designed for the bigger problem that agent canvases usually skip: not only running an agent, but defining the full lifecycle around intake, approval, validation, handoff, release, and publication.

Low-code by default

Drag lifecycle components into a canvas, configure them inline, and launch them into the OrbitForge workbench without rebuilding the flow by hand.

Synced ecosystem

Signed-in builders can sync blueprints across devices, while JSON export keeps the contract forkable and reviewable in the open.

Lifecycle first

Intake, context, debate, approval, validation, release, and publish are all first-class stages.

Blueprint Controls

Build once, sync it, export it, or launch it. OrbitForge treats lifecycle design as a first-class asset, not a side note.

Local mode

Sign in to sync ecosystem flows across devices.

Active blueprintTitleSummaryGoalVisibility

Design the lifecycle visually, then export it as an open OrbitForge contract or send it straight into the workbench.

Starter kits

Component Palette

Drag components into the lifecycle canvas. OrbitForge turns the flow into a mission board, workbench seed, CLI recipe, and open JSON contract.

Mission Intake

intake

Lock the objective, owner, deadline, and non-goals before any agent starts improvising.

Context Pack

context

Bundle repos, docs, incidents, specs, and environments into a reusable mission capsule.

Parallel Lanes

parallelize

Run architect, implementer, critic, or custom lanes in parallel with an explicit workflow frame.

Approval Gate

approval

Require a human decision before the flow advances into risky changes or external publication.

Validation Matrix

validation

Encode proofs, tests, and evidence so “looks done” never passes for “is done.”

Release Gate

release

Turn the run into a release contract with rollback, blast radius, and communication duties.

Publish Pack

publish

Produce the assets required for public shipping: changelog, status note, and ecosystem handoff.

Lifecycle Canvas

Untitled ecosystem flow

Drop components here

Mission Intake

intake component

LabelNotes

OwnerDeadlineNon-goals

Step 1: Lock the objective, owner, deadline, and non-goals before any agent starts improvising.

Context Pack

context component

LabelNotes

SourcesConstraints

Step 2: Bundle repos, docs, incidents, specs, and environments into a reusable mission capsule.

Parallel Lanes

parallelize component

LabelNotes

WorkflowLanes

Step 3: Run architect, implementer, critic, or custom lanes in parallel with an explicit workflow frame.

Compiled OrbitForge Contract

Preview the lifecycle before you run or publish it.

# Untitled ecosystem flow

Compose the lifecycle, approvals, and validation rules before agents run.

Goal: Ship a trustworthy result with explicit handoffs, proof, and release control.
Visibility: private
Workflow: release

## Lifecycle
1. Mission Intake (intake)
   Component: Mission Intake
   Why it exists: Lock the objective, owner, deadline, and non-goals before any agent starts improvising.
2. Context Pack (context)
   Component: Context Pack
   Why it exists: Bundle repos, docs, incidents, specs, and environments into a reusable mission capsule.
3. Parallel Lanes (parallelize)
   Component: Parallel Lanes
   Why it exists: Run architect, implementer, critic, or custom lanes in parallel with an explicit workflow frame.
   Config:
   - workflow: general

## OrbitForge Use
- Export this blueprint as JSON for the public OrbitForge repo.
- Run it in the CLI with `--blueprint-file` or send it into the hosted workbench.

Run Everywhere

One lifecycle, multiple surfaces.

Hosted workbench

Launch this blueprint straight into the OrbitForge workbench with one click.

Public CLI

Use the generated CLI recipe to run the same lifecycle contract in the open-source repo.

orbitforge --parallel --workflow release --provider ollama --model deepseek-coder:33b --blueprint-file ./ecosystem-d0552afd.json

Open Ecosystem Contract

Publishable, reviewable, and forkable by design.

JSON blueprint

Every flow is plain JSON, so contributors can review, fork, version, and extend lifecycle logic in the open.

Lifecycle-first, not node-first

OrbitForge solves the larger problem n8n-style agent nodes leave open: ownership, context, dissent, approval, proof, and release.

Community-ready flows

Mark a blueprint as community-ready, then publish it into the open repo, docs, or future marketplace without rewriting the logic.