Scale without exhausting the browser

Theoretical size is the product of value counts across participating dimensions and is calculated with arbitrary-precision integers. Size can grow faster than visual or storage capacity, so the browser never builds an unbounded product.

Small spaces use bounded local enumeration and store at most one configured page per action. Large spaces use authenticated engine routes. The browser sends model and version selectors plus bounded settings; Arena reloads the authorized persisted version, verifies method access and feature entitlements, builds a safe projection, and forwards only that projection to the engine.

Engine responses have byte, result-count, deadline, and schema limits. Exact enumeration, partial search, and representative sampling are labelled differently. A sample is never reported as the exact feasible count. Timeouts or unavailable services preserve model edits and analysis settings. Returned configurations and the canonical analysis reference are saved through normal optimistic-concurrency version persistence.