Skip to content

docs(wasm): compute-unit build guidance and trigger/discovery - #170

Merged
jamiesun merged 1 commit into
mainfrom
docs/wasm-compute-unit-guidance
Jun 27, 2026
Merged

docs(wasm): compute-unit build guidance and trigger/discovery#170
jamiesun merged 1 commit into
mainfrom
docs/wasm-compute-unit-guidance

Conversation

@jamiesun

Copy link
Copy Markdown
Collaborator

What

Expands the Agent Compute Units page (book/en and book/zh, kept in sync) with three guidance sections, in response to questions about what Wasm units are worth building and how they get invoked.

Added

  1. Recommended Compute Units — a selection principle (deterministic + usable under readonly + dependency-free) plus two tiers of high-leverage units (structured-data query/convert, safe calculator, hash/encode-decode; then redactor compressor, diff/patch, token counter).
  2. Not-recommended units — an explicit anti-pattern list explaining why network, filesystem, clock/randomness, regex, and stateful/installer units do not belong in the pure data-transform sandbox (sandbox traps them, or built-ins already cover them).
  3. How Units Are Triggered (And Discovered) — clarifies the two trigger paths (model-driven wasm_tool for kind="tool" vs host-driven automatic kind="compressor") and the discovery gap: Scoot does not advertise individual packages, so a tool package is most useful shipped alongside a skill that advertises its path.

Scope

Docs-only. No code or behavior changes. English and Chinese pages updated together per the documentation language policy.

Validation

  • mdbook build book/en and mdbook build book/zh both build clean.
  • Pre-push local CI passed.

…tion

Expand the Agent Compute Units page (EN + ZH) with three additions:

- Recommended compute units: a selection principle (deterministic +
  usable under readonly + dependency-free) and two tiers of
  high-leverage units to build first.
- Not-recommended units: an explicit anti-pattern list explaining why
  network, filesystem, clock/randomness, regex, and stateful/installer
  units do not belong in the pure data-transform sandbox.
- How units are triggered (and discovered): clarifies the two trigger
  paths (model-driven wasm_tool vs host-driven compressor) and the
  discovery gap that Scoot does not advertise individual packages, so a
  tool package is most useful shipped alongside a skill that advertises
  it.

Docs-only change; mdBook builds clean for both book/en and book/zh.
@jamiesun
jamiesun merged commit b8e8b87 into main Jun 27, 2026
7 checks passed
@jamiesun
jamiesun deleted the docs/wasm-compute-unit-guidance branch June 27, 2026 18:14
@jamiesun jamiesun mentioned this pull request Jun 30, 2026
jamiesun added a commit that referenced this pull request Jun 30, 2026
- Opt-in PreToolUse policy hook at the guard() chokepoint (#136, #177)
- Opt-in PostToolUse audit/observability hook (#137, #179)
- Structured ReACT event sink for protocol adapters (#156, #178)
- WebAssembly spec conformance test suite for scoot-wasm (#163, #180)
- project-audit agent skill scoring ten dimensions of repo health (#168)
- scoot-edge E1 status heartbeat + E0 boundary doc (#172, #173)
- Harden scoot-wasm against hostile bytecode: explicit traps/errors, no OOM panic (#174, #181)
- Tighten agent boundary guardrails (#176)
- Wasm compute-unit build guidance and docs (#170)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant