diff --git a/vibe/PRD/ai-back-office/agent-architecture.md b/vibe/PRD/ai-back-office/agent-architecture.md
index 776170a..8dc654e 100644
--- a/vibe/PRD/ai-back-office/agent-architecture.md
+++ b/vibe/PRD/ai-back-office/agent-architecture.md
@@ -176,6 +176,7 @@ The integration contract ([T17](task-inventory.md#t17--knowledge-capture--retrie
 - **Capture:** fleet outputs worth remembering land as **append-only inbox/area notes with idempotent frontmatter** — the pattern the Gitea ingest already proves; human-authored notes are never edited in place.
 - **Retrieval:** context-hungry atoms query the vault and carry facts *with their note dates* — notes are **trusted-but-stale**: anything contradicting the ERP, or older than its subject's last change, triggers re-verification rather than belief.
 - **Rails reused, not rebuilt:** M4-side access is direct filesystem + `mcp-obsidian`; the weekly digest and the human's PARA filing ritual remain the curation loop; cluster-side access is open decision [D7](#open-decisions).
+- **Client dossiers — the junction of the agent families.** `01-Projects/Clients/<client>/` is where this fleet meets the sales chain (prospection → proposal → contract) and the future **delivery agents** working on client projects (the KM architecture notes already live there). Deposits are **agent-owned files** (e.g. a regenerated billing-snapshot note with `ai_generated` frontmatter), never edits of human notes; each family both feeds and reads the dossier — the back-office deposits billing state and contract facts and retrieves dunning tone; delivery agents deposit decisions, meeting notes and **new-business sightings** (contract clauses like the KM 4 % settlement make this a billing input) and retrieve contract scope and billing state. Client-project content is confidential by default — the vault's own routing doctrine applies (Ornith/local first).
 
 ## Open decisions
 
diff --git a/vibe/PRD/ai-back-office/task-inventory.md b/vibe/PRD/ai-back-office/task-inventory.md
index a3af24d..67314a6 100644
--- a/vibe/PRD/ai-back-office/task-inventory.md
+++ b/vibe/PRD/ai-back-office/task-inventory.md
@@ -250,5 +250,6 @@ Explicitly out of the current inventory; each becomes a task fiche when its trig
 - **Paper mail** — scan + ingest lane (low volume; needs a scanning habit before automation makes sense).
 - **Expense reports / personal-account visibility** — movements on the personal CCA (`fk_account=3`) are API-invisible; a manual CSV import lane or a banking-app export would open T07 coverage.
 - **Payroll & DSN** — dormant until the first salary is paid (see hub non-goals).
-- **Prospection/CRM admin** — the `prospection` repo exists; its admin loops (follow-ups, pipeline hygiene) can reuse this fleet's patterns later.
-- **Contract lifecycle** — renewal reminders and obligation extraction from client/supplier contracts (extraction atoms generalize naturally).
+- **Prospection/CRM admin** — the `prospection` repo exists (its own PRD, daily pipeline, Mode A/B scoring); its admin loops (follow-ups, pipeline hygiene) and the conversion bridge (a Mode-B prospect becoming a Dolibarr thirdparty + proposal through the gated write path) reuse this fleet's patterns later. Audited 2026-07-11: Dolibarr's propal/contrat/projet modules are enabled but empty — proposals and contracts live outside the ERP today.
+- **Contract lifecycle** — record contracts in the ERP (the KM retainer terms exist only as WIP JSON today: $5,500/mo = $2,500 net-30 + $3,000 deferred +3 months — the deferred schedule is the source of truth T06 dunning needs), renewal reminders, obligation extraction (the KM 4 % new-business clause), signed originals in the GED. Needs write-skill ops for contacts/contracts/products (same extension pattern as the GED-attach issue).
+- **Client delivery agents — the third family.** Agents working *on* client projects (the KM architecture notes in the vault are the embryo) share the [client dossiers](agent-architecture.md#knowledge-layer--the-second-brain) with this fleet: they deposit decisions, meeting notes (Granola → vault ingest is a natural `sb.py` job) and new-business sightings; they retrieve contract scope, contacts and billing state. Reuses T17 rails and the vault routing doctrine; REX at project close feeds `03-Resources` → prospection Mode B evidence → CMS case studies.