# Portfolio Architecture

The Life Enterprise System (LES) is built and documented across four interconnected layers. Together, these four layers constitute the public portfolio of NikiDigitals. This page describes the architecture of that portfolio: what each layer is, who it is written for, what it contains, and how the layers connect.

The four-layer portfolio architecture was adopted as a formal project decision (Decision 4).

***

### Overview

| Layer | Name         | Platform | URL                                                                | Audience                                                  |
| ----- | ------------ | -------- | ------------------------------------------------------------------ | --------------------------------------------------------- |
| 1     | Executive    | Website  | [nikidigitals.com](https://nikidigitals.com)                       | General professional — recruiters, clients, collaborators |
| 2     | Thinking     | GitBook  | [nikidigitals.gitbook.io/les](https://nikidigitals.gitbook.io/les) | Architects, researchers, technical evaluators             |
| 3     | Evidence     | GitHub   | [github.com/NikiDigitals](https://github.com/NikiDigitals)         | Developers, engineers, technical evaluators               |
| 4     | Professional | LinkedIn | [linkedin.com/in/nmlangendam](https://linkedin.com/in/nmlangendam) | Professional network, thought leadership audience         |

Each layer operates independently and can be entered without prior exposure to the others. Each layer also links outward to each of the other three. No layer is a dead end.

***

### Layer 1 — Executive (Website)

**Platform:** WordPress, Astra theme, Elementor Free\
**URL:** [nikidigitals.com](https://nikidigitals.com)\
**Status:** Live — six pages built, styled, and responsive

The website is the executive layer. It communicates the NikiDigitals identity, the LES concept, and the career direction in terms accessible to a general professional audience. It does not contain technical depth — it points toward the GitBook for readers who want it.

**Pages:**

| Page              | Purpose                                          |
| ----------------- | ------------------------------------------------ |
| Home              | Identity, brand, and overview                    |
| LES — The Project | What LES is and why it exists                    |
| Portfolio         | Overview of the four portfolio layers with links |
| About             | Professional background and career direction     |
| Insights          | Published articles (first article pending)       |
| Contact           | Contact form with email delivery configured      |

**Design system:**\
Navy Night (`#0D1B2A`) and Circuit Blue (`#4A90B8`) on a Off-White (`#F4F7FA`) base. Syne Bold headings, DM Sans body. Dark bookend pattern: every page opens and closes with a Navy Night section.

The website speaks for NikiDigitals. LES appears as proof of work, not as the identity itself.

***

### Layer 2 — Thinking (GitBook)

**Platform:** GitBook\
**URL:** [nikidigitals.gitbook.io/les](https://nikidigitals.gitbook.io/les)\
**Status:** Infrastructure complete — content in active production

The GitBook is the thinking layer. It contains the documentation that sits below the executive surface: architectural decisions, module specifications, governance frameworks, research, and the learning record. It is written for a technically and academically informed reader.

The GitBook speaks for LES. NikiDigitals is the author attribution. The space is structured in twelve top-level sections, described in the How to Navigate page.

The GitBook is the authoritative public reference for every decision, design, and research output produced in the course of LES. GitHub holds the working documents; GitBook holds the finished, reader-facing versions.

***

### Layer 3 — Evidence (GitHub)

**Platform:** GitHub\
**Account:** [github.com/NikiDigitals](https://github.com/NikiDigitals)\
**Status:** 18 repositories created — LES-Master and NikiDigitals profile README public; all others private until content reaches a presentable standard

GitHub is the evidence layer. It holds code, infrastructure definitions, internal documents, working drafts, and version history. It is the technical audience layer — developers and engineers who want to inspect the implementation, not just read the documentation.

GitHub holds:

* Code and infrastructure files
* Internal documents — master context, templates, drafts in progress
* Working documentation — architecture notes, decisions in progress
* Everything that feeds into GitBook but has not yet reached a reader-facing standard

The GitHub profile (`NikiDigitals` repository) is a professionalised README containing the full portfolio table and identity.

The repository architecture is described in detail on the Repository Architecture page.

***

### Layer 4 — Professional (LinkedIn)

**Platform:** LinkedIn\
**Personal profile (primary):** [linkedin.com/in/nmlangendam](https://linkedin.com/in/nmlangendam)\
**Company page (secondary):** [linkedin.com/company/niki-digitals](https://linkedin.com/company/niki-digitals)\
**Status:** Active — first article pending

LinkedIn is the professional network layer. It distributes condensed insights and findings to a professional audience, linking back to the GitBook for depth. It also maintains the professional experience and certification record.

LinkedIn speaks for NikiDigitals. LES is the primary current topic.

The LinkedIn personal profile is the primary portfolio destination (Decision 48). The company page exists as a secondary brand presence.

***

### Cross-Layer Linking Architecture

Every layer must contain at least one exit point to each of the other three layers (Decision — cross-layer linking rule). This ensures that any reader, however they arrive, can navigate to the depth of content that serves them.

**Identity rules by layer:**

| Layer    | Speaks for   | LES appears as             |
| -------- | ------------ | -------------------------- |
| Website  | NikiDigitals | Proof of work              |
| GitBook  | LES          | NikiDigitals is the author |
| GitHub   | NikiDigitals | Repositories speak for LES |
| LinkedIn | NikiDigitals | Primary current topic      |

***

### Demo Environment

A fully isolated demo environment will be built on a separate Azure subscription in Phase 2 (Decision 44). A synthetic persona manages all public demonstration data. Production data is never exposed. The `LES-demo-data` repository manages synthetic data generation. Personal data is absent from all repositories and public documentation permanently.

***

### Related Pages

* How to Navigate
* Repository Architecture
* Project Overview
* **Website:** [nikidigitals.com](https://nikidigitals.com)
* **GitHub:** [github.com/NikiDigitals](https://github.com/NikiDigitals)
* **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/02-project-governance/portfolio-architecture.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.