CONNECT
Grant only the systems, signals, and actions this workflow needs.
SAIOS LOOP / GOVERNED OPERATIONS
CLOSE THE LOOP ON FAILURE.
WATCH. UNDERSTAND. APPROVE. RECOVER. VERIFY.
SAIOS Loop begins with an independent evidence layer for critical websites and services. A native private Alpha is running now: it observes, records incidents, verifies recovery, and prepares bounded recommendations. Provider-neutral diagnosis and permissioned recovery are the next stage—not current claims.
OUTSIDE-IN EVIDENCE
MINIMUM NECESSARY ACCESS
NO EXECUTION AUTHORITY
HUMAN AUTHORITY BY DESIGN
MINIMUM NECESSARY ACCESS
NO EXECUTION AUTHORITY
HUMAN AUTHORITY BY DESIGN
AVAILABLE NOW
MONITORING WITH A MEMORY.
The AWS-hosted private Alpha watches 18 public services, records what changed, opens incidents after confirmed failures, and closes them only after the endpoint passes its recovery check. It can recommend; it cannot execute or approve a change.
01
Availability
Outside-in HTTPS checks from a network independent of the service being watched.
02
Incidents
Two confirmed failures open a durable incident instead of turning one network miss into a crisis.
03
Recovery
The incident closes only after the service is observed working again.
04
Recommendations
Bounded proposals remain separate from execution and require accountable human authority.
PRODUCT DIRECTION / THE GOVERNED LOOP
SELF-HEALING IS A CONTRACT, NOT A SWITCH.
Every workflow declares what may be observed, what actions are allowed, what requires approval, how success is verified, and how the system returns to a known-good state.
OBSERVE
Collect outside-in checks, system telemetry, analytics, and change history.
EXPLAIN
Correlate evidence and state what is known, uncertain, and affected.
PROPOSE
Recommend the smallest reversible response and show its verification plan.
APPROVE
Require the accountable person where policy, risk, or consequence demands it.
ACT
Execute only within the declared authority and preserve a complete audit trail.
VERIFY
Prove recovery from the user’s point of view—not merely that a command ran.
ROLL BACK
Return to the last known-good state when recovery does not hold.
ONE WORKFLOW / MANY SURFACES
CONNECT THE TOOLS. KEEP THE AUTHORITY.
Planned adapters let a customer choose the model, cloud, data sources, and operator surfaces that fit their environment. The capability contract stays portable even when a provider changes.
AI PROVIDERS
A tool-neutral workflow layer designed for ChatGPT and Codex, Claude, Amazon Quick, Grok, local models, and future providers.
APPLE COMPANIONS
Focused iPhone, iPad, and Apple TV views for alerts, incident context, approvals, and shared operational awareness.
GOOGLE ANALYTICS
A read-only signal adapter that can correlate experience and traffic changes with incidents without replacing operational telemetry.
OMARCHY
An inspectable plugin for status, approvals, local diagnostics, and operator workflows on an Omarchy workstation.
SAIOS CUBE
A locally controlled platform where Loop can place approved observation and execution close to private systems and data.
OPEN / HOSTED BOUNDARY
The license, trademark policy, contribution terms, and split between public and managed capabilities remain explicit founder decisions.
PRODUCT DIRECTION / AUTONOMY WITH EXPLICIT BOUNDS
START SAFE. EARN MORE AUTHORITY.
L1
OBSERVE
Read signals and retain evidence.
L2
RECOMMEND
Explain the issue and prepare a recovery plan.
L3
ACT WITHIN BOUNDS
Future playbooks may run only after authority, reversibility, and verification are proven.
L4
HUMAN GATE
Escalate production, destructive, uncertain, or representational decisions.
OPEN DIRECTION / MANAGED SERVICE
HELP BUILD AN OPERATIONS LAYER PEOPLE CAN INSPECT, TRUST, AND OWN.
The product now has a name: SAIOS Loop. Its open-source boundary, license, and first public contribution model are being designed now. The native private Alpha is already running while that foundation is designed and tested.