absolutejs-isolated-jsc-example

Host clock via Reference — calls a host-defined now() function from inside the sandbox.

Runaway loop -> TimeoutError — tight while (true) {}; the host enforces the configured timeout.

Memory bomb -> MemoryLimitError — allocates heap-resident JS objects past the configured cap; the isolate terminates.

No host filesystem access — shows the hardened default global shape: host capability globals are not exposed directly.

Result limit -> ResultSizeError — returns a payload larger than maxResultBytes; the host rejects it before app code accepts it.

Capability output limit -> CapabilityError — asks a host capability to return more than its maxOutputBytes; the broker rejects it before sandbox code receives the value.

Console limit -> receipt flag — emits more console lines than the host forwards; the receipt records truncation.

Audit buffer -> receipt flag — calls a host capability repeatedly; the receipt records dropped audit events instead of retaining an unbounded array.

Policy recipe helpers — shows the helper-built audit, broker, console, run, and runner options that wrap the sandbox request.

The example deliberately uses one-shot execution to keep each demo self-contained. A real PaaS should use createIsolatedRunner() to pool by tenant/session, precompile hot callables, and expose host powers through typed capability tools with manifests and receipts.

For user plugins or agent tools, expose only explicit host capabilities, validate inputs, redact audited values, bound audit buffers, set timeouts, and audit every call.