id: design: intranet-mode servers (from #5683) #5879

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-1562
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 · picked up

   • Agent: queue worker (repo-worker-code), lane code-u
   • Session / ID: task 10281
   • Found via: queue claim (direct execution lane)
   • Task: Triage issue id: design: intranet-mode servers (from #5683) #5879 — verify the design ticket's standing, parent state, and ordering at current main.
   • Expectation: s — triage findings + ordering recorded on issue id: design: intranet-mode servers (from #5683) #5879.
   • Links: task 10281 (repo-health-code-pilot)
5. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triage findings (task 10281, lane code-u, direct lane)

   Verdict: VALID design ticket, correctly filed and linked — ACTIONABLE AS A DESIGN PASS in parallel with its siblings, per the parent's own triage ordering. Not superseded.

   Evidence (fresh, 2026-11-05):

   • Issue id: design: intranet-mode servers (from #5683) #5879 is a follow-on design ticket from issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683's decomposition sketch, filed in the 2026-11-04 WS-F gap pass; programme epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056 (open). Subject: intranet-mode servers — boundary definition, generic-activity gating, fail-closed behaviour, break-glass.
   • Parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683 is OPEN and was triaged today (task 10116, lane code-k). Its recorded ordering governs this ticket: the parent's remaining deliverable is the framework document, authored as a synthesis referencing the seven decomposition designs; where a decomposition design is still open, the framework states the shared vocabulary and leaves the surface detail to that ticket — it does not pre-empt them, and they are not blocked on it. Parent triage recorded: blockers none external, priority low, no Drew decision needed.
   • No intranet-mode decision record exists on current main (searched doc/ at 04f7869).

   Ordering / next action (recorded per triage acceptance):

   • This design pass may proceed in parallel with its siblings. Where it overlaps the shared vocabulary, it should consume — not redefine — the terms being settled in issue id: design: residency evidence model (from #5683) #5876 (residency evidence model) and issue id: design: sanctions boundary data model (from #5683) #5878 (sanctions boundary data model); any point where this design would change a parent decision (Drew-ruled opt-in, framework-first; every restriction an opt-in capability, default off) must be recorded explicitly on this issue rather than silently forked, per the filing.
   • The design pass closes this ticket with a recorded decision: boundary definition, generic-activity gating, fail-closed behaviour, and break-glass shape, plus rejected alternatives and implementation invariants. Implementation timing is a separate decision, possibly months out (per the filing), so this triage enqueues no implementation follow-up.
   • Priority is low per the parent framing; this should not pre-empt higher-priority app/id design work. No status/blocked is set: unlike a stage-gated design, nothing external blocks the design pass itself.

   This triage (task 10281) completes as triaged; issue #5879 stays open as the design ticket of record.
6. 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-u
   • Session / ID: task 10281
   • Found via: queue claim (direct execution lane)
   • Task: Triage of issue id: design: intranet-mode servers (from #5683) #5879 complete — valid design ticket; per parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683's triage ordering (task 10116) the design pass proceeds in parallel with its siblings, consuming issue id: design: residency evidence model (from #5683) #5876 / issue id: design: sanctions boundary data model (from #5683) #5878 vocabulary where they overlap; low priority per parent framing. Findings in the triage note above.
   • Expectation: done — triage outcome exists.
   • Links: task 10281 (done, outcome triaged), parent issue design(id): residency & boundaries framework — opt-in evidence, sanctions, and intranet-mode capabilities #5683
7. 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
8. github-actions

   assigned

   dezren39

   on Nov 5, 2026