Getting Started

Start With A Workflow That Cannot Fail

JacqOS is deterministic containment for non-deterministic intelligence. The fastest way to evaluate it is to choose one workflow where an agent can reason freely but an unsafe action must never reach the outside world.

JacqOS Studio and Cloud are currently distributed through a reviewed private beta. Self-service downloads and new account signup are paused.

Request beta access

Private beta access is reviewed by the JacqOS team.

What Happens After You Request Access

1. We review the workflow. Tell us what the agent can do, which action would be expensive or dangerous, and what evidence your team needs to inspect.
2. We choose a narrow proof path. A useful beta starts with one invariant, one refusal path, and one replayable scenario—not a platform-wide migration.
3. We provide access and onboarding. Accepted teams receive the current Studio or Cloud access path and the matching installation details directly.

This keeps the evaluation tied to a real failure mode and ensures the package, workspace, and organization are provisioned for the same beta release.

The First Proof To Inspect

The flagship walkthrough uses a live AI sales agent that is tricked into proposing a $1 offer on a $68,900 truck. JacqOS lets the model propose the bad action, then refuses to let that action reach the customer because it violates the declared pricing boundary.

During a guided evaluation, you should inspect four things:

• the observation that entered the system,
• the facts derived from that record,
• the proposal the model produced,
• the named invariant that blocked execution.

The result should be replayable. The same observations and evaluator must produce the same decision and the same evidence.

Prepare A Useful Beta Request

Before submitting the form, write down:

• the external action the agent wants to take,
• the business rule that must hold before that action can execute,
• the system that would receive the action,
• the people who need to review the resulting evidence,
• one failure scenario you can replay as an acceptance test.

You do not need Datalog experience or a finished agent architecture. A clear workflow and a concrete refusal condition are enough to start the conversation.

What To Read Next

• Studio Demo — preview the blocked-action walkthrough and the evidence Studio exposes.
• Installation — understand how packages, integrity metadata, and organization access are delivered during the beta.
• What You Just Saw — understand why the model proposes instead of acting directly.
• Examples — choose a proof path by failure mode or industry.
• Trust — review the guarantees, limits, and shared-responsibility boundary before an enterprise evaluation.

When you are ready to evaluate your own workflow, request private beta access.