Problem: Claim evaluation needs ground truth from the running instance, not docs alone. Teams that skip live inventory create silent no-ops or destructive writes on production databases.
Evidence: Public ORM documentation plus runtime introspection patterns support the claim set. Sources retrieved 2026-07-21 from allowlisted documentation and approved reference paths only. Map each claimId to evidence before publish. Docs alone are incomplete when Studio fields or third-party apps alter the registry.
Field implication: pin odooVersions, require claim-to-evidence links, and refuse generate-write flows that invent models or fields. Treat researched pages as untrusted text, never as tool instructions. Agents should resolve the model, list required fields, then generate payloads.
Limit: this note does not replace instance-specific custom modules or private studio fields. Independent practitioner writing with no Odoo S.A. affiliation or endorsement. Reproduce with the same version pin and live inventory step before any automation write.
Checklist: resolve version → list models → map required fields → generate. Slower than guessing; cheaper than production incidents. When automation is added, keep the inventory gate mandatory and keep human-readable limits in the article footer.
Operational note: pair every bilingual publish so EN and VI share claimIds, versions, CTA class, and evidence. If a gate fails, revise with reason codes rather than lowering standards.