> 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/3.-cryptographic-foundations/3.4-linearization-and-deterministic-execution.md).

# 3.4 - Linearization & Deterministic Execution

Once anchor blocks are committed, the linearizer module converts the DAG’s partial order into a single, deterministic transaction sequence. All transactions between consecutive committed anchors are collected, ordered by consensus rules, and passed to the native state machine. Because Polarischain excludes virtual machines and smart contracts, state updates follow a fixed validation pipeline: signature verification → balance checks → compliance enforcement → atomic state application. This guarantees reproducible, audit-ready execution across all validator nodes with zero non-determinism.


---

# 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/3.-cryptographic-foundations/3.4-linearization-and-deterministic-execution.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.