# Decision Log

*Section: Decision Log | Phase 0 | May 2026*

The Decision Log is the audit trail of LES. Every significant architectural, strategic, technology, and operational decision made in the course of the project is recorded here with its rationale and, where applicable, the alternatives considered.

Decisions are captured in Architecture Decision Records (ADRs) — one dated file per day, following the naming convention `ADR-YYYY-MM-DD.md`. All decisions made on a given day are grouped within that single file by category.

***

### Structure of an ADR File

Each file contains four sections: Architecture Decisions, Strategic Decisions, Technology Decisions, Operational Decisions. Each entry states what was decided and why. High-impact decisions also document alternatives considered and anticipated consequences.

Every decision carries a **GitBook: Yes/No** flag indicating whether it warrants publication here.

***

### Index and Templates

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

As of May 2026, 64 formal decisions have been recorded.

***

* [Governance Framework Overview](https://app.gitbook.com/o/tbne7ZtUlyqO49hsY3QC/s/Nb5M0j365A1RgeUSUy4w/02-project-governance/governance-framework-overview)
* [Document Taxonomy & Coding System](https://app.gitbook.com/o/tbne7ZtUlyqO49hsY3QC/s/Nb5M0j365A1RgeUSUy4w/00-introduction/document-taxonomy-and-coding-system)
* **GitHub:** [github.com/NikiDigitals](https://github.com/NikiDigitals)
* **Website:** [nikidigitals.com](https://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/03-architecture/decision-log.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.