Architecture

System Architecture

From plain text to executable meaning. The CNL-PL stack follows a deterministic pipeline: lexical analysis, parsing, validation, AST normalization, and pragmatic execution.

Part 1

The Unidirectional Pipeline

From Lexer to Compiler: a strict one-way flow without backtracking or feedback loops.

Part 2

The Storage Model

Why we don't use SQL. The in-memory Bitset Store and Relation Matrices.

Part 3

The Compiler & Plan IR

The contract of determinism and the intermediate representation that bridges AST and Runtime.

Part 4

Runtime Engines

Different execution strategies for Queries (Fast Path), Proofs (Trace Path), and Planning (Search Path).

Part 5

Identity System

Managing the duality of stable ConceptualIDs and fast DenseIDs via Interning.

Part 6

Proof Traces

The standard contract for explaining answers, used by Explain, Proof, and Planning.

Runtime snapshots

Explain why Socrates is Mortal.
- Socrates is a man.

Solve for ?X such that ?X touches Region_B.
["Region_A"]