docs(prd): D4 leaning — Qonto as the plateforme agréée (ex-PDP)
Operator direction: Qonto is the capital-deposit bank, a DGFiP-registered PA with e-invoicing included in every plan, and the fleet's richest existing API integration. POC-6 rewritten from shortlist to validation spike (reception + business-API pull + GED archival + 2027 e-reporting path for the KM export invoices); C12 residual now names the vendor- concentration trade-off; terminology refreshed PDP -> PA (renamed by the administration in July 2025); 2027-09 milestone clarified (e-reporting for export invoices; emission only if a French B2B client arrives). Co-Authored-By: Claude Fable 5 <[email protected]>
This commit is contained in:
@@ -149,7 +149,7 @@ To be settled by POC evidence, each closing with a short ADR:
|
||||
| D1 | Work queue | telegram-gateway's planned Postgres durable queue (**leaning** — already roadmapped, transactional, one less system) vs. flat files in git vs. Redis |
|
||||
| D2 | Orchestration runtime | Claude Agent SDK headless for cluster-triggered jobs + **hermes** for M4-side lanes (**leaning** — hermes already runs skills + cron there) vs. bespoke TS orchestrator (erp `test/` Deno codebase) vs. pure CronJobs + scripts |
|
||||
| D3 | KM monthly invoice firing | enable Dolibarr template auto-fire (`frequency>0`) vs. agent-fired via sandbox+promote (**leaning** — keeps the gate + mention audit in-line) |
|
||||
| D4 | PDP (e-invoicing platform) | shortlist + Dolibarr 22 module compatibility test on sandbox — **must close before 2026-09-01** ([C12](challenges.md#c12--e-invoicing-reform-unknowns)) |
|
||||
| D4 | PA — e-invoicing platform (*plateforme agréée*, ex-PDP) | **Leaning: Qonto** (operator direction, 2026-07 — the capital-deposit bank, DGFiP-registered PA, e-invoicing included in every plan, and the fleet's richest existing API integration); POC-6 validates reception + API pull before the ADR — **must close before 2026-09-01** ([C12](challenges.md#c12--e-invoicing-reform-unknowns)) |
|
||||
| D5 | OCR provider for scanned docs | Mistral OCR (EU cloud) vs. local vision model on M4 vs. Tesseract baseline |
|
||||
| D6 | Pi inference serving | llama.cpp server vs. Ollama on arm64, resource limits, node pinning ([C5](challenges.md#c5--slm-capability-ceiling-on-pi-hardware)) |
|
||||
| D7 | Cluster↔vault access | git clone/pull of the SecondBrain remote (**leaning** — the Gitea remote exists, offline-friendly, reviewable) vs. tunneled Obsidian REST API (M4-only today) vs. keeping vault access M4-exclusive |
|
||||
|
||||
Reference in New Issue
Block a user