Skip to content

Add KineticOS continuation-fleet example (agent fleet built on SuperPlane)#5091

Open
sahielbose wants to merge 1 commit into
superplanehq:mainfrom
sahielbose:add-kineticos-continuation-fleet-example
Open

Add KineticOS continuation-fleet example (agent fleet built on SuperPlane)#5091
sahielbose wants to merge 1 commit into
superplanehq:mainfrom
sahielbose:add-kineticos-continuation-fleet-example

Conversation

@sahielbose
Copy link
Copy Markdown

What this is

A self-contained example under examples/kineticos-continuation-fleet/
KineticOS, a project built on SuperPlane: a CAD image of a broken
industrial machine comes in → a fleet of agents identifies the fault, generates
a new 3D-printable CAD file, validates it, and resumes production, with
SuperPlane gating every phase.

Maintainers: this is a downstream app example, not a platform change. It
lives entirely under examples/, adds nothing to your build/CI, and touches no
existing files. If you'd rather take only the workflow template, the one file
worth upstreaming is the Canvas — it drops into templates/canvases/ with
metadata.isTemplate: true per docs/contributing/templates.md. I'm glad to
reshape this PR down to just that. See SUBMISSION.md in the folder.

Highlights — the Canvas

infra/superplane/kineticos-fleet.canvas.yaml (34 nodes / 40 edges) exercises a
lot of SuperPlane in one real workflow:

  • Parallel fan-out + merge — six perception agents run concurrently from
    the ingest trigger; a merge barrier fuses them.
  • Gate pattern (×4) — each phase ends in http (evaluate-gate) → if
    (decision == "proceed") → approval (human gate); rejections route to halt.
  • Conditional branchif chooses an off-the-shelf substitute vs. a
    generated continuation part.
  • http executors call the app's per-agent endpoints; annotations
    document each section on-canvas.

A .local.canvas.yaml variant points executors at host.docker.internal:3000
for a containerized SuperPlane calling the app on the host.

The rest of the folder

The downstream app it drives — Next.js HTTP executors (src/app/api/agents/**,
src/lib/contract.ts), the node→agent map / loader / offline rehearsal
(infra/superplane/{README,apply.sh,smoke.sh}), and project docs. The
TypeScript is illustrative (not platform code; not built by your CI).

Full project: https://github.com/sahielbose/KineticOS-Superplane-Hackathon

🤖 Generated with Claude Code

…lane)

Self-contained under examples/kineticos-continuation-fleet/. Primary artifact is
a 34-node Canvas (parallel perception fan-out + merge, the http→if→approval gate
pattern x4, a conditional design branch, on-canvas annotations) exercising a
real multi-agent workflow. Also includes the downstream Next.js HTTP executors
the Canvas calls (illustrative — not platform code, not built by CI) and docs.

Adds nothing to the platform tree or CI. See SUBMISSION.md for context; happy to
reshape to a single templates/canvases/ entry per docs/contributing/templates.md.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@superplanehq-integration
Copy link
Copy Markdown

👋 Commands for maintainers:

  • /sp start - Start an ephemeral machine (takes ~30s)
  • /sp stop - Stop a running machine (auto-executed on pr close)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant