Self-improving intelligence. Customer-controlled authority.
SupraOS continuously improves its understanding, priorities and recovery paths from verified transitions while customer-set permissions and approvals continue to govern every action.
Effective and last reviewed: 16 July 2026
Authority starts with a Charter
A Recovery Charter defines the business objective, human owner, approved sources, permitted action classes, actions that must be held, approval rules, evidence requirements, confirmation rule, and stop conditions.
Observe
Read approved sources and surface evidence-linked work.
Propose
Prepare the recovery plan, required work and expected result.
Coordinate
Create and route work, evidence requests, and approvals without releasing a consequential write.
Execute
Perform permitted actions only inside the current Charter, policy, permission, and approval boundary.
Verify
Read supported destination systems back and record the observed result.
Improve
Use checked results to improve company context, recommendations and the next recovery path.
Consequential actions
External communications and legal, financial, access, pricing, customer, production, or other material actions can require explicit human approval. The exact boundary is stated in the deployment schedule.
Approval stays tied to the exact action
Approval stays bound to the exact reviewed action. If the target, action or execution context changes, SupraOS pauses and requests approval again.
Action states
Allowed
The action is inside scope and may proceed under the current authority.
Held
Evidence, approval, or a required condition is missing; the action remains pending.
Blocked
The action is outside scope, prohibited, expired, or cannot be safely verified.
Connector changes and human-completed work
Connector-verified work
SupraOS reads the destination system back and compares the observed state with the exact approved action before marking the change verified.
Human-completed work
Human work keeps its accountable owner, reported completion and supporting record. It is not presented as a connector-verified system change.
Rollback and compensation
Rollback and compensation are configured by connector and action class.