Videos · 0:57 · 2026-09-26

Execution Layer for Odoo: AI writes with approvals and proof.

Execution Layer for Odoo: AI writes with approvals and proof 0:57 · sound on
Real Execution Layer screens and real MCP responses on a demo database (Odoo 19). One client reference is blurred.

An AI asks to change payment terms on 12 customers. The change waits for a person, runs only as approved, is read back from the database as a verified Action Receipt, and stays in the record history. A message to the team waits for a person to confirm the exact words, and a user switched to No access is refused at once.

Read the page: Execution Layer for Odoo

Transcript

  1. Execution Layer for Odoo: An AI is asking permission.
  2. Execution Layer: Nothing has happened yet. Request: update_records res.partner 12 customers payment term: 30 Days.
  3. A person approves, in Odoo: Bound to the exact change.
  4. Read back from the database: Verified. Request: update_records (identical arguments).
  5. The Action Receipt: Executed · Persisted · Verified · Recorded.
  6. Evidence · record history: Every change, before and after.
  7. It can message too: Nothing sends until a person confirms. Request: send_message #Sales updates "Reminder: launch checklist review at 3pm today.".
  8. Sent, and marked as AI: The words confirmed are the words sent.
  9. Every user as themselves: Switch one person off.
  10. The same key, seconds later: Refused at once. Request: count_records (Ana's existing key).
  11. AI that proves what it did. The enterprise MCP server for Odoo 19. nanti.ai/execution-layer Available now for Odoo 19 · USD 499 one-time · Odoo 20 support in progress · real product, demo data.

More videos

All videos