Governance commitments

Commitments

What Aarmos commits to

Aarmos governs the execution of declared governance. It does not determine what governance ought to be.

These are technical commitments, not legal ones. They apply to supported governed paths and evidence artifacts, with the required local runtime, policy and retained trust material. Browser controls and standalone Bridge permissions are distinct; these statements do not imply complete coverage or equal qualification across distributions. Consult Run for current support and qualification boundaries. A receipt does not by itself establish deployment isolation, policy quality or downstream business outcomes.

Local-first governance and independently verifiable evidence support customer-controlled deployment within those boundaries. Our Principles describe how we choose to build; they are not additional technical commitments.

What Aarmos commits to

  • Deterministic evaluationThe same declared governance and the same inputs produce the same Decision, on any machine, at any time.
  • Deterministic compositionParticipant contributions combine under one published rule: a contribution may narrow a Decision, never widen it.
  • Evidence integrityEach receipt is signed and chained to the one before it. Alteration, removal, or reordering is detectable.
  • Tamper-evident evidenceEvidence is append-only, signed and hash-chained. Change is detectable; the storage medium is not claimed to be tamper-resistant.
  • Offline verificationA supported artifact can be checked offline against a supplied trust root. The standalone command-line verifier is not currently publicly distributed.
  • ReplayA recorded Decision is reproducible from the contributions recorded alongside it.
  • Contribution attributionEvery Decision is explainable solely from the participant contributions on the receipt. There is no hidden step.
  • Observation is read-onlyWatching a run — in a terminal or a paired browser on the same machine — cannot change a Decision, a policy, or the evidence it describes.
  • Control-plane independencePolicy evaluation, receipt signing and chaining can continue with the required local artifacts when Aarmos-hosted services are unreachable. Hosted administration and managed evidence services may pause or become unavailable.

What Aarmos does not commit to

  • Business correctnessWhether an action was the right one for the business is not something the runtime evaluates.
  • Regulatory complianceAarmos produces evidence auditors can read. It does not determine whether an organization meets an obligation.
  • Policy qualityA policy that permits too much is executed faithfully. The runtime does not judge whether governance is sufficient.
  • External evaluator correctnessAn answer from a customer's evaluator is recorded with its identity and inputs, not re-derived or second-guessed.
  • Organizational approval decisionsAn approval satisfies a step-up. Whether the approver should have approved is the organization's judgement.
  • Action taken outside AarmosGovernance covers what is routed through it. Coverage is reported as counts and named gaps, never assumed.
  • Universal isolation or compromise preventionSupported-path enforcement does not establish universal consequence isolation or prevent initial agent compromise. Customer-controlled deployment and bypass controls remain necessary.
  • Legal non-repudiationIndependent evidence verification establishes the supported recorded facts against retained trust material; it is not a legal guarantee of non-repudiation.
  • Protection against all reverse engineeringThe runtime does not claim protection against all reverse engineering. Customer custody and deployment controls do not establish that protection.

Ownership of each item in the second list is set out in the shared responsibility model. Liability is allocated in the Terms of Service.