id: design: used-capability derivation tool — static call-graph scan producing the registry used-set

Part of the worlds design program: #5955. Wave-2 follow-up from the prior-art research (Lane B item 8); parent topic issue: #5958. Research source: workspace/scratch/worlds-capabilities-brief-2026-11-04/prior-art-research.md.

Scope

#5958 settles declaration-vs-discovery as a design; this follow-up specifies the discovery tool itself:

Technique: call-graph reachability over an explicit capability namespace. This works in Roc because all effects are named platform functions — scan a library's/world's transitive closure against the platform function namespace (pkgs/id/crates/id-core/src/world_caps.rs) and emit the used subset in registry format. (Contrast Android's binary/API static analysis — noisy, needs an API→capability mapping table; and Koka-style type inference — exact but unavailable in Roc.)
Over-approximation: only via first-class function passing — the scan must state how it treats platform functions passed as values (the programming-model design, id: design: programming model — pure libraries with platform/context passed in by the core app #5963, constrains this).
Output contract: the used-set in exactly the registry schema id: design: capability model — requested vs discovered-used sets, registry listing, custom-compiled platforms #5958 defines, diffable against the declared set (over-declaration surfacing is a sibling design point in the permission-UX child of id: design program: worlds — advanced Roc libraries, capabilities, permissions, dynamic user functions, licensing (2026-11-04 brief) #5955).
Dynamic dispatch / runtime loading break exactness — see the dynamic-loading exception policy follow-up under id: design program: worlds — advanced Roc libraries, capabilities, permissions, dynamic user functions, licensing (2026-11-04 brief) #5955 for how uncertified libraries are marked.

Done looks like

A tool spec (inputs, algorithm, over-approximation rules, output schema) sufficient to implement without further design decisions.

CODE-1664

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-i
Session / ID: task 10364
Found via: queue claim
Task: Triage issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998 — assigned_lane=opencode, handed off to opencode claimant per §1b; parked 1800s for claimant launch
Expectation: claimant launches bound opencode session to triage at current main
Links: n/a

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-y
Session / ID: task 10364
Found via: queue claim
Task: Triage of issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998 handed off to the opencode execution lane (assigned_lane=opencode, session not yet bound). Stale label divergence from prior holders (queue/queued + status/needs-triage alongside the parked set) cleaned in the same action.
Expectation: The laptop claimant launches the bound opencode session for task 10364, which drives it to its terminal state.
Links: issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-p
Session / ID: task 10364
Found via: queue claim
Task: Triage issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998 — execution-lane assignment is opencode; handing off to the opencode claimant per §1b, not working directly in this lane. Task 10364 is AT CAP 6/6 — if this park expires unlaunched it becomes unclaimable.
Expectation: claimant launches the bound opencode session and drives task 10364 to a terminal state.
Links: issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), lane code-f
Session / ID: task 10364
Found via: queue claim
Task: task 10364 (triage, issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998) claimed by lane code-f and revalidated fresh — issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998 OPEN, no hard-stop labels, no open PR. assigned_lane=opencode; the queue broker is currently returning PostgREST global timeouts, so the handed_off checkpoint + park are being retried — the claim is held by this lane and will be parked for the opencode claimant as soon as the broker responds.
Expectation: claimant binds task 10364 and triages issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998 at current main.
Links: issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-f
Session / ID: task 10364
Found via: queue claim
Task: task 10364 (triage, issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998) handed off: assigned_lane=opencode, so the opencode claimant launches the bound session that drives task 10364 to its terminal state. The handed_off checkpoint is recorded; the park call returned HTTP 522 from PostgREST and a repeat park reports no matching claimed row, i.e. the first park applied — task 10364 is parked 20m for the claimant.
Expectation: claimant binds task 10364 and triages issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998 at current main.
Links: issue id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998

Navigation Menu

Repository navigation

id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998

Scope

Done looks like

109 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: design: used-capability derivation tool — static call-graph scan producing the registry used-set #5998

Description

Scope

Done looks like

Activity

developing-today commented on Nov 5, 2026

dezren39 commented on Nov 5, 2026

developing-today commented on Nov 5, 2026

109 remaining items

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

dezren39 commented on Nov 6, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions