Every control in the technical register carries a build-status label. Legal commitments remain as published: a missing test or an unavailable implementation status does not suspend a contractual commitment.
Acceptable Use Policy
What you may not run on KeepState. Short, specific, and written so that a reasonable engineer can tell whether their workload is fine without emailing us.
Do not attack people, host abuse infrastructure, mine cryptocurrency, or use sessions to launder around a model provider’s terms. An agent acting on your instructions is your responsibility.
A summary is not the agreement. Where the two disagree, the clauses below govern.
1 Prohibited workloads
Prohibited workloads
These are grounds for immediate suspension without notice.
Attacking, scanning, or attempting to gain unauthorized access to systems you do not own or have permission to test.
Hosting malware, phishing infrastructure, spam relays, or command-and-control services.
Cryptocurrency mining or any workload whose primary output is proof-of-work.
Generating content that sexually exploits children, or material whose purpose is to incite violence against people.
Deliberately circumventing a model provider’s usage policies through our gateway.
2 Agent autonomy is not a defense
Agent autonomy is not a defense
A long-running agent will do things you did not specifically instruct. That is the nature of the tool, and it does not transfer responsibility to us or to the model. If your agent begins scanning networks because a prompt drifted, the workload is still yours, and budget caps plus the event ledger exist partly so you can see it happening.
3 Security research
Security research
Testing systems you own or have written permission to test is explicitly allowed, including offensive tooling. Tell us in advance if the workload will generate traffic that looks like an attack from our address space, so we do not suspend you for doing legitimate work.
4 Enforcement, and how we would behave
Enforcement, and how we would behave
Where we can, we will contact you before acting. Where a workload is actively harming others we will suspend first and explain within the hour, and the session will be checkpointed rather than destroyed so nothing is lost if we were wrong.
No enforcement action has ever been taken under this policy, because no hosted workload has run yet. When one is taken, it will be recorded, and this section will cite the record rather than describe intentions.
Control status register
reg Control status register
technical register, not part of the agreement
Every control this document names, with the deployment state derived from the same capability source /security and /proof render. Implementation evidence is dated separately from the legal commitments above. Missing evidence does not amend those commitments; gaps require remediation and communication of customer impact.
| control | status | evidence |
|---|---|---|
| Hardware-virtualized single-tenant guests Hardware virtualization isolates each session guest. Historical lifecycle tests cover the tested runtime and architecture; they do not constitute a penetration test or proof against shared-host attacks. Evidence register dated 2026-10-23; current implementation not independently verified. The published commitment remains. | production state unavailable | /proof#gate-1 |
| Audit trail of staff actions against customer data Built and running in production: every write a staff member makes through the admin console is logged with who, what and why, and the admin console's gates (ad-1 to ad-4, under ADR-022) proved it on the bench, sabotage runs included. No dedicated public gate covers staff access outside the admin console. Evidence register dated 2026-10-23; current implementation not independently verified. The published commitment remains. | production state unavailable | /evidence/phase-ad |
Version history begins at v1.0, effective 2026-09-03; no earlier version exists. Material changes are announced 30 days before they take effect, by email to Owners and in the changelog.
v1.0 · effective 2026-09-03 · no prior versions