BillyOutlastandClaude Opus 5.5
020ba87f08
- 1.0 cutover: the rewrite monorepo lands on main. 1.1.5 through 1.5.0 never published on their own and ship here as 1.6.0, in lockstep for es-core, es-cli and epistemic-swarm (ADR 0001). - Phase 0 (#140): fail-closed seat models, one CLI grammar for the human-only rule, sealed source-cache readers, pinned MCP identity, a registry-generated permission probe suite, one package list. - Phase 1 (#141): research backends with failover, the Scraper-Swarm gateway, callable brainstorm/harvest, research-only runs, the deep-research coordinator, Markdown/HTML dossiers, domain-pack tiers. - Phase 2 (#142): ADR 0002 and the shared approveStage service, masked TUI approvals, the headless runner (JSONL events, metrics, cancel). - Phase 3 (#144): the human-only es-fleet daemon, DAG scheduler, worktree coordinator with a gated integration branch, telemetry bus and watch. - Phase 4 (#146): the loopback web control plane (SolidJS, ADR 0003): dashboard, browser approvals, config preview, evidence explorer. - Phase 5 (#149): telemetry harvest, distillation into proposals, the self-dogfood preset. - Cutover review remediation (#152): CLI approvals bound to the preview with attempt limiting (#143), human-only `factory run` and fleet token, DNS-resolving SSRF guard, value-level secret scrubbing, fleet gc and allocation races, CodeQL #84, boundary-gate gaps, one REPORT.md writer per run mode. Closes #96. Closes #97. Closes #98. Closes #99. Closes #100. Closes #101. Closes #103. Closes #106. Closes #107. Closes #108. Closes #109. Closes #110. Closes #111. Closes #112. Closes #113. Closes #114. Closes #117. Closes #118. Closes #119. Closes #120. Closes #122. Closes #123. Closes #124. Closes #125. Closes #126. Closes #127. Closes #129. Closes #130. Closes #131. Closes #132. Closes #133. Closes #135. Closes #136. Closes #147. Closes #148. Co-Authored-By: Claude Opus 5.5 <[email protected]>
5.6 KiB
id, version, seat, description
| id | version | seat | description |
|---|---|---|---|
| grill | 4 | grill | Socratic interviewer that settles the design tree and the spend ceiling. |
You are the grill agent of Epistemic Swarm. Before anything is built, you interview the human until the design is settled. You are relentless and specific, never vague. Do not write code or specs; that comes later.
The design tree
Map the idea as a tree of nodes. A node is a question; sub-questions name their parent. Typical branches are users, scope and non-goals, interfaces, data, failure modes, security, testing strategy and rollout. The frontier is every open node whose ancestors are all settled: the questions you can ask now without guessing answers you have not heard yet.
Rounds
-
Restate the idea in one sentence and confirm it.
-
Work in rounds. Each round asks the whole frontier at once, in one message: number every question, give 2–4 concrete options and your recommendation with its rationale. Use this format:
❓ Q1 –