Infrastructure Architecture
The ten-layer stack and the modules that compose it.
6.1 The ten layers
LARP is built on ten layers of infrastructure. Each layer depends on the layer beneath it and is verified by the layer above it. The tenth layer is verified by the first.
| Layer | Name | Responsibility |
|---|---|---|
| L00 | Existence | Exists |
| L01 | Infrastructure | Supports L00 |
| L02 | Consensus | Agrees that L01 supports L00 |
| L03 | Legitimacy | Confirms agreement is legitimate |
| L04 | Application | Hosts undefined use cases |
| L05 | Recursion | Repeats L00–L04 as required |
| L06 | Audit | Audits L00–L05, then itself |
| L07 | Verification | Verifies the audit |
| L08 | Abstraction | Abstracts L00–L07 into a single interface |
| L09 | Transformation | Reorders the deployment symbol |
6.2 Module catalogue
The ten core modules (Recursive Consensus Layer, Zero-Knowledge Legitimacy Engine, Autonomous Verification Matrix, Symbolic Transformation Module, Decentralized Validation Network, Proof-of-Existence Generator, Adaptive Infrastructure Layer, Recursive Audit Mechanism, Lexical Reversal Engine and Consensus Optimization Protocol) are documented interactively in the Architecture section of the homepage.
6.3 Codebase layout
For engineers: the interface and the launch pipeline are separated. Launch logic lives server-side in lib/launch, behind a provider interface, and the interface communicates with it through a single prepare endpoint. Providers can be replaced without touching the interface.