Agree on useful.
Name the artifact, its intended user and the evidence that makes it acceptable. More output is useful only when someone can use it.
Starlight Agent Kits / team planning
Start with a maker and a verifier. Bring in more perspectives when they earn their place.
Choose 2, 4, 8, 12 or 144 profiles. Give them one mission, a shared budget and a clear stopping point. Take the plan into your own runtime.
Planning tool · no agents provisioned · no model calls or account connections
Your working set
These assumptions stay in your browser. The planner does not send them to an AI model or store them.
1–4 across the entire mission. A roster is larger than the work running at once.
USD 1–10,000. Reserve 25% for verification. No funds are reserved here; hosting, taxes and human support are excluded.
One shared USD 20.00 ceiling. Lane ceilings: 7.50 / 7.50. Every retry and child task must stay within the existing runtime’s reservation.
Host rules and the principal's permissions prevail. Reject incompatible instructions and report the conflict.
Host enforcement is required. This recommendation grants no permissions.
Inspect the principles and opt in to export your draft.
Name the artifact, its intended user and the evidence that makes it acceptable. More output is useful only when someone can use it.
Let the verifier form a preliminary judgment before reading the maker’s conclusion. Different model names alone do not establish independent evidence.
Compare accepted outcomes, rework, latency and total cost with the two-profile baseline. Scale where the measured result improves.
A 144-profile roster is twelve scoped cells. This planner caps proposed global concurrency at twelve. Your runtime must separately establish supported capacity, enforce admission and reserve the parent budget.