Customer Lifecycle

2026-04-23

Governed customer management on top of Odoo res.partner, layered across three progressive governance generations:

• V1 — Foundation. Service Accounts (SAs), memberships, role-based access.
• V2 — Stamps. x_sa_id / x_actor_id compatibility stamps on governed models.
• V3 — Association models. Dedicated assignment tables such as ov.sa_customer_assignment with full lifecycle history.

Start here

• Customer Lifecycle — End-to-End — the canonical walkthrough from bootstrap to archival, covering every stage, the data model, the API surface, and visibility policies.
• Agent · Start Here — a task-oriented entry point for agents and automations working in this repo.

Key concepts

Concept	Where it lives
SA hierarchy (global root → seed → branch)	SA Hierarchy
Customer creation & V3 dual-write	Stage 1 — Creation
Visibility policies (sa_wide, assigned_plus_unassigned, assigned_only)	Visibility Policy Reference
Membership revocation side-effects	Stage 5 — Revocation
Legacy backfill	Backfill
Roadmap for Phase 2+	Roadmap

Contributing

1. Edit the Markdown sources under docs/.
2. Record progressive architecture decisions in docs/adr/.
3. Keep stable lookup material (terminology, external refs) under docs/reference/.
4. Preview locally with mkdocs serve.

---

Small notes: progressive architecture decisions are tracked in Architecture Decision Records; stable lookup material lives under Reference.