Run the bundled example
Use a deterministic example so the evaluation is about the system boundary, not prompt luck.
How To Evaluate
How to evaluate JacqOS in 20 minutes.
Run a demo, inspect a blocked action, open provenance, read the verification output, and decide whether the operating model actually fits the workflow you care about.
Open a blocked action
Look for the refusal path that names the invariant or decision rule that stopped the action.
Trace provenance backward
Confirm that the system can show the exact observation and derived state behind the proposal.
Read the verification output
Fixtures, replay, and verification artifacts should make the contract visible without reading generated logic.
Test one real workflow
Map the operating model to a concrete expensive failure mode in your own domain before deciding fit.
Decision checklist
- Is the expensive problem really about bounded real-world actions, approvals, or accepted facts?
- Will your team actually maintain invariants, fixture corpora, and explicit authority rules?
- Do replay, provenance, and blocked-action receipts materially help your rollout or buying motion?
Red flags
- You mostly need lightweight orchestration or low-stakes prompting, not a strong boundary.
- Your team wants the model to remain the unbounded driver of truth and action.
- You are not prepared to encode the domain contract outside the prompt.
Evaluation path Examples
Browse proof-first examples by failure mode and by industry.
Explore → Evaluation path Studio TrackSee the human review loop built around invariants, fixtures, replay, and provenance.
Explore → Evaluation path TrustRead the guarantees, limits, and verification surfaces in plain language.
Explore → Evaluation path Studio DemoRun the deterministic bundled demo before you write any app code.
Explore → Evaluation path Verification BundleInspect the artifacts JacqOS exports for review, replay, and audit.
Explore →Next step
Use one workflow as the real fit test.
If the boundary looks strong in the demo, the next useful move is to map JacqOS onto one concrete workflow where a bad action would actually matter.