Starlight Intelligence
Explore

WorkflowsGoverned workflowRoute, then converge

Marketplace adoption

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

  • 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

Marketplace adoption: Envoy, then Lattice, then Cassian, then Aegis, then Install 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 user need, host environment, and authority boundary are known.

  1. Route

    Artifact Delivery Planner

    Routes the work and splits it into lanes.

    An expansion profile: a blueprint draft with no tools connected and no external effects.

  2. Make

    Lattice, Agent Interoperability Architect

    Works in parallel with the other makers.

  3. Check

    Cassian, Resource Planning Analyst

    Checks the makers while they work.

  4. Check

    Aegis, Agent Trust and Governance Lead

    Verifies the result independently before it reaches you.

  5. Your yes

    Install gate

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

  6. Publish

    Ships with proof

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

What it hands you, and what stops it

Exit proof

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

Kept with the run

Record the installed version and permission receipt; no silent upgrades.

It stops on

  • Compatibility unknown.
  • Permissions exceed declared need.
  • Package provenance or cost unclear.

If it fails

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