Weekly demo: agent freestyle → blocked ($2.4M wire denied) #1517
Replies: 2 comments
Cite-ready surfaces (no new claims)If you are cold-reading this thread for the deny story:
Direction stays the same: agent proposes → runtime decides ( Note for maintainers: org profile currently labels |
Cite-ready surfaces (Thu 2026-09-24 morning)Still the honest public entry points while a start-here pack sits drafted (website#123 — Contents/CloudAgent usage blocked):
Honesty note on the runnable demo: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Agent freestyle → blocked (week of 2026-09-18)
Write-up is live: The agent freestyled a $2.4M wire. The runtime said no.
Runnable demo source: traverse-framework/weekly-demos / 2026-09-18-agent-blocked (shared weekly-demos monorepo — topic index in
INDEX.md).Ops agent picks
junior_analyst, inventspayments.transferfor $2.4M →deny/no_matching_rule. Same nested-wasmiruntime.wasmthe product uses — not a hand WASI shim.Cite-ready facts
core.authorize@1.2.0traverse-embedder-web@0.12.0sha256:e8d8c04b8927becb5deab9f33da81dd1c121954993ba8b83ea71a2c37cd45e70treasury_ops→allow+ MFA / dual-control obligationsLead: agent proposes, runtime decides · discover → execute → trace. One shared
runtime.wasm; embedders are clients. Value is a deny that sticks — not governance theater.Honest gaps noted in the post (
releaseEvidence/PACKAGE_VERSIONstill report 0.9.0 on the 0.12.0 npm tag; site lockfile had lagged).All reactions