Starlight Intelligence
Explore

WorkflowsGoverned workflowFan out, then converge

Build to verified artifact

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

  • 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.

The run, step by step

Build to verified artifact: Tess, then Rivet, then Prism, then Ignis, then Vera, then Production 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 scoped specification, verified repository lane, and acceptance test exist.

  1. Route

    Tess, Software Systems Architect

    Routes the work and splits it into lanes.

  2. Make

    Rivet, Software Build Engineer

    Works in parallel with the other makers.

  3. Check

    Prism, Product Quality Reviewer

    Checks the makers while they work.

  4. Combine

    Ignis, Product Development Lead

    Combines the lanes into one result.

  5. Check

    Vera, Decision Evidence Reviewer

    Verifies the result independently before it reaches you.

  6. Your yes

    Production gate

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

  7. Publish

    Ships with proof

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

What it hands you, and what stops it

Exit proof

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

Kept with the run

Record code, test, build, and review receipts before promotion.

It stops on

  • Failing initializer.
  • Same actor is sole verifier.
  • Tests or provenance missing.
  • Production authorization absent.

If it fails

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