ADR-001 — Bootstrap: infra-vanos as the Knowledge-OS node of Prime Products Ltd

Revision note: originally written in Greek; translated to English per ADR-003 (content unchanged).

Status

accepted — 2026-07-02 (decided by: taranas)

Context

Prime Products Ltd is starting an AI transformation within the same framework TPL followed for its own. It needs a “second brain”: a single place where the company’s needs, its infrastructure, the decisions taken, and the project’s progress are recorded — so that humans and AI agents work from the same source of truth, and knowledge accumulates over time instead of scattering across emails, documents, and memories.

The model already exists, proven at TPL: Knowledge-OS repos (infra-okd, infra-hyperv, tpl-organisation) with an Obsidian vault, OKF-conformant frontmatter, the ADR/runbook/session/HANDOFF lifecycle, and agent-driven bookkeeping (Karpathy LLM-wiki principle: the agent does the bookkeeping, the human curates).

Decision

1. The infra-vanos repo is the central knowledge base of Prime Products Ltd. The repo root is an Obsidian vault; content = plain Markdown + YAML frontmatter.
2. We adopt the TPL federation conventions (master-vault/conventions.md): OKF-conformant frontmatter (additive superset), kebab-case names, one concept per file, ADR format, session-log format, HANDOFF format.
3. Structure: 01-Company, 02-Requirements, 03-Infrastructure, 06-Decisions, 07-Runbooks, _sessions, _templates, plans — with 04-Systems and 05-Processes reserved as slots, to be created when real content arrives. (The 06/07 numbering for Decisions/Runbooks follows the backoffice-vault scheme, leaving room for the intermediate slots.)
4. New concept types: requirement (REQ-NNN files in 02-Requirements/, lifecycle captured → validated → in-progress → delivered | dropped) and interview (capture-session notes). An allowed extension of the type vocabulary as a superset.
5. Frontmatter vault: vanos on every knowledge doc.
6. Project-repo profile: session logs live locally in _sessions/, HANDOFF.md at the root, refreshed at the end of every substantive session (vault-session skill + Stop hook backstop).
7. Secrets: 1Password only, referenced as op:// URIs — never plaintext in git. The dedicated 1Password vault for Prime Products secrets will be defined by a future ADR when the first credential is needed.

Consequences

• Every substantive piece of work leaves a trace: session log (what happened) + HANDOFF (where we are) + ADR (why it was decided). History is never rewritten — append-only.
• Knowledge is portable (OKF): usable by Obsidian, Onyx/RAG, or any OKF-aware tool, with no vendor lock-in.
• Phase 1 (requirements + infrastructure capture) has a working mechanism from day one — templates, register, lifecycle.
• Open (not decided here): (a) whether the vault joins the TPL Federation Map in master-vault or stays standalone — it is another company’s knowledge; (b) GitHub hosting org (resolved same-day: TPL-S-A — see HANDOFF); (c) language policy — see ADR-002, superseded by ADR-003 (English-only); (d) Onyx/context-lake ingestion and confidentiality tiers.