# ADR 000005 UK English GitBook **Date:** May 2026\ **Status:** Accepted\ **Decider:** NikiDigitals\ **Version:** GitBook — Thinking Layer *** ## The Decision All written output across every layer of the NikiDigitals portfolio — documentation, research, articles, code comments, commit messages — is written in UK English. This is a single, non-negotiable standard applied from the first word to the last. ## Why It Matters Consistency in language is not a minor preference. In a portfolio that will be read by professional and academic audiences over five years, inconsistency in spelling, terminology, and style signals a lack of discipline. A document that switches between "organisation" and "organization", or "analyse" and "analyze", tells the reader that standards are not maintained rigorously. That is precisely the wrong signal for a project building credibility in enterprise finance systems. UK English was chosen over US English for a straightforward reason: the European professional and academic context in which this portfolio operates — finance, enterprise systems, technology — uses UK English as its standard. The alignment is natural. The practical implication is simple: every tool, every editor, every spell-checker is set to UK English. Every session with Claude produces UK English output by default. Any future collaborator operates under the same standard. The consistency is total because partial consistency is no consistency at all. --- # 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/phase-0-foundation/adr-000005-uk-english-gitbook.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.