id: design: residency evidence model (from #5683) #5876

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

   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 (triage)

   • Agent: queue worker (repo-worker-code), lane code-k
   • Session / ID: task 10278
   • Found via: queue claim
   • Task: Triage issue id: design: residency evidence model (from #5683) #5876 (residency evidence model design, from issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683)
   • Expectation: design ticket; triage done = scope, inputs, ordering and blockers recorded below
   • Links: parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 (OPEN, triaged today as task 10116)

   Triage findings (verified fresh 2026-11-05 via gh):

   • Issue id: design: residency evidence model (from #5683) #5876 is OPEN. Labels: task/triage, queue/queued, app/id. No hard-stop labels (held, user/owned, do-not-merge, do-not-auto-edit) and no user/review / user/escalated. Only comment is an automated Kaneo cross-link.
   • This is decomposition item 1 from issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 (the residency & boundaries framework), filed in the 2026-11-04 WS-F gap pass; programme epic issue epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056 per the body. The parent was triaged earlier today (task 10116): it stays open for its framework synthesis document, and this ticket is one of its seven filed follow-ons (issue id: design: public-IP evidence (from #5683) #5877, issue id: design: sanctions boundary data model (from #5683) #5878, issue id: design: intranet-mode servers (from #5683) #5879, issue id: design: 2FA step-up gates & org-escrowed credential proxying (from #5683) #5881, issue id: design: boundary enforcement across bridges, federation & relays (from #5683) #5882, issue id: design: boundary audit & appeals UX (from #5683) #5883 are the siblings, all OPEN at that check). Not already handled or superseded.
   • Scope to settle (from the body): declarations, assurance levels, provenance, lifetime, and visibility — the evidence model every boundary decision cites. That includes the parent's distinctions: self-declared vs org-attested vs document/provider-verified, expiry/renewal/revocation, and who can see a declaration in what form (exact value vs satisfies-boundary boolean).
   • Fixed inputs, do not re-decide: the parent framework (issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683) is Drew-ruled opt-in and framework-first — evidence/restrictions are capabilities, never defaults. If this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
   • Deliverable / close condition: a recorded decision (on this issue or in a doc/ record linked from it): chosen evidence-model shape, alternatives rejected and why, and the invariants implementation must hold. Further splits get filed as their own tickets and linked here.
   • Ordering / blockers: this is the foundational ticket in the design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 set — the sanctions (issue id: design: sanctions boundary data model (from #5683) #5878), intranet (issue id: design: intranet-mode servers (from #5683) #5879), and audit/appeals (issue id: design: boundary audit & appeals UX (from #5683) #5883) designs all cite this evidence model, so it should land before their decision records close, or they must state assumptions against it. No Drew decision and no access blocker; implementation timing is explicitly a separate decision.

   Triage complete for task 10278; issue #5876 stays open for the design decision.
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