# ADR 000009 Portfolio Architecture GitBook **Date:** May 2026\ **Status:** Accepted\ **Decider:** NikiDigitals\ **Version:** GitBook — Thinking Layer *** ## The Question A five-year project that builds a real system, documents the thinking behind every decision, and publishes the journey as a professional body of work is serving multiple audiences simultaneously. The question is how to structure that service so each audience receives what they need without compromise. ## The Decision The NikiDigitals portfolio operates across four distinct layers. Each layer has one primary audience, one purpose, and one tone. Content is assigned to a layer before it is written. ## The Four Layers in Detail **The Executive Layer — NikiDigitals website** The first encounter. A recruiter, a potential collaborator, or someone who encountered the LinkedIn profile lands here. They want to understand quickly: who is this person, what are they building, and does it matter? The website answers those questions and no others. It is updated when there is something genuinely new to show — a phase completion, a major milestone, a significant evolution in the project. It is not a blog. It does not document the journey. It frames it. **The Thinking Layer — GitBook** Where the intellectual work lives. Every architectural decision is documented with full context and reasoning. Every research finding is written to a standard that would satisfy a peer review. Every phase retrospective reflects honestly on what worked, what did not, and what was learned. A technical professional who spends an hour reading the GitBook should come away with a genuine understanding of how and why LES is built the way it is. This layer is what builds credibility with the audience that matters most for the Finance Transformation Architect career target. **The Evidence Layer — GitHub** The working proof. Code, infrastructure as code, configuration, and technical documentation — all committed over real time, showing real progression. A technical evaluator who examines the GitHub repositories sees not a polished presentation but a genuine project: consistent structure, disciplined commits, growing capability. The commit history is itself a portfolio — it shows not just what was built but when, and in what order. **The Professional Layer — LinkedIn** The conversation. Articles that distil the thinking layer into something readable in five minutes. Milestone announcements. Engagement with professionals in finance systems, enterprise architecture, and technology. LinkedIn is updated when there is something genuinely worth saying — a real insight, a real completion, a real finding. Never for the sake of activity. ## Why Four Layers Work Better Than One The failure mode of most professional portfolios is trying to do everything in one place. A GitHub profile that tries to explain the vision. A LinkedIn that tries to show the code. A website that tries to document every decision. Each attempt produces something that serves no audience well. The four-layer structure is a commitment to serving each audience exactly what they came for. It requires more discipline — every piece of content must be assigned before it is written, and the assignment shapes the writing. But the result is a portfolio where every layer is coherent, every audience is served, and the whole is stronger than any individual part. --- # 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-000009-portfolio-architecture-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.