# How to Navigate This documentation space is the thinking layer of the Life Enterprise System (LES) — a long-term, enterprise-grade personal operating system built and documented in public by [NikiDigitals](https://nikidigitals.com/). This page explains how the space is organised, who each section is written for, and how to find what you are looking for. *** ### How the Space Is Structured The GitBook is divided into twelve top-level sections. Each section serves a distinct function. #### 00 — Introduction The starting point for any reader. This navigation guide, the document taxonomy, and the project overview are contained in this document. Read this section first. #### 01 — Vision & Strategy The founding documents of LES. Covers the project concept, the five-year roadmap, the master project plan, and the governance framework. This section establishes the *why* before the *what*. #### 02 — Project Governance Operational governance of LES as a project: scope management, change control, review cadence, and quality standards. This section treats LES as a live project under active management. #### 03 — Architecture The technical backbone of the system. Contains the architecture overview, module architecture, infrastructure design, data architecture, integration layer, and diagramming standards. The most technically detailed section. #### 04 — Modules One sub-section per department. Each module section covers its data model, processes, intelligence requirements, and agent specification. Modules are populated as they enter active development. #### AI Agents The multi-agent system that powers LES intelligence. Covers the agent architecture, the orchestrator design, and the specification for each department agent. #### Security & GRC Security architecture, governance, risk and compliance frameworks, and audit and monitoring standards. Security is a cross-cutting concern in LES and receives dedicated documentation. #### Decision Log Every significant architectural, strategic, technology, and operational decision recorded and reasoned. Decisions are indexed and cross-referenced. This is the audit trail of the project. #### Research Academic-style research notes on topics directly relevant to the LES architecture and domain. Structured as standalone research entries with references. #### The Journey The learning record. Weekly journal entries documenting what was built, what was learned, and what changed. Written for a reader who wants to understand the human experience of building a system like this from scratch. #### Reference Conventions, standards, taxonomy, and templates used across the project. The authoritative reference for how things are named, formatted, and classified. #### Articles & Publications Longer-form writing produced as part of the NikiDigitals body of work: technical articles, reflections, and published pieces. *** ### Document Codes Every document in LES carries a reference code. These codes appear in page headings and cross-references throughout this space. The coding system is explained in full on the [Document Taxonomy & Coding System](https://app.gitbook.com/o/tbne7ZtUlyqO49hsY3QC/s/Nb5M0j365A1RgeUSUy4w/00-introduction/document-taxonomy-and-coding-system) page. *** ### External Links Every section of this space contains at least one exit point to each of the other three portfolio layers. Cross-layer links are formatted consistently and appear at the foot of major pages. * **Website:** [nikidigitals.com](https://nikidigitals.com/) * **GitHub:** [github.com/NikiDigitals](https://github.com/NikiDigitals) * **Niki Digitals LinkedIn:** [linkedin.com/company/niki-digitals](https://linkedin.com/company/niki-digitals) * **Personal LinkedIn:** [linkedin.com/in/nmlangendam](https://linkedin.com/in/nmlangendam) *** *This space is a live documentation record. It is updated continuously as LES develops. All content is authored by* [*NikiDigitals.*](https://www.nikidigitals.com/) --- # Agent Instructions: 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: ``` GET https://nikidigitals.gitbook.io/les/00-introduction/how-to-navigate.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.