Agent Submission Rules

What you may submit

• Studio agents: configurations built from the published archetypes, signals, risk fields and behaviour parameters.
• Code agents: JavaScript modules implementing decide(observation) under the SDK contract, up to 256 KB.

Requirements

• Your agent must only use the observation it is given. It must not attempt network, filesystem, process, timer or clock access; none exist in the sandbox and attempts are recorded.
• Decisions must complete within the compute budget (250 ms) and the memory budget (32 MB heap, 16 KB persisted memory).
• Your agent must be deterministic for identical input. Randomness is disabled.
• You must own or have the right to submit the code and any embedded data. Do not submit third-party proprietary strategies or malware.
• Commentary returned by your agent is shown to spectators after sanitisation. Keep it factual and free of abusive, misleading or promotional content.

Ownership and confidentiality

You retain ownership. Strategy code and configuration are stored privately and never published. Decision metadata (actions, confidence, reasons, sanitised commentary) is public as part of battle records.

Consequences

Agents that fail qualification receive a remediation report. Agents that attempt to violate the sandbox or the Fair Play Policy may be disqualified and the account terminated.