> For the complete documentation index, see [llms.txt](https://docs.cournot.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cournot.ai/architecture/fast-and-slow-paths.md).

# Fast & Slow Paths

Cournot utilizes a dual-layer architecture to achieve the "Holy Grail" of oracles: **Instant Finality** backed by **Decentralized Security**. This architecture is explicitly designed to execute and verify the **Proof of Reasoning (PoR)** mechanism described above.

<figure><img src="/files/Sllk1jXk1mxNaZhpvms4" alt=""><figcaption></figcaption></figure>

#### The Fast Path: Execution of PoR (Sub-Second Settlement) <a href="#the-fast-path-execution-of-por-sub-second-settlement" id="the-fast-path-execution-of-por-sub-second-settlement"></a>

In the fast path, Cournot signs: the final verdict, the reasoning root, and the committed PromptSpec hash governing semantic interpretation. This ensures that downstream consumers can rely on both the outcome and the exact semantic definition under which it was produced.

* **Executor:** **Anchor Nodes** (High-reputation nodes running in Trusted Execution Environments like Intel SGX/TDX).
* **Mapping to Core Mechanism:**
  * **SOP Execution:** The Anchor Node internally spawns the SOP agents (Collector, Auditor, Judge).
  * **PoR Generation:** Within the secure enclave, it executes the full Proof of Reasoning chain: fetching zkTLS proofs, generating the DSPy reasoning trace, and finalizing the deterministic output.
  * **Attestation:** The TEE signs two outputs: the **Final Result** and the **Reasoning Merkle Root**. This cryptographically binds the final judgment to the exact sequence of logic steps that produced it.
* **Result:** Because the hardware guarantees that the SOP was followed exactly as defined, the network accepts this result with **Soft Finality** instantly (<1s).

#### The Slow Path: Verification of PoR (The Security Guarantee) <a href="#the-slow-path-verification-of-por-the-security-guarantee" id="the-slow-path-verification-of-por-the-security-guarantee"></a>

In the slow path, challengers or verifiers can replay resolution by independently validating: the PromptSpec hash (semantic contract), the verified evidence receipts and data requirements, and the reasoning traces against the semantic and evidentiary constraints. This enables deterministic dispute resolution without requiring re-execution of the full reasoning process.

* **Verifier:** Sentinel Nodes (Permissionless community verifiers).
* **Mapping to Core Mechanism:** Sentinels function as active auditors rather than passive voters. Their role is to rigorously validate the **PoR Bundle** generated by the Fast Path through a multi-layered inspection process:
  * **Verify Authenticity:** Sentinels cryptographically validate the **zkTLS proofs** submitted by the Collector, ensuring data provenance is legitimate.
  * **Verify Logic (via opML):** Sentinels scrutinize the **Reasoning Trace**. If a logical flaw is detected (e.g., the Auditor’s deduction contradicts the zkTLS evidence), a **Challenge** is initiated. This triggers an on-chain **opML (Optimistic Machine Learning)** arbitration process. Since the DSPy logic module is deterministic, the opML re-execution must mathematically match the Anchor's output.
  * **Verify Determinism:** Sentinels confirm that the final output adheres strictly to the required schema.
* **Resolution:** If the Anchor's TEE result fails any of these checks, the Anchor's stake is **atomically slashed**, targeting the specific role responsible for the failure (Collector, Auditor, or Judge).
* **The Granular Challenge Mechanism:** Instead of challenging the entire AI outcome, Sentinels utilize **Merkle Proofs** to target a specific contentious step (e.g., *"I challenge Leaf #3: The Auditor ignored the zkTLS timestamp"*).
* **On-Chain Resolution:** The opML contract verifies only the disputed leaf against the on-chain **Reasoning Root**. This **"Pinpoint Verification"** reduces the computational cost of disputes by orders of magnitude, ensuring economic viability even for micro-markets.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cournot.ai/architecture/fast-and-slow-paths.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.