id: design: keyless-custody login feasibility (investigation) (from #5684) #5885

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-1568
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

   on Nov 5, 2026
4. github-actions

   assigned

   dezren39

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

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   🤖 Agent note · handed off

   • Agent: queue worker (repo-worker-code), lane code-v
   • Session / ID: task 10287
   • Found via: queue claim
   • Task: Triage: id design — keyless-custody login feasibility investigation (from issue design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684) (issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885)
   • Expectation: handed off to the opencode execution lane; the laptop claimant launches the bound opencode session, which drives task 10287 to its terminal state.
   • Links: issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885
6. developing-today

   added

   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

   and removed

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

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

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   🤖 Agent note · state: handed off

   • Agent: queue worker (repo-worker-code), lane code-m
   • Session / ID: task 10287
   • Found via: queue claim (task 10287 returned to the queue after a prior handoff park expired unbound)
   • Task: Triage of issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 (id design: keyless-custody login feasibility, from design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684) is assigned to the opencode execution lane — handed off again to the opencode claimant, which launches a bound session to drive task 10287 to its terminal state.
   • Expectation: claimant launches the bound opencode session during the park window; if unbound at lease expiry, task 10287 returns to the queue.
   • Links: issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885
8. developing-today

   added

   queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

   status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
9. 115 remaining items

   Load more

10. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-f
    • Session / ID: task 10287
    • Found via: queue claim
    • Task: task 10287 for issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 assigned to the opencode execution lane; handing off to the opencode claimant, which launches the bound session. Re-verified fresh: issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 OPEN, no hard-stop labels.
    • Expectation: claimant launches the bound opencode session for task 10287; this lane does not work it directly.
    • Links: issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885
11. dezren39

    added

    queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

    status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume condition

    queue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)

    on Nov 6, 2026
12. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    🤖 Agent note · picked up

    • Agent: OpenChamber scheduled lane (repo-worker-code)
    • Session / ID: task 10287; lane 7b47536b-c162-444c-be8a-3a9538cc4cb5
    • Found via: atomic queue claim in repo-health-code-pilot
    • Task: Triage issue id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 at current main. The prior queue progress repeatedly routed this to the opencode execution lane; this OpenCode scheduled lane is now working it directly rather than handing it off again.
    • Expectation: verify current issue/PR state, record the design-ticket routing and any blockers, then close task 10287 with evidence.
    • Links: id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 · task 10287
13. dezren39 commented on Nov 6, 2026

    

    dezren39

    on Nov 6, 2026

    MemberAuthor

    More actions

    Triage at current main (2026-11-06; origin/main dfe3277).

    • State / duplication: id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 and parent design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684 are OPEN. GitHub search for open PRs referencing id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 returned none. PR fix(id-web): collision-proof spaced-destination placeholders on save (#1348) #4665 is OPEN but its scope is unrelated (id(web): spaced-destination placeholder can collide with document text — global replace on save rewrites the document's own words (PR #1022) #1348, Markdown destination placeholders); it is not a competing PR. No hard-stop labels are present.
    • Current implementation / prior art: pkgs/id/src/directory.rs has AccountSignedUp and AccountKeyed account models, but a current pkgs/id/src search found no Google/OIDC/OAuth/WebAuthn/PAKE login implementation. The existing doc/2026-10-29T11-28-18Z_investigation_key_recovery_hosted/ (id: investigate: key recovery for hosted users — Google SSO loss vs the ID keypair #2060) is relevant prior art: it separates hosted-account SSO from identity-key custody and argues SSO must not rebind a key. It does not settle this issue's username/password and PAKE feasibility, login-method × custody matrix, or exact signed setup/hash construction, so id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 is not superseded.
    • Route / scope: keep id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 as a design-only investigation per its non-goals. Produce the feasibility matrix for Google/OIDC and username/password across the custody variants; name established constructions or blockers, including offline-guessing exposure for password-derived material; and specify the setup statement/hash, storage and verification flow. Do not implement login here or re-decide design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684's simplicity-first and custody boundaries. No runtime reproduction or code tests apply.
    • Ordering: id: design: native ID creation & setup ceremony (from #5684) #5884 (native ID setup ceremony) is interleaved for the exact setup artefact and first signatures. Run this feasibility investigation now/in parallel with that setup design; settle its result before finalizing dependent variant designs id: design: service-held keys (custody variant a) (from #5684) #5886, id: design: user-held keys (custody variant b) (from #5684) #5887 and id: design: pseudo-login identities & scoped do-as delegation (variant d) (from #5684) #5889. id: design: identity management UX (from #5684) #5890 should consume the resulting login/custody UX. There is no hard blocker to starting the investigation; these are design coordination edges, not implementation prerequisites.
    • Follow-up: id: design: keyless-custody login feasibility (investigation) (from #5684) #5885 itself is the already-filed follow-on design ticket, so no duplicate issue/task was created.

    Outcome: scoped and ready for design/research; no evidence of completion or supersession.

    🤖 Agent note · triaged

    • Agent: OpenChamber scheduled lane (repo-worker-code)
    • Task / lane: 10287 · 7b47536b-c162-444c-be8a-3a9538cc4cb5
    • Links: design(id): identity, login & delegation — simplicity-first key custody, security-code recovery, and pseudo-login identities #5684, id: design: native ID creation & setup ceremony (from #5684) #5884–id: design: identity management UX (from #5684) #5890; prior-art record id: investigate: key recovery for hosted users — Google SSO loss vs the ID keypair #2060
14. dezren39

    added

    status/triagedTriaged and routed (see agent note)Triaged and routed (see agent note)

    and 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 6, 2026