Hook Body

Capability tokens a script body may request.

The runtime sandbox enforces these — if a body uses a ctx API that requires

a capability it did not declare, the call throws at invocation time.

• api.read — ctx.api.object(...).find / findOne / count / aggregate

• api.write — ctx.api.object(...).insert / update / delete

• crypto.uuid — ctx.crypto.randomUUID()

• crypto.hash — ctx.crypto.hash(algo, data)

• log — ctx.log.info / warn / error

http.fetch is intentionally absent — outbound calls go through Connector

recipes (separate spec) so they remain auditable and replayable.

TypeScript Usage

import { ExpressionBody, HookBody, HookBodyCapability, ScriptBody } from '@objectstack/spec/data';
import type { ExpressionBody, HookBody, HookBodyCapability, ScriptBody } from '@objectstack/spec/data';

// Validate data
const result = ExpressionBody.parse(data);

ExpressionBody

L1 expression body — pure formula, no IO

Properties

HookBody

Hook/Action body — expression (L1) or sandboxed JS (L2)

Union Options

This schema accepts one of the following structures:

Option 1

L1 expression body — pure formula, no IO

Properties

Option 2

L2 sandboxed JS body — runs inside an isolated VM with declared capabilities

Properties

HookBodyCapability

Allowed Values

• api.read
• api.write
• crypto.uuid
• crypto.hash
• log

ScriptBody

L2 sandboxed JS body — runs inside an isolated VM with declared capabilities

Properties