PUBLIC DEMO

Small workloads.
Hard limits.

Try conservative TINY/SMALL demonstrations of all four engines. The web request only validates and queues work; MIK-LAB-01 executes it asynchronously through the outbound worker bridge.

BOUNDED FORMS

Choose an engine.

Frontend limits are only a convenience; the API, database and workstation independently enforce the same or stricter policy.

G1

Gold1 · TINY / SMALL

Count a small interval

Public intervals are capped by server policy; benchmark-scale ranges stay restricted.

R2

Red2 · TINY / SMALL

List small primes

The full sieve and high-range screen are never exposed through the public demo endpoint.

B3

Blue3 · TINY / SMALL

Reference scan

The public path uses the bounded reference implementation; native large-search controls remain restricted.

V4

Violet4 · TINY

Inspect search grammar

Public mode exposes bounded search information only. Training and holdout validation remain owner/licensed workflows.

LIVE STATUS

Queue and node state.

The site remains responsive even if MIK-LAB-01 is offline. Jobs are persisted in the cloud database and no browser request waits for numerical execution.

MIK-LAB-01

Public demo queue

Checking…
UnknownNode
Queue
Public compute

Public compute remains disabled until the owner explicitly enables it in the Admin Command Centre.

SAFETY BOUNDARY

What the public endpoint cannot do.

Benchmark-scale or owner/licensed workloads cannot be reached by changing form HTML or calling the API directly.

01

Classification gate

Every request is classified TINY, SMALL, MEDIUM, HEAVY or REJECTED; only TINY and SMALL may enter the PUBLIC queue.

02

Queue gate

At most four public jobs may be non-terminal globally and at most two per public identity.

03

Workstation gate

MIK-LAB-01 must explicitly advertise ALLOW_PUBLIC_COMPUTE=true and reclassifies the claimed job before launch.

04

Compute isolation

The HTTP/API process never runs the numerical engine itself; it only stores and reports jobs.