arcodange-org/factory
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(prd): integrate the second brain as the fleet's knowledge layer

Browse Source 
The PARA Obsidian vault (arcodange/SecondBrain — git-synced, sb.py
digest/inbox/gitea-ingest jobs on the hermes cron ticker, local Ornith
model, mcp-obsidian access) enters the PRD as a first-class component:
new T17 knowledge capture & retrieval fiche, knowledge-layer section in
the architecture (ERP = book of record, vault = context + institutional
memory, append-only idempotent deposits, trusted-but-stale retrieval),
hermes/Ornith recognized as the resident M4 runtime (D2 leaning, new D7
cluster<->vault access decision), foundation ledger row, diagram +
goals updated (mermaid revalidated, 231 links/anchors re-checked green).

Co-Authored-By: Claude Fable 5 <[email protected]>
This commit is contained in:
arcodange
2026-07-11 14:35:22 +02:00
co-authored by Claude Fable 5
parent 45418ff79c
commit 31158b05fa
7 changed files with 47 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
vibe/PRD/ai-back-office/challenges.md
+2 -2
View File
@@ -30,7 +30,7 @@ Each challenge states what breaks, the mitigation strategy, and the **residual**
## C4 — Data confidentiality & sovereignty
**Breaks:** sensitive financial/contractual content ends up in a cloud it shouldn't be in; credentials leak into prompts or journals.
**Strategy:** data classes (`public`, `internal`, `sensitive-financial`) with a class→tier ceiling ([routing policy](model-fleet.md#routing-policy)): sensitive stays local or EU-cloud; escalations carry minimized structured fields, not raw documents; secrets only via Vault/ENV (never in prompts, journals scrubbed); mailbox and bank scopes read-only by construction.
**Strategy:** data classes (`public`, `internal`, `sensitive-financial`) with a class→tier ceiling ([routing policy](model-fleet.md#routing-policy)): sensitive stays local or EU-cloud; escalations carry minimized structured fields, not raw documents; secrets only via Vault/ENV (never in prompts, journals scrubbed); mailbox and bank scopes read-only by construction. The second brain's own `--local` lane (Ornith via hermes — nothing leaves the Mac) already embodies this doctrine for vault content.
**Residual:** the human can explicitly widen a payload to the frontier tier when judgment says it's worth it — that judgment call is the point, not a leak.
## C5 — SLM capability ceiling on Pi hardware
@@ -66,7 +66,7 @@ Each challenge states what breaks, the mitigation strategy, and the **residual**
## C10 — Fleet maintenance burden & bus factor
**Breaks:** the fleet itself becomes the new admin burden — flaky atoms, stale prompts, undocumented behavior only its author (an LLM session) ever understood.
**Strategy:** everything in git under house conventions (skills documented, runbooks with `[AGENT]`/`[HUMAN]` markers, guidebook updated same-change); the **graduation path** (prototype skill → frozen deterministic script + tests) shrinks LLM surface over time; the explicit kill rule — *an atom that needs weekly babysitting gets demoted or deleted*; fleet net-value reviewed monthly (time saved vs. time spent tending).
**Strategy:** everything in git under house conventions (skills documented, runbooks with `[AGENT]`/`[HUMAN]` markers, guidebook updated same-change); the **graduation path** (prototype skill → frozen deterministic script + tests) shrinks LLM surface over time; vault deposits reuse the second brain's proven idempotent-frontmatter pattern (re-runs never duplicate); the explicit kill rule — *an atom that needs weekly babysitting gets demoted or deleted*; fleet net-value reviewed monthly (time saved vs. time spent tending).
**Residual:** single human operator remains the bus factor for the *company* — out of scope for this PRD, but the evidence packs and runbooks are written so a successor (or expert-comptable) could reconstruct the books.
## C11 — Laptop-tier availability