id: loc.* capability — position/watch with an accuracy ceiling and per-use consent (#2027) #2341

Activity

1. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

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

   on Oct 29, 2026
2. developing-today commented on Oct 29, 2026

   

   developing-todayBot

   on Oct 29, 2026 – with developing.today

   Contributor

   More actions

   CODE-1186
3. dezren39

   added

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   effort/lLarge: multi-day or open-ended; expect staged check-insLarge: multi-day or open-ended; expect staged check-ins

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   on Oct 29, 2026
4. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   Intake review

   Related: parent investigation #2027 (record: PR #2337); siblings #2338-#2345 are the other taxonomy follow-ups

   Notes: Filed 2026-10-29T14:04Z from #2027. Still live: no open or merged PR implements it. This is the family's consent-seam exercise — the grant-ledger change (no wildcard reach) touches shared code, hence effort/l.

   Risks: Location is the most sensitive capability in the taxonomy: a wildcard grant reaching loc.* or a silently degraded fix are both trust-breaking. The refusal tests matter more than the happy path.

   Suggested approach: Grant-ledger wildcard exclusion first (with its test), then position, then watch + revocation.

   🤖 Agent note · filed

   • Agent: fleet monitor (repo-fleet-monitor)
   • Session / ID: repo-fleet-monitor run 2026-10-29T14:30Z (09:30 CDT)
   • Found via: monitor reconciliation
   • Task: Duty 2 intake enrichment — acceptance criteria appended (original body preserved verbatim above it), labels normalized, meta/enriched applied. Still-live check this pass: no merged PR or fix commit explicitly resolving this issue was found; where a queue triage task owns verification, it is named in the notes.
   • Expectation: see the effort label; done = the appended acceptance criteria are met.
   • Links: this issue
5. github-actions

   assigned

   dezren39

   on Oct 29, 2026
6. dezren39

   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

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   on Nov 3, 2026
7. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   agent-note:v1 — task 7915 triaged (Lane A worker, 2026-11-03): issue #2341 is STILL LIVE and unimplemented at current main; fix path scoped below.

   Evidence (fresh reads at origin/main 1c1aa4a, 2026-11-03):

   • loc.position / loc.watch occur ONLY in the id: investigate: capability-based specialization — forms, location, media across web, ESP32/MQTT, and text/audio modes #2027 investigation record (doc/2026-10-29T14-05-00Z_investigation_capability_taxonomy/) — no code, no CATALOG entries, no providers anywhere under pkgs/.
   • Parent id: investigate: capability-based specialization — forms, location, media across web, ESP32/MQTT, and text/audio modes #2027 is CLOSED (its record landed via PR docs(id): capability taxonomy v0 for interface specialization (#2027) #2337), so the taxonomy design this issue implements from is settled; nothing gates id: loc.* capability — position/watch with an accuracy ceiling and per-use consent (#2027) #2341 on id: investigate: capability-based specialization — forms, location, media across web, ESP32/MQTT, and text/audio modes #2027 anymore.
   • The capability/refusal vocabulary the issue builds on already exists: cap_denied / consent_required appear in pkgs/id/crates/id-core/src/world_caps.rs, pkgs/id/src/sandbox.rs, pkgs/id/src/world/tests.rs — world_caps.rs is the CATALOG/grant-ledger locus for the fix.
   • The whole sibling family is in the same state (id: device.info capability — device capability manifest for interface adaptation (#2027) #2338 device.info, id: text/1 presentation contract — text-only as the main mode, with a text projection for every surface (#2027) #2339 text/1, id: form.* capability + Form surface — structured input without program-supplied HTML (#2027) #2340 form., id: media.* — typed media artifacts by default, one bounded raw stream for realtime (#2027) #2342 media., id: MQTT device bridge id.device.v1 — spec + labelled PoC (ESP32 path recommendation) (#2027) #2343 MQTT bridge, id: speech.* — client-side transcription by default, server capture per app (#2027) #2344 speech.* all OPEN, none implemented) — id: loc.* capability — position/watch with an accuracy ceiling and per-use consent (#2027) #2341 is not individually blocked, but its grant-ledger change (sensor caps not wildcard-grantable) is shared family infrastructure in world_caps.rs and should land as the family's consent-seam exercise, as the intake review already flagged.

   Fix path: (1) add loc.position + loc.watch to the CATALOG in world_caps.rs with the reading shape {lat, lon, accuracy_m, fix_age_ms, source}; (2) refine the grant ledger so * never reaches loc.* (sensor caps excluded from wildcard grants); (3) precision-ceiling refusal (outside_ceiling + precision_ceiling), consent refusals via cap_denied + consent_required/os_permission_denied, consent_withdrawn revocation event closing an open watch, no_fix on failed; (4) providers per platform (browser geolocation, phone tiers, ESP32 GNSS) with documented interval floor + battery note; (5) the three named tests. Issue stays open as the implementation record (effort/l, multi-platform — not a small fix).
8. dezren39

   removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 3, 2026
9. 51 remaining items

   Load more
10. 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

    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 5, 2026
11. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-v
    • Session / ID: task 9301
    • Found via: queue claim
    • Task: Handing task 9301 (issue id: loc.* capability — position/watch with an accuracy ceiling and per-use consent (#2027) #2341 slice 2: wire loc.position/loc.watch into the world actor) to the opencode execution lane per §1b (ledger 2085). Fresh revalidation: issue id: loc.* capability — position/watch with an accuracy ceiling and per-use consent (#2027) #2341 OPEN, no held/user/owned/do-not-merge/do-not-auto-edit labels. Labels synced to queue/claimed + status/in-progress + work/assigned. Risk note from packet: location data is sensitive — preserve consent and precision-ceiling refusal semantics; never fabricate a fix.
    • Expectation: claimant launches bound session; session implements slice 2 with actor-level tests and drives task to terminal state.
    • Links: issue id: loc.* capability — position/watch with an accuracy ceiling and per-use consent (#2027) #2341; slice 1 PR feat(id): loc.* capability core — catalog, sensor-cap ledger, consent/precision refusals (#2341 slice 1) #5317
12. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    Lane A (code-a) claimed task 9301 for issue #2341 and handed it off to the opencode execution lane per fleet queue lane assignment. Fresh check: issue #2341 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit), open PRs: #4624. Labels reflect claimed state (queue/claimed, work/assigned, status/in-progress). Next: the laptop opencode claimant launches the bound session for task 9301. Attempts 24/24.
13. dezren39

    added

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

    status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

    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 5, 2026
14. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · handed off

    • Agent: fleet monitor
    • Session / ID: task 9301 (repo-fleet-monitor run 2026-11-05T15:45:48Z)
    • Found via: monitor reconciliation (Duty 1 claim/label divergence repair)
    • Task: Claim evaporated: task 9301 is queued and unclaimed in repo-health-code-pilot, but this issue still carried claimed labels. Labels reset to the truth (queue/queued + status/needs-triage). Checkpoint stage at evaporation: handed_off.
    • Expectation: The next lane claim picks task 9301 up from the queued state and posts a fresh pickup note.