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

WorkflowsGoverned workflowParallel makers converge

Incident to safe recovery

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

  • BLUEPRINT: Roles, gates and limits are specified. No runtime runs this workflow yet. A governed workflow contract across the houses. The roles, gate and limits are specified; no runtime runs it yet.
Plan a team from this crew

The run, step by step

Incident to safe recovery: Sentinel, then Cipher, then Beacon, then Vera, then Recovery gate, then Ships with proofSwipe to follow the steps. Drawn to show the order of the steps; nothing is running.

Steps

Who does what, in order.

Starts when: A bounded incident signal and accountable operator are present.

  1. Make

    Sentinel, Operational Risk Analyst

    Works in parallel with the other makers.

  2. Check

    Cipher, Data Privacy Analyst

    Checks the makers while they work.

  3. Combine

    Beacon, Incident Response Coordinator

    Combines the lanes into one result.

  4. Check

    Vera, Decision Evidence Reviewer

    Verifies the result independently before it reaches you.

  5. Your yes

    Recovery gate

    As designed, nothing moves past this point until a person says yes. Silence never counts as approval.

  6. Publish

    Ships with proof

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

What it hands you, and what stops it

Exit proof

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

Kept with the run

Append a redacted incident receipt and prevention action; never expose private incident data publicly.

It stops on

  • Containment scope unknown.
  • Evidence integrity uncertain.
  • Recovery is destructive or irreversible.

If it fails

Failure receipt with last valid evidence, limit reached, and safe resumption condition. It never retries on its own.

The agents in this workflow