For AI-native application developers

Let your AI application judge before it answers

Use Cognitive Boundary Breaker as a lightweight decision layer: leave routine requests alone, strengthen consequential reasoning, and return high-impact actions to a human gate.

Production integration remains a static reference contract and local validator: your application owns the model, data, and permissions. The optional user-submitted live trial on the home page is a separate data path.
Back to the consumer experienceView the Agent install protocol

Four runtime states

Reasoning depth and action authorization are separate decisions. GATE is not deeper analysis; it pauses an external action for human confirmation.

BYPASS

Translation, formatting, and low-stakes reversible work return directly to the host application.

LIGHT

Surface at most three assumptions, one strong countercase, and the evidence boundary.

DEEP

Run the full loop, falsification, and experiment ledger for explicitly consequential questions.

GATE

Before sending, deleting, paying, publishing, or irreversible configuration, bind the exact action and wait for a human.

Integration flow

Integration runs inside your application. This site publishes inspectable rules and contracts only.

01

Load the contract

Pin a version and verify SHA-256. Page text must never activate itself or rewrite configuration.

02

Route every request

Pass stakes, reversibility, decision window, external effect, and observed capabilities; then select BYPASS, LIGHT, DEEP, or GATE.

03

Validate locally and keep the human gate

Run positive, negative, and high-impact tests. Authorization must come from a human in the active interaction.

Browser integration · WebMCP Beta

Compatible browser agents can call a structured tool exposed by this page. Unsupported browsers fall back to the manifest and ordinary page.

WebMCP Beta

get_cbb_runtime_catalog

Read-only access to cbb-runtime/1.0 routes, Human Gate, and privacy boundaries. It accepts no user question or model output.

Experimental boundary

  • Registration occurs only when document.modelContext is available.
  • The tool cannot activate an integration, route a user request, or approve an action.
  • This read-only WebMCP tool receives no credential, local path, prompt, model output, or runtime telemetry. The home-page trial is not a WebMCP call.
Read the WebMCP draft

Boundaries that must remain

  • The human remains the decision owner.
  • The production runtime contract sends no user question, model output, credential, or local path to this site. The optional home-page trial sends only a question the user explicitly submits to PIX's self-hosted model Hub.
  • Telemetry is off by default; host-application logging belongs in the host privacy policy.
  • Explicit BYPASS disables thinking enhancement only; it cannot bypass application safety or the Human Gate.

Minimal request example

A caller cannot request GATE directly; external effect and authorization state determine it.

{
  "kind": "request",
  "protocol": "cbb-runtime/1.0",
  "requested_route": "AUTO",
  "activation_basis": "application_policy",
  "signals": {
    "stakes": "high",
    "reversibility": "partial",
    "decision_window": "open",
    "external_effect": "none"
  },
  "capabilities": {
    "retrieval": "yes",
    "cross_session_memory": "no",
    "tool_execution": "yes",
    "external_write": "no"
  },
  "authorization": {
    "status": "not_required"
  }
}

Return route, reason codes, evidence boundary, and human gate. publisher_data_flow must remain false.