FAQ
SupraOS FAQs
Answers about mandate-driven execution, Company Twin, Autonomous Charters, receipts, and how SupraOS differs from agents, dashboards, workflow tools, and consulting.
What is the Agent Execution Runtime?
The Agent Execution Runtime is how SupraOS runs approved work. It assigns specialized agents to Work Objects inside Autonomous Charter boundaries, constraining each agent by source access, policies, approvals, evidence requirements, and receipt obligations.
Does SupraOS use external signals?
Yes, when approved and relevant. SupraOS can combine internal operating signals with external context such as competitor moves, market shifts, vendor risk, regulatory change, customer/public signals, pricing changes, and sector-specific data.
How is SupraOS different from agents?
Agents execute tasks. SupraOS discovers the work, structures it, coordinates humans and agents, governs execution, and proves outcomes. Agents do what they are told. SupraOS finds what needs doing.
How can SupraOS work without being told what to do?
SupraOS does not operate without boundaries. Leaders grant Autonomous Charters: approved mandates with goals, systems, permissions, approval rules, and proof requirements. Within those boundaries, SupraOS detects issues, creates Work Objects, coordinates execution, and escalates when approval or judgment is required.
What is a Company Twin?
A living operating model of the business: tools, teams, workflows, owners, customers, vendors, KPIs, decisions, approvals, evidence, risks, and value pools. It lets SupraOS understand what matters and where work should already be happening.
Is SupraOS tied to specific SaaS tools?
No. SupraOS is tool-agnostic by design and source-bound by permission. It builds the Company Twin from approved operating sources: systems of record, systems of work, documents, communications, metrics, contracts, logs, internal tools, APIs, and data stores.
What is source coverage?
Source coverage shows what SupraOS can see, what remains limited, and where blind spots exist. A Company Scan should make coverage explicit before any action authority is granted.
What is an Autonomous Charter?
A business mandate that defines what SupraOS may pursue, what it may observe, what it may coordinate, what it may execute, and what must be proven. Charters hold authority boundaries outside the prompt.
What is a Work Object?
A structured unit of execution that includes the request or discovered need, owners, systems, policy requirements, evidence, decisions, status, and eventual receipt.
What is the Value Leak Engine?
The system that detects work that should already be moving: renewal risk, stalled approvals, missing evidence, vendor delays, CRM/billing mismatches, open obligations, and other money, time, risk, trust, or evidence leaks.
What is the Value Ledger?
A record of value at risk, value captured, risk prevented, time saved, evidence generated, and outcomes proved. It ties execution back to measurable business impact.
What do you mean by receipts?
Receipts are machine-readable proof records of intent, policy, approvals, actions, evidence, systems touched, and outcomes. They support verification, auditability, accountability, and controlled disclosure.
How is SupraOS different from workflow tools?
Workflow tools track work someone entered. SupraOS detects missing work, creates Work Objects, coordinates execution across humans, agents, and systems, and proves the outcome.
How is SupraOS different from dashboards?
Dashboards show what happened and require interpretation. SupraOS recommends interventions, launches governed work, follows up with owners, escalates decisions, and updates receipts and the Value Ledger.
How is SupraOS different from consulting?
Consulting is episodic. SupraOS productizes repeatable consulting work into continuous operating software: diagnosis, synthesis, initiative design, workstream management, executive reporting, follow-up, and value tracking.
What does a Company Scan produce?
A Company Scan starts read-only. SupraOS maps the operating landscape, detects value leaks, recommends the first Autonomous Charter, and defines what should be instrumented for ROI and proof.
Can SupraOS act without human approval?
Only inside the autonomy mode and authority boundaries defined by an approved Charter. Low-risk coordination may run automatically. High-risk actions require policy checks, approval, and evidence requirements before execution.
Do you train models on customer data?
By default, no. Customer data is used to execute the customer’s workflows and generate receipts, not to train shared models, unless a customer explicitly opts into a governed arrangement.
Can SupraOS run in a private environment?
SupraOS is designed with enterprise deployment patterns in mind, including private cloud/VPC options, private networking, and controlled environments for regulated customers.
How do we get access?
Request a Company Scan or email info@supraos.co. We prioritize organizations with high-cost workflows where proof, governance, and speed matter and where impact can be measured quickly.