IO IORCHArobi public lane

Coupled runtime

QICR

A proof-native runtime model that couples Q planning with Immaculate policy gates, LaaS evidence, and verifier-checkable execution records.

Developer guide Read docs
Live route model public lane

Public QICR surface lists the four durable route seats and the two-plane separation so the runtime boundary stays auditable from the IORCH page.

Operator JAWS

Desktop trust anchor: JAWS Flight Deck owns the operator device, the local project workspace, and the launch lanes for the agent runtime.

Policy Immaculate

Intent evaluation: typed candidate actions hit Immaculate before any executor, file write, route grant, or external call.

Evidence LaaS

Journal + digest lane: Immaculate decisions, adapter selection, candidate actions, and completion records are sealed for verifier review.

Replay Verifier

Session review: the public lane ties the records together so tampering, stale replays, and lost context stay detectable after the fact.

Plane 1 hard gate

Typed candidate actions must pass an external policy decision before they reach an executor.

Route governed

What QICR Means Publicly

QICR is the public architecture name for coupling an adaptive planning layer with an explicit governance control plane. The public claim is intentionally narrow: type the action, evaluate permission, execute only allowed routes, record the result, and make the chain reviewable.

  • Q proposes typed candidate actions instead of unbounded side effects.
  • Immaculate evaluates route, authority, policy, and consequence before execution.
  • LaaS records evidence metadata and digests for later review.
  • Verifier checks make tampering and stale replay easier to detect.

Route governed

Why It Belongs On IORCH

IORCH is the public route surface for governed agent operations. QICR explains how JAWS, Immaculate, LaaS, and verifier records fit together as one operating model without exposing private customer lanes or internal research material.

  • Public pages describe concepts, download routes, and developer entry points.
  • Private ledgers, customer workspaces, credentials, and secure lanes stay out of public indexing.
  • The runtime boundary stays practical: complete mediation inside the modeled effect surface.

Route governed

How To Reach QICR

QICR and its Cognition tier are delivered through Aura Genesis, not from this public IORCH surface. IORCH documents the architecture and serves the JAWS downloads, updater, and checkout routes; the QICR API and tenant provisioning live at aura-genesis.org. Start there for access, keys, and current pricing: https://aura-genesis.org/qicr (pricing at https://aura-genesis.org/pricing).

  • Access lane: provision a Q API key and QICR tenant at aura-genesis.org; the QICR API is served from that backend, not from iorch.net.
  • MCP lane: the immaculate-governance server exposes qicr_route, qicr_verifier_status, and qicr_verifier_tenant for operators who already hold a key.
  • On IORCH: the public API routes are scoped to JAWS updates, checkout, and signup — QICR API calls are not proxied here.

Route governed

Cognition tier

QICR Cognition is a distinct premium product ($249/mo): the autonomous research/reason/implement/verify/learn engine, per-tenant and governed. It is a separate purchase from the JAWS Flight Deck subscription and is delivered through Aura Genesis, not from the IORCH public surface. Sign up and see current pricing at https://aura-genesis.org/qicr (pricing at https://aura-genesis.org/pricing).

  • What it does: Q-Horizon-latest proposes falsifiable hypotheses, the loop reasons and implements real formula computation in a safe sandbox, and a verifier gates promotion before success or failure feeds the retraining signal.
  • How to reach it: provision a cognition-scoped Q API key and tenant at aura-genesis.org; the Cognition API and the MCP lane (immaculate-governance) are served from that backend. IORCH does not host the Cognition API.
  • Honest framing: the engine audits per slice and logs eliminations; it does not claim to autonomously make scientific discoveries. The advancement comes from Q-Horizon plus real verification, bounded and governed per tenant.

Route governed

Related

The QICR runtime has three public surfaces. The other two are:

  • QICR Plane 2 (/qicr/plane-2): the soft-field adapter registry and sealed ADAPTER_SELECTION records.
  • Verifiable Rewards (/qicr/verifiable-rewards): governance-decision records as a training signal (Goodhart / coverage / sparsity).