Starlight Intelligence
Explore
Concept artwork of Product Forge agents working through a shared build at a long workbench

HousesFOR

Product Forge

Takes a real customer problem from design to tested build.

BLUEPRINT: A designed house of five agents. None of them runs in production. Rivet fills a crew role you can explore in preview; none runs in production.

Concept artwork

Routing

How work moves inside the house.

Ignis hands work to each specialist, and the specialists pass it between themselves when a step needs a second pair of hands. Two routes leave the house inside governed workflows.

Drag sideways to explore the map, then tap an agent to open its profile. Hover or tab onto an agent to light up its routes. Arrow keys move between agents, Up and Down jump between houses, Enter opens the profile.

Routes that leave the house

  • Ignis hands off to VeraOut to Sovereign Command
  • Vera verifies IgnisIn from Sovereign Command

Workflows

Workflows this house joins.

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

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

What the house delivers, and where it stops

Delivers

  • A product increment tied to an evidenced user need
  • Acceptance proof that distinguishes built, tested, and shipped states

Stops and asks you when

  • The customer problem or acceptance criterion is unverified
  • The requested change exceeds the named product and repository boundary
  • Launch, production, budget, customer, legal, or brand commitments are requested
  • A scope or architecture choice creates a material irreversible cost