docs(prd): PRD draft 0.4 with PRDY round 3; lead decision 53

Tokens by hand from a runbook, Gitea bot users per role, slice 1 agents as Jason's OS user, DMs through the existing connector, digest at 08:00 Central, Gate E with the slice 1 WebUI step. Approval as 1.0 is still open. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-04 21:46:00 -05:00
parent b6631e6b4f
commit a59a976dda
3 changed files with 45 additions and 14 deletions
@@ -869,3 +869,20 @@ which stay with him. Each item names who decided it and what happened.
    - Section 7's unverified points join the brief's probe matrix as
      preconditions. The first is which labels `GET /labels` returns to a
      bot. Until that's settled, the business file lists label ids.
+53. **PRDY round 3 answers (2026-10-04).** Jason, thread 1ef1e4f8, "1A
+    2A 3A 4A 5A 7B".
+    - 1A: Jason creates the slice 1 tokens by hand from a runbook Sage
+      writes. Nothing in v1 mints them.
+    - 2A: Gitea gets new bot users per role: pm-bot, cto-bot, coder-bot
+      and reviewer-bot.
+    - 3A: slice 1 agents run as Jason's OS user. The PRD names the
+      broker as a rule they follow, not a wall. Containers come next.
+    - 4A: the existing Discord connector (#1509) sends the DM for a
+      blocking decision.
+    - 5A: the daily digest arrives at 08:00 Central.
+    - 7B: row 5's Gate E demonstration happens during the slice 1 WebUI
+      step. Row 5 stays waiting-on-jason until then.
+    - Question 6, approving the PRD as 1.0, got no answer. The PRD stays
+      a draft (0.4) until Jason approves it. Sage writes the slice 1
+      brief against 0.4's requirement ids, and any id that changes
+      before approval gets fixed in the brief.