> For the complete documentation index, see [llms.txt](https://novaq-docs.gitbook.io/novaq/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://novaq-docs.gitbook.io/novaq/novaq-protocol/how-the-protocol-works.md).

# How the Protocol Works?

### **How the Protocol Works (Lifecycle)**

#### 1. **Initialization**

Project submits their AI model to NovaQ (via file hash or hosted model endpoint). Protocol initializes verification sequence.

#### 2. **Model Fingerprinting**

* Model is hashed using SHA3/BLAKE3
* Simulated TEE loads model, generates attestation record
* Fingerprint sent to 3+ MCP nodes for consensus

#### 3. **Merkle Log Anchor**

* Each verification step is hashed and added to a Merkle Tree
* Root hash timestamped and stored (future: on-chain anchoring)

#### 4. **Prompt Optimization (if enabled)**

* Developer submits prompt templates
* Optimizer rewrites using grammar tree reduction, lattice structuring, and safety checkers
* Log of optimizations stored for reproducibility

#### 5. **API Testing (if enabled)**

* Protocol bombards specified endpoints with crafted prompts
* Measures latency, output quality, failure cases
* Generates **Resilience Score Report** with visual summaries


---

# 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, and the optional `goal` query parameter:

```
GET https://novaq-docs.gitbook.io/novaq/novaq-protocol/how-the-protocol-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.