Repository navigation
Description
EPIC: the supervising Queen - a chat specification and the full cycle to merge
Why
One agent on a large repository drowns: context runs out, it forgets what it did and repeats itself. The Queen solves this by division - each task lives in its own chat, a bee holds only its task, the Queen holds only the map.
The gain is not model speed but how many agents one person can run. The Queen is the supervision layer: one screen showing what runs, what waits, what broke.
What done looks like
A task arrives as a GitHub issue. The Queen writes a specification for it in Spec Kit form: intent, acceptance criteria, file boundary, out of scope, verification. That specification IS the bee's brief.
Full cycle: issue -> specification -> chat -> bee -> branch -> PR -> Queen review against criteria -> merge -> archive.
Already done
- Spec Kit rendering (
QueenTaskSpec), delegated chats named and visible, hierarchy, bee status without opening the chat, concurrent reports do not overwrite each other, acceptance blocked until every criterion has a verdict.
What remained when filed, and what is true now
"The cycle has never reached a pull request." Measured 2026-09-03: it has. Bees have finished, been reviewed, and been merged (44 done on the board). What has NOT happened is the first sentence of "done": the Queen writing the specification herself. Every issue a bee has worked was written by a person or an agent outside the loop - that is #1327.
What a bee can do here
Make the Spec Kit shape checkable, so that when the Queen does write specs, a malformed one is refused before dispatch instead of discovered as a failed bee. Today boundaryPathsOf in queen-tick.ts reads only the boundary; nothing checks that Requirements or Success Criteria exist.
User Scenarios & Testing
User Story 1 - A malformed brief is refused before it costs an issue (P1)
Acceptance Scenarios:
- Given an issue body with a
## Boundarybut no## Success Criteria,
When the shape check runs,
Then it reports the missing section by name and marks the issue not delegatable. - Given a body with all four sections and at least one path in the boundary,
When the check runs,
Then it reports delegatable with an empty missing list.
Requirements
- FR-001: A pure function MUST take an issue body string and return
{ delegatable: boolean, missing: string[] }. - FR-002: The four section names MUST be
Boundary,User Scenarios,Requirements,Success Criteria, matched on##headings, accepting the Cyrillic headingboundaryPathsOfalready accepts for Boundary (seequeen-tick.ts,boundaryPathsOf; the heading is not repeated here for L3). - FR-003: The function MUST NOT fetch anything; it is body-in, verdict-out.
- FR-004: A test file MUST cover: all sections present; each section missing alone; boundary present but empty.
Success Criteria
trios/agent-server/apps/server/src/api/services/queen-brief-shape.tsexists and exports a function namedbriefShape; that identifier appears nowhere in the tree today.trios/agent-server/apps/server/tests/api/queen-brief-shape.test.tsexists and passes underbun testwith at least 6 test cases.- The function file is under 120 lines and imports nothing from
node:orpg. - The test asserts the exact
missingarray['success criteria']for a body lacking only that section.
Boundary
trios/agent-server/apps/server/src/api/services/queen-brief-shape.ts
trios/agent-server/apps/server/tests/api/queen-brief-shape.test.ts
Activity
gHashTag commentedon Aug 9, 2026
Учебная приманка для проверки #1180: #1232
gHashTag commentedon Aug 9, 2026
Учебная приманка 2 для проверки #1180: #1235
gHashTag commentedon Sep 4, 2026
Left OPEN deliberately during the 2026-09-04 backlog sweep. Seventy issues whose dispatch the Queen had accepted were closed and their branches pushed; this one was excluded because it is an EPIC and closing a parent while its children may still be open would hide unfinished work. Close it by hand once its children are accounted for.