Skip to content

id: enforce restricted jurisdiction routing and object entry guards #3400

Open

Description

@dezren39

Follow-up to #2283. Implement the single jurisdiction-required user ID/stub routing module, confined raw binding, restricted namespace selection and fail-closed identity guard at all identity-touching entry points. Both unrestricted and legacy pre-2026-03-15 alarm undefined jurisdiction cases must be safe.

Acceptance: missing jurisdiction cannot create a second empty store; mismatch and missing context reject without side effects; tests cover all entry paths, alarms and raw binding bypass. Depends on directory signup and the hosted Durable Object interface; use #2285 for deployed PoC.

Activity

  1. developing-today commented on Nov 1, 2026

    @developing-today
    Contributor
  2. added
    kind/infrastructureInfrastructure / host-portability work
    priority/highImportant and time-sensitive
    effort/mMedium: expected under 1 day of work
    source/humanFiled directly by a human
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 1, 2026
  3. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Intake review

    Related: #2283 (parent), #2285 (deployed PoC evidence), #3399 (directory signup — dependency), siblings #3401–#3404.

    Notes: Inline Acceptance present (no second empty store on missing jurisdiction; mismatch/missing context reject without side effects; all entry paths incl. alarms and raw-binding bypass tested). Fail-closed identity guard at all entry points is the crux — partial coverage is the known failure mode for this kind of change.

    Risks: The legacy pre-2026-03-15 alarm cases with undefined jurisdiction are easy to miss; the acceptance section names them explicitly.

    Suggested approach: Single routing module first, then entry-point inventory driven by grep for identity-touching handlers, each wired or explicitly exempted with a test.

    — fleet monitor intake (2026-11-01)

  4. added
    queue/queuedHas a queued task in the Supabase agent queue
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 1, 2026
  5. 169 remaining items

  6. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent: repo-worker-code
    state: picked up
    queue: repo-health-code-pilot
    task: 5801
    lane: aea12c82-c5af-4e5a-9b66-f8e360f87177
    found_via: atomic queue claim
    at: 2026-11-04T22:00:40Z

    Claimed task 5801 and resumed its verified state. The packet gates implementation on #3399 landing and #2285 clearing user/escalated. I am revalidating all three issues and implementation PR state fresh; no source edits or worktree have started. I will park if either gate remains unmet.

  7. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 4, 2026
  8. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    agent: repo-worker-code
    state: parked
    queue: repo-health-code-pilot
    task: 5801
    lane: aea12c82-c5af-4e5a-9b66-f8e360f87177
    at: 2026-11-04T22:02:12Z

    Parked task 5801 for 30 minutes after fresh revalidation. Issue #3400 remains OPEN; gate #3399 remains OPEN, assigned to dezren39, and labeled status/blocked + user/escalated; gate #2285 remains OPEN with status/blocked + user/escalated and no residency PoC evidence. No implementation PR for #3400 was found. The packet explicitly forbids starting Phase 2 before #3399 lands, and #2285 authorization remains unresolved. No source or worktree changes were made. Resume only after #3399 merges/closes and #2285 clears user/escalated, then revalidate all issues and PR state. Labels now reflect parked state: queue/parked + status/parked + work/assigned.

  9. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  10. added
    queue/blockedQueue or user escalation state
    status/blockedQueue or user escalation state
    user/escalatedQueue or user escalation state
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 4, 2026
  11. dezren39 commented on Nov 4, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · blocked / escalated to user

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)effort/mMedium: expected under 1 day of workkind/infrastructureInfrastructure / host-portability workmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivequeue/blockedQueue or user escalation statesource/humanFiled directly by a humanstatus/blockedQueue or user escalation statetask/triageQueue packet kind: verify, reproduce, and route this itemuser/escalatedQueue or user escalation statework/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions