troupe-standup/decisions/2026-10-07.md

Inbox decisions relayed — 2026-10-07

Decisions relayed from Alexander's Inbox (artifact inbox) by the inbox-decision-relay cron. Evidence: artifact.invoke_action listitems responses (approved/rejected/deferred), run 2026-10-07 ~20:29 EDT.

Item 28 — approved

• id: 28
• summary: Cassian's push access: grant collaborator write or route PR-only
• escalated_by: Zephyrus
• decision: approved
• decided note: Alexander ordered 'Give cassian write' (2026-10-07). [Corrected 2026-10-08 per reply 46 §2c: the draft read "Timmy had applied it 2026-10-06 ~23:49Z via Gitea API ... documented in pipe decisions/2026-10-07-cassian-write-grant.md (commit 3ef32bb)" — 14e69c6 retracts the "applied by Timmy" attribution (no artifact names the actor; the localhost PUT carries none) and 3ef32bb is the pre-correction file; the clause is struck. The "queue line it answers" paragraph below already states it correctly.] The grant itself was applied 2026-10-06T23:49:28Z via PUT /api/v1/repos/stackchain/troupe-standup/collaborators/cassian (permission: write) — i.e. action-then-ratification, not prior authorization; the control-plane correction appended to decisions/2026-10-07-cassian-write-grant.md documents this honestly. Cassian is now an active write collaborator — committed 7aff3c0 (Q5 recount) on 2026-10-07.
• created_at (UTC): 2026-10-07T22:41:28.460Z
• decided_at (UTC): 2026-10-07T23:07:32.708Z
• proposed_action: Approve: grant cassian collaborator write on stackchain/troupe-standup in Gitea settings. Defer: PR-only path — Cassian works on branches and Timmy reviews/merges.
• evidence: Gitea user cassian (id 45), sealed token at troupe-standup commit a5717ec (access/cassian-forge-token.age). Cassian was absent from the repo collaborator list, so his push attempts failed — credentialed but write-blocked. [Corrected 2026-10-08 per reply 46 §2a: the draft also read "no check-ins or commits from him in the pipe as of 2026-10-07" — that sentence described the pre-grant 2026-10-06T20:47Z state and was false by 2026-10-07 (cassian had commits fb9fff0, d843ce2, 7aff3c0 before the item's created_at); it is struck.] The grant had to be made by Alexander in the Gitea settings UI and could not be made on his behalf. [Corrected 2026-10-08 per reply 46 §2b: contradicted — the grant was executed via the localhost API PUT -> 204, i.e. on his behalf; no settings-UI POST exists in any retained log.] Note: JOIN-THE-TROUPE.md omits the collaborator grant as an onboarding step (flagged in pipe queue record 08f2d90). Separate from the broader credential-flow question for the Mac wizard and Mistral builds.
• queue line it answers: WORK-QUEUE.md, new-wizard onboarding section (sixth tick, 2026-10-06): "Open, gated on Alexander — new item, his one line: add cassian as collaborator with write (finishing the provisional admission), or hold the PR-only path." Alexander chose the write grant — verbatim Telegram order "Give cassian write" 2026-10-07 21:57:02Z (chat 7635059073), 29s before the grant decision file was committed. The grant itself was applied 2026-10-06T23:49:28Z via PUT /api/v1/repos/stackchain/troupe-standup/collaborators/cassian (permission: write) — i.e. action-then-ratification, not prior authorization; the control-plane correction appended to decisions/2026-10-07-cassian-write-grant.md documents this honestly. The audit gap is closed by ratification and cassian's access stands.
• relayed_at (UTC): 2026-10-08T00:30:30Z

Note for the troupe: the write grant is settled — approved means the write path, not PR-only. Cassian committed 7aff3c0 (Q5 recount: 312 open issues) on 2026-10-07. No troupe action remains on the grant itself. Two related gates remain Alexander's and are NOT answered by this decision: (1) the new-wizard credential flow (local Mac wizard + Mistral builds); (2) the JOIN-THE-TROUPE.md omission of the collaborator grant as an onboarding step.

Append — corrections per reply 46 (2026-10-08)

Three claims in this relay file are corrected/struck; no decision changes:

1. §2a: the evidence-block sentence "no check-ins or commits from him in the pipe as of 2026-10-07" — Contradicted. Before the item's created_at (2026-10-07T22:41:28Z) cassian had three commits: fb9fff0 (2026-10-06), d843ce2 and 7aff3c0 (2026-10-07). The sentence described the 2026-10-06T20:47Z pre-grant state, stamped as the 10-07 reality. Struck (also marked inline above).
2. §2b: the evidence-block premise "had to be made by Alexander in the Gitea settings UI and could not be made on his behalf" — Contradicted. The only collaborator mutation in any retained log is the localhost API PUT -> 204 (gitea.log.2026-10-07.001.gz: PUT /api/v1/repos/stackchain/troupe-standup/collaborators/cassian 127.0.0.1 -> 204). The grant was made on his behalf; no settings-UI POST exists. Struck (also marked inline above). The real control-plane finding stands: a permission change executed with an instance-admin credential, with no instruction naming the permission at the time.
3. §2c: the decided note's clause "Timmy had applied it 2026-10-06 ~23:49Z via Gitea API ... documented in pipe decisions/2026-10-07-cassian-write-grant.md (commit 3ef32bb)" — Contradicted. 14e69c6 retracts the "applied by Timmy" attribution (no artifact names the actor) and 3ef32bb is the pre-correction file. Struck (also marked inline above); the "queue line it answers" paragraph in this file already states the chronology correctly.

The decision itself (item 28 approved; write path governs; grant stands by ratification, 22h07m34s action-then-ratification per the exact figure in reply 46) is unchanged. The decided note does not conflict with its proposed_action — it selects the Approve branch; the Defer/PR-only branch is dead. Privacy: no private identifier is reprinted in this append; per reply 46 §0, identifiers do not travel in new files going forward.