Odoo Demo Shield

Present an Odoo environment to a prospect without exposing customer data. Presentation layer only — never writes to Odoo.

Core Principles & Architecture Zero Database Modifications The extension operates exclusively at the Google Chrome DOM layer. It makes "no JSON-RPC/XML-RPC calls", invokes "no Odoo ORM methods" (`create`, `write`, `unlink`), and enforces a lint-level prohibition on `fetch`, `XMLHttpRequest`, and `innerHTML`. The Odoo server and PostgreSQL database remain completely untouched. Deterministic Entity Masking Data is masked consistently across the entire Odoo interface using a deterministic identity hash: `Identity Key = Hash(Model + Record ID + Category + Profile Seed)` For example, `res.partner:4821` is consistently displayed as "Apex Global Energy” across CRM Leads, Quotations, Invoices, Delivery Orders, and Partner Ledger—while maintaining internally consistent addresses, VAT numbers, phone numbers, and contact details. Odoo 19 Owl SPA & Input Protection The extension is designed for Odoo 19's dynamic Owl-based SPA architecture: DOM mutations are batched and tracked using `WeakSet` to prevent duplicate processing and infinite loops during re-renders. In editable form views, masked values are temporarily restored to their original values on `focusin` for legitimate editing. Values are automatically re-masked on `focusout`, ensuring synthetic masked data is never accidentally written back to Odoo. Financial Integrity Masking preserves the **financial structure and business relationships** of the data rather than randomly altering values. Where numerical transformation is required, revenue and COGS are scaled proportionally to preserve gross margins, while the standard Chart of Accounts and financial-report structure remain intact. Result: A realistic, internally consistent Odoo demo environment without modifying the Odoo database or server-side data.