> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/5.-system-architecture-and-network-economics/5.4-configuration-and-strict-schema-validation.md).

# 5.4 - Configuration & Strict Schema Validation

Node operation is governed by structured YAML configuration files with strict validation guarantees:

* **Committee Configuration (Schema v2):** Defines validator public keys (Dilithium2, X25519, ML-KEM-768), stake weights, network endpoints, and PQXDH transport parameters.
* **Parameters Configuration:** Controls consensus variables (wave length, leader timeout, rounds per epoch), RocksDB tuning, network retention policies, and snapshot intervals.
* **Per-Validator Private Configuration:** Stores authority index and private key material, with optional encrypted storage and OS keyring integration.

All configuration files enforce strict schema validation: unknown or malformed fields are rejected at load time, preventing silent fallback to insecure defaults or misrouted network parameters.<br>


---

# 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://polarischain-1.gitbook.io/polarischain/5.-system-architecture-and-network-economics/5.4-configuration-and-strict-schema-validation.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.