id: design: service-held keys (custody variant a) (from #5684) #5886

Activity

1. dezren39

   added

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1569
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   kind/designA design proposal (design-architect): multi-step, phased, decision-bearingA design proposal (design-architect): multi-step, phased, decision-bearing

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane code-y
   • Session / ID: task 10288
   • Found via: queue claim
   • Task: Triage of issue id: design: service-held keys (custody variant a) (from #5684) #5886 (design: service-held keys, custody variant a) at current state.
   • Expectation: triage only — fix path scoped, blockers and ordering recorded. No implementation spawned.

   Triage findings (verified 2026-11-05 against fresh GitHub state)

   • Issue id: design: service-held keys (custody variant a) (from #5684) #5886 is a design-decision ticket, not a code fix. Its deliverable is a recorded decision: chosen custody shape for service-held keys, the signing audit, migration out to self-custody, alternatives rejected and why, and the invariants implementation must hold.
   • Ordering / blocker: parent issue design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684 is still OPEN (kind/design, priority/high, queue/queued). The parent fixes the key-custody variants, security-code recovery, and pseudo-login delegation, and issue id: design: service-held keys (custody variant a) (from #5684) #5886 must not re-decide parent decisions. This design therefore cannot be closed with a decision record until the parent design's decisions land; where an answer here would change a parent decision, it must be recorded explicitly on issue design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684, not forked here.
   • Set, not solo: the custody variants were decomposed as a set — issue id: design: user-held keys (custody variant b) (from #5684) #5887 (variant b, user-held keys), issue id: design: 10 security codes recovery (custody variant c) (from #5684) #5888 (variant c, 10 security codes recovery), issue id: design: pseudo-login identities & scoped do-as delegation (variant d) (from #5684) #5889 (variant d, pseudo-login / scoped do-as delegation), plus issue id: design: native ID creation & setup ceremony (from #5684) #5884 (native ID creation & setup ceremony), issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 (keyless-custody login feasibility), and issue id: design: identity management UX (from #5684) #5890 (identity management UX). All are open. The four variant designs share one custody architecture surface; deciding variant a alone risks forking the shared model, so the variant set should be decided together or explicitly cross-checked.
   • Nothing already settles this: no doc or code on main records a service-held-keys custody decision (repo code search for "service-held keys" returns nothing), and issue id: design: service-held keys (custody variant a) (from #5684) #5886 carries no prior design discussion — only the Kaneo link comment from filing.
   • No implementation task spawned: the issue body states implementation timing is a separate decision, possibly months out. The next action is the design decision itself, sequenced after parent issue design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684; that sequencing is recorded here rather than as a new queue task.
   • Added label kind/design to match the parent's taxonomy. Issue stays open.
5. dezren39

   removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
6. github-actions

   assigned

   dezren39

   on Nov 5, 2026