Implementation guide · v2.0.1 · 2026-09-26
Identity, access and controlled writes
Shared business knowledge does not imply identical visibility or write authority.
Where permissions are enforced
Use existing enterprise accounts, tenant boundaries and resource permissions when connecting. Check server-side visibility for queries, relationships, summaries, caches, logs and exports. Role switching in the demo illustrates different users’ views.
Controls for writes
Handle changes through draft, diff, validation, approval, commit and read-back. Approval applies to a specific plan and base version; confirm again when either changes. Check repeated submissions, version conflicts and recovery before use.
Authorize each business operation
Ontology maintenance, ERP order changes, payments, email and SQL/shell operations involve different interfaces and permissions. Confirm them for each task. Public interactive demos use simulated data and do not change production systems.