Limits and versions
Design within explicit protocol, payload, collection, artifact, and lifecycle bounds instead of discovering them in production.
Limits protect deterministic execution, mobile hosts, Station recovery, and reviewability. Exact schema maxima remain authoritative; this page highlights the boundaries authors most often need.
| Boundary | Current contract |
|---|---|
| Package UI message | PACKAGE_UI_MAX_MESSAGE_BYTES |
| Connector protocol frame | CONNECTOR_MAX_MESSAGE_BYTES (64 KiB) |
| Station observation | STATION_OBSERVATION_MAX_BYTES (64 KiB) |
| Station delivery batch | STATION_BATCH_MAX_OBSERVATIONS (50) |
| Activity effects per transition | 128 |
| Metrics per activity | 64 contract maximum; author brief intentionally narrows to 16 |
| Artifacts / contributions per package | 128 each |
| Creator event delivery page | 100 items |
| Creator capture clock samples | 512 |
| Creator media anchors | 5,000 |
| Creator upload part | 8 MiB |
Do not split one semantic fact merely to evade limits. If a real vertical cannot fit, document representative evidence and propose a contract tranche.
Version identities are separate
Keep these concepts distinct:
- package semantic version: immutable released bytes;
- capability version: host/extension feature contract;
- configuration version: interpretation of saved mode setup;
- result-contract revision: whether Measurements remain comparable;
- progression definition version: rank thresholds and evidence policy;
- observation contract version + payload digest: exact source semantics;
- schema version: serialization shape for one named protocol.
An update can advance one without advancing all. The evolution guide explains when history must split.
Agent API and MCP
Let an authorized coding agent find Pursuits, install Suites, create Sprints, and submit a private package without gaining practice or billing authority.
Release and review
Prepare immutable package or connector bytes, prove them locally, and preserve enough evidence for independent review.