Docs / readme
key-account-prime — Prime Products Ltd Knowledge Base (Second Brain)
Repo README — what this vault is, its structure, and where to start reading.
key-account-prime — Prime Products Ltd Knowledge Base (Second Brain)
The central knowledge base of Prime Products Ltd This is where the company’s needs, its infrastructure, the decisions taken, and the progress of its AI transformation are recorded — within the same framework TPL used for its own transformation (Knowledge-OS: Karpathy LLM-wiki + Google OKF + context lake).
Operating principle: the agent does the bookkeeping, the human curates. Every fact lives in exactly one file (single source of truth), one concept per file, with OKF-conformant frontmatter — so the knowledge is portable and equally usable by humans, Obsidian, and AI agents.
Quick facts
| Company | Prime Products Ltd |
| Repo role | Second brain — central knowledge, enriched over time |
| Format | Obsidian vault at the repo root, plain Markdown + YAML frontmatter |
| Framework | TPL Knowledge-OS conventions ($TPL_VAULTS_ROOT/master-vault/conventions.md) |
| Language | English-only content (ADR-003) |
| Phase | Program designed (08-Transformation) — discovery & requirements capture starting |
| Founded | 2026-07-02 (ADR-001) |
Structure
| Folder | Contents |
|---|---|
| 01-Company/ | Company profile, sites, organization, key people |
| 02-Requirements/ | Requirements capture — one file per need (REQ-NNN), with register |
| 03-Infrastructure/ | Infrastructure — network, servers, workstations, cloud, telephony |
04-Systems/ | (reserved — ERP, business apps; created when content arrives) |
05-Processes/ | (reserved — business processes) |
| 06-Decisions/ | Decisions (ADRs) — append-only, numbered |
| 07-Runbooks/ | Step-by-step procedures (as they emerge) |
| 08-Transformation/ | AI-first transformation program — strategy, charter, WBS, roadmap, department plans, technical blueprint, KB & Mission Control designs, AI portfolio, commercial stages (ADR-004) |
| _sessions/ | Session logs — what happened, when (append-only) |
| _templates/ | Templates: requirement, decision, interview |
| plans/ | Implementation plans (one file per plan) |
site/ | Mission Control (vanos.tpl.one) static-site generator — Astro, renders opt-in vault docs (ADR-005) |
| tools/ | Self-contained vault utilities — OKF Graph, the single-file interactive graph visualizer (ADR-007) |
| chat/ | Wiki-chat backend — Bedrock Opus 4.6 chat over the published vault, no retrieval DB (ADR-008) |
| planka/ | Planka task board — TPL-internal Kanban, OKD-hosted, seeded from HANDOFF/epic-board (ADR-014) |
| HANDOFF.md | Where we are right now — always-current snapshot |
| _index.md | Dashboard / entry point |
How we work
- Start from HANDOFF.md — it shows the current state and next steps.
- New need → new file in
02-Requirements/from the template + a row in the register. - New decision → new ADR in
06-Decisions/(append-only, never rewritten). - End of every substantive session → session log in
_sessions/+ HANDOFF.md refresh (the agent does this —vault-sessionskill, with a Stop hook as backstop). - Never plaintext credentials in tracked files — 1Password
op://references only.
What this repo is NOT
- Not TPL-internal knowledge — this is Prime Products Ltd’s knowledge (built with the TPL framework).
- Not a code repo — the value is in the content; four narrow exceptions:
site/, the Mission Control build tooling (ADR-005),tools/, self-contained vault utilities (ADR-007),chat/, the wiki-chat backend (ADR-008), andplanka/, the TPL-internal Kanban task board (ADR-014). - Not a document dump — structured, interlinked knowledge, one concept per file.