Execution units and limits
Resource accounting and the exact bounds in the reviewed preview profile.
XU is the display name
The node displays Execution Units as XU. Signed eu-schedule-0.1 identifiers and historical EU fields remain unchanged for verification. Costs accumulate: a host function may also incur argument-expression and function-call charges. These numbers are not total per-line costs, wall-clock durations, or monetary fees.
| Metered operation | Schedule cost |
|---|---|
| Source block of up to 32 bytes (at least one) | 1 |
| Statement / expression | 8 / 4 |
| Function call / entry | 20 / 30 |
| Loop iteration / collection item | 12 / 2 |
| State get / put | 120 / 180 |
| Event emission / SHA-256 host operation | 250 / 160 |
Profile limits
Limits are part of the selected profile. A source file can validate yet fail for a particular input, state, capability set, or budget. Test boundary cases explicitly.
| Resource | Limit |
|---|---|
| Source / input / context | 65,536 / 262,144 / 65,536 bytes |
| AST nodes / functions / arguments per function | 5,000 / 32 / 16 |
| Call depth / aggregate loop iterations | 32 / 10,000 |
| Data nesting / collection items | 64 / 10,000 |
| State keys / key bytes / total state bytes | 256 / 128 / 262,144 |
| Events / total event bytes | 64 / 65,536 |
| Output bytes | 65,536 |
| Integer / decimal precision | Signed 256-bit / 38 decimal digits |
Runtime budgets are not worker isolation
The execution node runs jobs in isolated, resource-bounded workers, separate from the reference simulator. Host memory, CPU, and wall-clock limits are additional deployment controls. An interpreter receipt, a worker termination, and a node attestation are different pieces of evidence; a timeout should not be presented as successful computation.