# ADR 000004 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 it, and publishes the journey as a professional body of work has multiple audiences with fundamentally different needs. A recruiter wants a clear narrative. A developer wants evidence. A researcher wants depth. A professional contact wants insight. No single platform serves all four.

## The Decision

The NikiDigitals portfolio is structured across four distinct layers. Each layer has one audience, one purpose, and one tone. Content is assigned to a layer before it is written — not after.

## The Four Layers

**The Executive Layer — NikiDigitals website**\
The first impression for anyone who does not know the project. It answers one question clearly: who is this and what are they building? It links outward to the layers that go deeper. It is updated rarely — only when there is something genuinely new to show.

**The Thinking Layer — GitBook**\
Where the reasoning lives. Every architectural decision, every research finding, every phase retrospective is documented here at the standard of a serious technical professional. A reader who spends an hour in GitBook should come away understanding not just what was built but why every significant choice was made. This is the layer that 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, commit history, and technical documentation written for a developer audience. GitHub does not tell the story — it shows the work. A technical evaluator who examines the repositories sees consistent structure, disciplined naming conventions, and a real system being built over real time.

**The Professional Layer — LinkedIn**\
The conversation layer. Articles that distil insights from the GitBook thinking layer into something readable in five minutes. Milestone announcements. Connections with professionals in finance systems, enterprise architecture, and technology. LinkedIn is updated when there is something genuinely worth saying — never on a schedule, never for the sake of activity.

## Why This Structure Works

The four layers are not independent — they are connected. The website points to GitBook for depth and GitHub for evidence. LinkedIn articles link back to GitBook entries. A reader who starts anywhere can navigate to the depth they want. The system is coherent without being repetitive.

It also enforces a discipline that matters over five years: not everything belongs everywhere. A working note belongs in GitHub. A finished decision belongs in GitBook. A milestone worth celebrating belongs on LinkedIn. The website shows the shape of the whole. Knowing which layer something belongs to before writing it makes the writing clearer and the portfolio stronger.


---

# 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-000004-portfolio-architecture-gitbook.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.