Operational limits

Operational limits

Limits depend on the component and supported execution path. This reference separates technical constraints from software access and commercial terms; it does not establish public edition entitlements.

Service limits are not governance authority

Reaching a service or acquisition limit does not grant broader authority or relax policy on an already-running supported governed path. Optional evidence delivery is separate from local enforcement and signing. This separation does not waive required local evidence capture: if required durable capture fails, the supported runtime refuses forwarding.

Governance commitments and limitations define the qualified boundary. A service limit is not permission to bypass it.

Enforced technical constraints

Supported runtimes apply their configured policy and operational bounds. Resource exhaustion, including a full disk or a read-only evidence store, is not an authorization override. Exact payload, import and delivery ceilings are component-specific, not a universal receipt or deployment allowance.

See the CLI reference and storage guidance for supported operations and failure behavior.

Artifact acquisition and authorization

Evaluation approval and workspace membership do not authorize proprietary software downloads. Each recipient requires individual Aarmos authorization and acceptance of the applicable agreement. Release availability and authorization are checked separately for each software channel; there is no public acquisition quota or fixed edition entitlement on this page.

Acquisition controls concern obtaining software; they do not count agents, governed executions, deployments, or running instances. They do not themselves widen or weaken governance already operating from delivered artifacts. Evaluation expiry and applicable agreements remain separate.

Request Evaluation for access and privately arranged commercial terms.

Local and customer-controlled resources

Retaining evidence locally is subject to device capacity, storage availability, configured pruning and customer backups. The evidence contract does not impose a fixed local retention duration; this is not a promise of unlimited storage or indefinite preservation of every local record.

Browser operational stores and CLI evidence storage are different components. Customer-controlled destinations have their own capacity, retention, availability and access controls. Preserve the exported evidence and trust material needed for later verification.

Shared responsibility and manage storage and retention describe operational ownership.

Configurable limits

The browser’s local operational stores use per-store age, row and storage-size settings. Applicable bounds differ by store; these are not one retention promise for every receipt, conversation or customer deployment. Review the active settings and usage in Storage before relying on retained history.

Runtime policy and resource settings must be assessed on the chosen supported path. Increasing a storage window or resource budget is not a grant of governance authority.

See configuration and storage settings.

Evidence-size contract and inactive hosted services

Aarmos-hosted Evidence Relay is not currently enabled. Its implemented typed-evidence validator rejects sections above 64 KiB (65,536 bytes) and total evidence objects above 256 KiB (262,144 bytes), measured as UTF-8 serialized JSON. The total includes the object’s structure. These are evidence-body contract ceilings, not a universal maximum for a complete signed receipt, CLI archive or container.

These validation bounds do not advertise a currently available hosted ingest service. Hosted daily ingest quotas, retention windows and remaining-capacity displays are not active evaluation entitlements. Any future activation requires separate approval and applicable service terms; no hosted availability or retention commitment is made here.

Rejecting an optional relay write does not change local policy enforcement, receipt signing or the on-device chain. Independently required local capture still applies.

This reference does not alter existing contractual rights. See Terms and Privacy. Operational constraints may evolve; privately negotiated terms remain separate.