Public Product Notes
Reviewer Guide
The shortest path for program reviewers evaluating what SimOracle is, what is live, and how pilots are meant to prove governed autonomy.
What to understand first
SimOracle is Cognitive Intelligence for governed autonomy. It is designed to interpret live context, simulate likely consequences, preserve evidence, and move work through an explicit authority model.
The important distinction is the path to autonomy. SimOracle does not ask reviewers or buyers to accept a black-box agent with unlimited authority. It starts with reviewable decision packets, then expands from recommendation to supervised execution to bounded autonomy as the workflow proves itself.
The reviewer mental model
- Context: what is happening, who is affected, and what source material matters
- Consequence: what changes if the action moves now, later, or not at all
- Authority: whether the system should answer, recommend, hold for approval, or act autonomously
- Audit: what evidence, rationale, approval, and outcome should be preserved
What is intentionally public
These docs explain the product model, operating boundaries, pilot path, and governance posture. They avoid disclosing internal implementation details, proprietary orchestration patterns, private infrastructure choices, or customer-specific configuration.
Best reading path
- Start with Product Overview for the category and product surface
- Read Governance and Autonomy to understand why autonomy remains the goal
- Read Pilot Readiness to see how the first workflow should be evaluated
- Read Architecture Overview for the public system model without private build details
- Use Data and Trust Boundaries for security, compliance, and reviewer caveats