Responsibility model
Shared responsibility
Aarmos governs the execution of declared governance. It does not determine what governance ought to be.
Governing a consequential action involves shared responsibilities. The customer defines enterprise intent, business rules, authority and trusted sources. Aarmos evaluates the proposed consequence under that declared governance and records the resulting execution evidence where supported. The table names where each contribution is recorded, or says when Aarmos does not record it.
| Responsibility | Aarmos | Customer | Where it is recorded |
|---|---|---|---|
| Consequence scope and governance requirementsWhich consequential actions are governed, and what the organization requires before they may proceed. | ✓ | Declared policy; its fingerprint is recorded on governed receipts | |
| Business rulesWhat counts as an acceptable amount, vendor, or change. Aarmos applies the declared rule; it does not author it. | ✓ | Declared policy | |
| External business-rule, risk and approval systemsExternal enterprise systems provide authoritative facts or evaluations. Aarmos policy determines what those facts mean for the Decision. | ✓ | Declared evaluator, and the facts or evaluation it returned, where the governed path records them | |
| Authority modelWho may grant Authority, step-up requirements, kill switch, classification. | ✓ | Signed policy, fingerprinted on the receipt | |
| Policy evaluationEvaluating a specific proposed consequence under the declared governance, deterministically, before execution. | ✓ | Receipt | |
| Decision (allow | deny | step_up | defer)Returning the Decision for the proposed consequence under the narrowing rule. | ✓ | Receipt | |
| Governed execution procedureGoverning the execution attempt where a supported origin enforces. Paths that do not reach a supported origin are not governed. | ✓ | Attempt receipt, on supported enforcing paths | |
| Evidence generationRecording what was authorized, attempted and observed, at the level the supported boundary can establish, sealed so later change is detectable. | ✓ | Signed receipt chain | |
| ReplayReproducing a recorded Decision from recorded inputs, offline. | ✓ | Replay report | |
| VerificationSupported artifacts can be checked offline against a supplied trust root without contacting an Aarmos service. | ✓ | Open verifier | |
| Retention policyHow long evidence is kept. You set the window; how long you must keep records is your obligation, not ours. Today, evidence remains on your device or in storage you control. | ✓ | Configured workspace retention window | |
| Retention enforcementExpiring evidence bodies at the end of your window while receipt identity, recorded Decision, and chain position survive. Your storage: we declare, your storage carries it out. Self-hosted: you enforce. A hosted evidence relay is designed but not currently enabled, so there is no hosted retention to enforce today. | ✓ | Recorded enforcement run and evidence expiry | |
| Local runtime exposureWhere the runtime listens, and who you pair a local observation session with. The runtime binds to loopback and refuses routable addresses; choosing to share the machine is yours. | ✓ | Recorded bind event and exposure class | |
| Organizational governanceWho may approve, what the organization requires, and whether declared governance reflects its obligations. | ✓ | Approval receipts | |
| Business correctness and regulatory obligationsWhether a governed action is the right business outcome, and whether declared governance meets your legal and regulatory obligations. Aarmos records evidence; it does not determine compliance. | ✓ | Not recorded by Aarmos | |
| Agents and application behaviourWhat your agents and applications try to do. Aarmos governs actions that reach a supported origin; it does not control agent reasoning or ungoverned routes. | ✓ | Attempt and Decision receipts, on governed paths only | |
| Permissions and IAMCredential custody and scoping remain with the customer. Paths outside supported Aarmos origins are not governed or observed. | ✓ | Not recorded by Aarmos | |
| Network architectureWhether traffic is forced through Aarmos. The runtime reports the paths it knows; it cannot see routes that never reach it. | ✓ | Known-bypass entries in the containment view | |
| Secrets and credentialsStoring, rotating and scoping the secrets your targets and providers need. | ✓ | Credential references only; values are never recorded | |
| Organization trust rootSupplying, independently checking and holding the organization trust root. Aarmos verifies organization records against the configured root; it does not establish its provenance. | ✓ | Pinned trust-root fingerprint | |
| AI providers for AI AssistChoosing, contracting with and configuring any provider and model. Aarmos supplies no model, and AI Assist sends nothing unless you invoke it. | ✓ | Invocation metadata; drafts go through normal review | |
| Data, content and classificationWhat data your agents handle and how it is classified. Aarmos records the declared classification; it does not discover or inspect content. | ✓ | Declared classification on the receipt | |
| Target-system behaviourWhat a database, queue, provider or API actually does after dispatch. Effects may be uncertain or unavailable, and Aarmos never claims a downstream business outcome. | ✓ | Observed Effect, when the origin can observe it | |
| Deployment and environment configurationHosts, bindings, versions and the environment Aarmos runs in. | ✓ | Recorded configuration and upgrade preflight report | |
| Enforcement boundaries and state reportingDocumenting which paths each supported origin enforces, and reporting enforcing, shadow, unconfirmed and bypass state truthfully. | ✓ | Truth Sheet and containment view | |
| Supported release behaviourSupported capabilities behave as documented; compatibility is checked per workspace and candidate release before you upgrade. | ✓ | Upgrade preflight report |
This table describes how the product operates. It is not a contractual allocation of responsibility; your agreement with Aarmatix LLC governs that.
Why the split matters
If a customer’s declared evaluator returns an answer that turns out to be wrong and the governed path recorded that evaluation, the receipt shows it plainly: which evaluator ran, which recorded inputs it consumed, what it returned, and how that evaluation contributed to the Decision. The record does not argue a position. It removes the ambiguity that would otherwise require one.
Related
- Governance commitments — what the runtime commits to, and what it does not.
- Terms of Service — how liability is allocated.
- Limits — technical constraints, configurable local retention and customer resource responsibilities.
- Trust — verification, keys, and evidence portability.