You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: implement: demo library + app importing a platform-capability dependency, with both negative tests #5957
Part of the worlds design program: #5955. Statements S5–S7 of the 2026-11-04 brief.
Task (Drew, in substance)
Find — or build — a demo library and a demo app demonstrating the Roc library import model for worlds:
The demo library relies on platform capabilities, so it is technically not pure.
The demo app imports that library and uses it successfully on a platform that provides those capabilities.
Existing starting points: pkgs/id/examples/{roc-world,roc-chat,roc-counter,roc-grid,roc-screen} (the roc-world example already carries the capability protocol helpers in RocCap.roc). Prefer extending an existing example's pattern over inventing a parallel one.
Acceptance criteria — BOTH negative tests are required
Negative test A (capability not on the platform): a variant of the demo app (or the same app compiled against a reduced platform) that tries to use something that is not on the platform must fail — compile-time failure preferred; if the failure is at load/admission time instead, the test must pin exactly that behavior and say why.
Negative test B (platform used wrong): a variant that imports the platform and tries to use it wrong (wrong signature, wrong protocol order, malformed capability request) must fail as a test.
The positive path (app + platform-dependent library on a sufficient platform) passes and runs.
All three cases are wired into the repo's normal test flow so they cannot silently rot — this is also a down payment on the Phase 9–10 Roc-library verification debt in #796 (cf. the closed #813: roc test was never wired into CI for library code).
Related
Import model design (filed alongside this task under #5955)
Demo library + app in the tree, both negative tests running in CI/test flow and failing for the right reason (asserted error, not just any failure), positive path green.
Ruling — C2 capability posture, demo implications (Drew, 2026-11-04 23:57 CST; primary record on #5958).
The earlier working interpretation — that the fs/network posture of tonight's brief supersedes the shipped default — is corrected: the default stays the current completely isolated seccomp policy. For this demo:
The negative tests stand against the default isolated posture (capability not on the platform → fails; platform imported + used wrong → fails).
If the demo exercises file/network capabilities, it does so as the new opt-in tier: off by default on servers, publishing first-party only for now, but built so it could be enabled for anyone later (general enablement is a future, testing-gated decision).
agent-note:v1
task: 10326
lane: code-u
state: picked-up
summary: Triage claimed by lane code-u (direct execution lane). Revalidating issue #5957 against current main before routing.
next: triage findings comment on this issue, then terminal queue state for task 10326.
agent-note:v1
task: 10326
lane: code-u
state: done
summary: Triaged CONFIRMED at current main — valid implementation task, not yet done, no blocker, no competing PR.
next: implementation follow-up enqueued as task 10533 (small_fix, repo-health-code-pilot).
Decision already ruled: Drew's comment on this issue (2026-11-04 23:57 CST) fixes the capability posture — negative tests stand against the default completely isolated seccomp posture; any fs/network exercise is the new opt-in tier, off by default. No Drew decision is outstanding.
Scoping for task 10533: extend the existing roc-world / RocCap.roc pattern rather than inventing a parallel one; positive path on a sufficient platform plus Negative A (capability not on the platform — asserted failure, compile-time preferred) and Negative B (platform used wrong — wrong signature / protocol order / malformed request), all three wired into the repo's normal test flow (also a down payment on issue #796).
Activity
developing-today commentedon Nov 5, 2026
CODE-1623
dezren39 commentedon Nov 5, 2026
Ruling — C2 capability posture, demo implications (Drew, 2026-11-04 23:57 CST; primary record on #5958).
The earlier working interpretation — that the fs/network posture of tonight's brief supersedes the shipped default — is corrected: the default stays the current completely isolated seccomp policy. For this demo:
dezren39 commentedon Nov 5, 2026
agent-note:v1
task: 10326
lane: code-u
state: picked-up
summary: Triage claimed by lane code-u (direct execution lane). Revalidating issue #5957 against current main before routing.
next: triage findings comment on this issue, then terminal queue state for task 10326.
dezren39 commentedon Nov 5, 2026
agent-note:v1
task: 10326
lane: code-u
state: done
summary: Triaged CONFIRMED at current main — valid implementation task, not yet done, no blocker, no competing PR.
next: implementation follow-up enqueued as task 10533 (small_fix, repo-health-code-pilot).
Evidence (fresh gh checks, 2026-11-05):
pkgs/id/examples/contains roc-world, roc-chat, roc-counter, roc-grid, roc-screen (plus lounge, territory); roc-world containsRocCap.roc(capability protocol helpers),platform.roc,RocGrid.roc,RocJson.roc,RocText.roc. Capability catalogpkgs/id/crates/id-core/src/world_caps.rspresent at main (79,834 bytes).gh pr list --search 5957empty).Scoping for task 10533: extend the existing roc-world / RocCap.roc pattern rather than inventing a parallel one; positive path on a sufficient platform plus Negative A (capability not on the platform — asserted failure, compile-time preferred) and Negative B (platform used wrong — wrong signature / protocol order / malformed request), all three wired into the repo's normal test flow (also a down payment on issue #796).
32 remaining items
dezren39 commentedon Nov 5, 2026
🤖 Agent note · parked
dezren39 commentedon Nov 5, 2026
🤖 Agent note · done
bash scripts/roc-test.shfull pass, both negative tests pinned and mutation-verified). Fresh checks this shift: issue id: implement: demo library + app importing a platform-capability dependency, with both negative tests #5957 OPEN with no hard-stop labels; PR examples: capability-dependent demo library + app with both negative tests (#5957) #6237 OPEN and MERGEABLE, diff scoped to pkgs/id/examples/roc-cap-demo + pkgs/id/scripts/roc-test.sh + the roc-world no-caps platform; no Codex reviews or inline comments to disposition. Its CI run has sat QUEUED since 2026-11-05T13:52Z (~5h, 3 pending, 0 failed) — an Actions queue stall, not a failure — so the PR is merged under the standing merge authority (verified work does not wait on a stalled CI queue; CI runs on main).examples: capability-dependent demo library + app with both negative …