Starlight Intelligence
Explore

Find your way through Starlight

Follow a completed mission, give your next project a brief, or build on the foundation.

Follow the workMissionsMake somethingMemory StudioMake it your ownFor buildersBuild togetherCommunity
Build once. Bring it with you.Capability FoundryFollow the thinkingResearchSee what is releasedOpen sourceQuestions and their evidenceStarlight AtlasJudgment that stays yoursTrust playbook2 to 144 perspectivesPlan a teamThe project and founderAbout StarlightYour first useful workflowStart with your agentTurn an idea into a crewMission composerMeet the crew and every seatAgentsCheck the prerequisitesInstall routerInspect the packagesDepartmentsPractice firstLearnGive an agent a jobAgent KitsSee what each agent contributedFollow a missionPick a working setTeamsSee the visual worldImagesFit to your workConfigureShared planePartnershipsA job in motionWorkflowsWho talks to whomAgent graphKeep the keyFoundationOne buildWorkshopsFour movesPathIdeas and evidenceTechnical notesContractsDevelopers
Concept artwork of two agents bringing a glowing model to a gate, where a person stands ready to decide what passes

Workflows

Watch the work move, step by step.

Every workflow shows its shape before anything starts: who plans, who makes, who checks, and the gate where it waits for you. Replay the one with a saved run, read the rest, then borrow a crew for your own plan.

Explore the recorded mission Browse the patterns
  • RECORDED: A saved run of this pattern replays on the homepage and in the mission studio. It is not a live run. One pattern has a saved run you can replay and inspect.
  • BLUEPRINT: Roles, gates and limits are specified. No runtime runs this workflow yet. The other ten are designs. None runs yet.
  • IN DEVELOPMENT: Implementation is in progress; customer availability is not established Durable runs on Cloudflare Workflows.
Concept artwork

The spine of every run RECORDED: One saved run of this pattern, a diagnostics workflow for a public Node.js repository, replays on the homepage and opens in the mission studio. It is a recording, not a live run.

Plan, fan out, wait for you, publish.

Here is the delivery pattern, the one with a saved run: Atlas investigates a public repository, Orion designs the checks, Rivet builds the files and Vera evaluates them before the gate. In the recording, that gate is staged; the original run had none.

Build something useful: Astra, then Atlas, then Orion, then Rivet, then Vera, then Hand-off gate, then Files handed offSwipe to follow the steps. Drawn to show the order of the steps; nothing is running.
  1. 01

    Plan

    Astra reads the goal, names the decision and splits the work into steps a specialist can own.

  2. 02

    Fan out

    Specialists take their steps, in parallel where they can, and record every tool call and source.

  3. 03

    Wait for your yes

    The run is designed to stop at the gate with the exact files in front of you. Silence never counts as approval.

  4. 04

    Publish

    Only what you approved leaves the run, with its hashes and receipts attached.

Walk through the delivery pattern step by step

Durable runs IN DEVELOPMENT: Implementation is in progress; customer availability is not established

Where a run will live while it waits for you

Durable runs on Cloudflare Workflows are being built so a run can plan, fan out, wait at the gate for up to seven days, then publish, and pick up from its last finished step after a restart. Until it ships, nothing on these pages runs on its own.

Crew patterns

Three ways to put the crew to work.

Shape a brief, investigate a question or build something useful. Each pattern uses the crew roles, and each one says plainly how far along it is.

Shape a project: 4 steps

Plan, draft, approveBLUEPRINT: A design for agent-drafted briefs; it does not run yet.

Shape a project

Turn the notes, links and half-formed plans you already have into one brief a crew can act on.

2 agent steps · 1 gate for your yes

Investigate a question: 6 steps

Plan, fan out, reviewBLUEPRINT: A design. Live retrieval is a planned tool, so this pattern does not run yet.

Investigate a question

Ask a question that deserves a proper answer and get findings where every claim points to a source.

4 agent steps · 1 gate for your yes

Build something useful: 7 steps

Plan, relay, evaluateRECORDED: One saved run of this pattern, a diagnostics workflow for a public Node.js repository, replays on the homepage and opens in the mission studio. It is a recording, not a live run.

Build something useful

Hand the crew a public codebase and get back working files, checked against what you asked for.

5 agent steps · 1 gate for your yes · one saved run

Governed workflows

Eight workflows across the houses.

Each contract names its makers, an independent verifier, hard limits on turns and spend, and the human gate it may not pass on its own. They are designs today, written down so you can read them before anything runs.

Intent to bounded mission: 6 steps

Route, then convergeBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Intent to bounded mission

A bounded mission brief with owner, constraints, routes, gates, and evidence plan.

4 agent steps · 1 gate for your yes

Research to evidence: 7 steps

Fan out, then convergeBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Research to evidence

A claim ledger, source set, synthesis, dissent note, and confidence statement.

5 agent steps · 1 gate for your yes

Build to verified artifact: 7 steps

Fan out, then convergeBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Build to verified artifact

A tested artifact, independent verification receipt, known-risk list, and reversible release plan.

5 agent steps · 1 gate for your yes

Story to responsible release: 7 steps

Parallel makers convergeBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Story to responsible release

A rights-cleared release packet with exact copy, media, crops, accessibility text, and approval receipt.

5 agent steps · 1 gate for your yes

Incident to safe recovery: 6 steps

Parallel makers convergeBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Incident to safe recovery

An incident timeline, containment state, recovery proposal, rollback path, and operator decision.

4 agent steps · 1 gate for your yes

Learning to demonstrated mastery: 6 steps

Practice loopBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Learning to demonstrated mastery

A demonstrated capability, learner reflection, evaluator evidence, and next-practice plan.

4 agent steps · 1 gate for your yes

Marketplace adoption: 6 steps

Route, then convergeBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Marketplace adoption

A compatible pack plan with permissions, provenance, cost, rollback, and explicit install approval.

4 agent steps · 1 gate for your yes

Memory and continuity: 6 steps

Relay chainBLUEPRINT: A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.

Memory and continuity

A source-linked memory atom with scope, confidence, contradiction state, and retention decision.

4 agent steps · 1 gate for your yes