# Document Taxonomy & Coding System

Every document produced within the Life Enterprise System (LES) carries a structured reference code. This page defines the full taxonomy: what codes exist, what they mean, where the documents they identify are stored, and how they appear across the four portfolio layers.

This system was adopted as a formal project decision (Decision 17) and applies to all documentation without exception.

***

### Why a Coding System

LES produces documentation across multiple platforms, multiple repositories, and multiple audience layers. Without a consistent reference system, cross-referencing becomes ambiguous, versioning becomes unreliable, and the audit trail breaks down.

The coding system serves three purposes:

1. **Identification** — every document has a unique, unambiguous identifier.
2. **Classification** — the code communicates the document type and owning domain at a glance.
3. **Traceability** — a code appearing in any layer (GitHub, GitBook, LinkedIn) points back to a single authoritative source.

***

### Document Type Codes

| Code Pattern         | Document Type                 | GitHub Location               | GitBook Section                    |
| -------------------- | ----------------------------- | ----------------------------- | ---------------------------------- |
| `ADR-YYYY-MM-DD`     | Architecture Decision Records | `docs/decisions/`             | Decision Log                       |
| `LES-ARCH-000[NNN]`  | Architecture Documents        | `docs/architecture/`          | Architecture                       |
| `LES-DIAG-000[NNN]`  | Diagrams                      | `docs/architecture/diagrams/` | Embedded in pages                  |
| `LES-ROAD-000[NNN]`  | Roadmaps                      | `docs/roadmap/`               | Vision & Strategy → Master Roadmap |
| `LES-PLAN-v[N]`      | Project Plan sub-pages        | `docs/project-plan/`          | Vision & Strategy → Project Plan   |
| `LES-[MOD]-000[NNN]` | Module Specifications         | `docs/specs/` in module repo  | Modules                            |
| `LES-AGT-000[NNN]`   | Agent Architecture Documents  | `docs/` in LES-AGT repo       | AI Agents                          |
| `LES-SEC-000[NNN]`   | Security & GRC Documents      | `docs/` in LES-SEC repo       | Security & GRC                     |
| `LES-GOV-000[NNN]`   | Project Governance Frameworks | `docs/governance/`            | Project Governance                 |
| `LES-RES-000[NNN]`   | Research Notes                | `docs/research/`              | Research                           |
| `LES-JOUR-000[NNN]`  | Learning Journal              | `journal/`                    | The Journey                        |
| `LES-PUB-000[NNN]`   | Articles & Publications       | `docs/publications/`          | Articles & Publications            |

***

### Module Codes

Module specification documents use the pattern `LES-[MOD]-000[NNN]`, where `[MOD]` is the three-letter module identifier. The full list of module codes is as follows:

| Code      | Module                     |
| --------- | -------------------------- |
| `LES-FIN` | Finance & Wealth           |
| `LES-EDU` | Education & Knowledge      |
| `LES-HLT` | Health & Performance       |
| `LES-PRJ` | Projects & Goals           |
| `LES-REL` | Relationships & Network    |
| `LES-OPS` | Daily Operations           |
| `LES-KNW` | Knowledge Base             |
| `LES-INT` | Intelligence & Analytics   |
| `LES-AGT` | AI Agent Orchestration     |
| `LES-SEC` | Security, GRC & Compliance |

***

### Architecture Decision Records (ADRs)

ADRs are the primary mechanism for recording decisions. They follow a distinct convention from all other document types.

**Naming convention:** `ADR-YYYY-MM-DD.md`

One file is produced per day. All decisions made on a given day are grouped within that single file, organised by subject. This approach avoids fragmentation while maintaining a clear chronological record.

**Internal structure of each ADR file:**

* Architecture Decisions
* Strategic Decisions
* Technology Decisions
* Operational Decisions

Each decision entry contains a decision statement and rationale. For high-impact decisions, full alternatives considered and anticipated consequences are documented.

**GitBook flag:** Each decision carries a GitBook: Yes/No flag indicating whether it warrants publication to the Decision Log section.

***

### Learning Journal (LES-JOUR)

Journal entries follow a distinct cadence from all other document types.

**Naming convention:** `LES-JOUR-000[NNN].md`

**Cadence:** One entry per week (Decision 64). The journal entry covers all sessions across all days of that week — it is a consolidated weekly record, not a daily log. It is written during the End of Week ritual in `LES-MENTOR`.

**GitBook publication:** A journal entry is published to The Journey section only when the content is substantial, standalone, and genuinely reader-facing. Routine weeks without significant decisions or findings are committed to GitHub but not published to GitBook.

**Content scope:** Each entry covers what was built, what was learned, what decisions were made, and what changed in the project during that week. It is written for a reader who wants to understand the experience of building LES — not just the outputs, but the process and the thinking behind it.

**Current entries published:**

* `LES-JOUR-000001` — committed to GitHub and published to GitBook
* `LES-JOUR-000002` — committed to GitHub and published to GitBook

***

### Numbering Convention

Sequential documents (all types except ADRs) use a zero-padded six-digit number:

```
LES-ARCH-000001
LES-ARCH-000002
LES-RES-000001
LES-JOUR-000001
```

Numbers are assigned in creation order within each document type. Numbers are never reused. Where a document is superseded, the original document is retained and the superseding document carries the next available number, with a cross-reference to the predecessor.

***

### Versioning

Documents that undergo substantive revision carry a version suffix:

```
LES-ROAD-000001-v3.7
LES-PLAN-v2.2
```

Minor corrections that do not alter the substance of a document do not increment the version number. The version history of each document is maintained in its GitHub commit log.

***

### How Codes Appear Across Layers

| Layer        | Usage                                                                              |
| ------------ | ---------------------------------------------------------------------------------- |
| **GitHub**   | Document codes appear in filenames and commit messages                             |
| **GitBook**  | Document codes appear in page headings and cross-references                        |
| **LinkedIn** | Document codes may appear as footnotes referencing the authoritative GitBook entry |
| **Website**  | Document codes do not appear — the website is an executive summary layer only      |

***

### Chat Session Codes

In addition to document codes, LES uses a parallel system of chat session codes to identify the type and purpose of each Claude working session. These are not document identifiers — they are session classifiers.

| Chat Code              | Purpose                                                               |
| ---------------------- | --------------------------------------------------------------------- |
| `LES-MENTOR`           | Home base — progress reporting, context updates, next step assignment |
| `LES-ROADMAP`          | Master planning, phase reviews, roadmap updates                       |
| `LES-SETUP`            | Account creation, platform configuration, first-time setup            |
| `LES-LEARN-[topic]`    | Deep learning sessions                                                |
| `LES-BUILD-[module]`   | Building sessions                                                     |
| `LES-WEBSITE-[number]` | Website build and content sessions                                    |
| `LES-DOCS`             | GitBook and LinkedIn content creation                                 |
| `LES-RESEARCH`         | Academic research sessions                                            |
| `LES-REVIEW`           | Progress reviews and retrospectives                                   |

The chat session protocol is described in full on the [Session & Chat Protocol](https://claude.ai/chat/07-session-chat-protocol.md) page.

***

### Reference

Full decisions index: `LES-Master/docs/decisions/LES-DECISIONS-INDEX.md` ADR template: `LES-Master/docs/decisions/TEMPLATE.md`

* **GitHub:** [github.com/NikiDigitals](https://github.com/NikiDigitals)
* **Website:** [nikidigitals.com](https://nikidigitals.com/)
* NikiDigitals **LinkedIn:** [linkedin.com/company/niki-digitals](https://linkedin.com/company/niki-digitals)
* **Personal LinkedIn:** [linkedin.com/in/nmlangendam](https://linkedin.com/in/nmlangendam)


---

# 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/document-taxonomy-and-coding-system.md?ask=<question>
```

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.