Skip to content

Simple vs Advanced mode

Every project runs in one of two modes. The mode determines how the ontology is managed, whether direct writes are allowed, and whether commits need approval. A fresh project defaults to Auto (Simple) so it works out of the box.

Mode	UI label	Ontology	Data writes (`save-context`)	Approvals
Auto	Simple	Self-organizing — created and extended automatically as data arrives	Writes nodes and relationships directly	None (frictionless)
Manual	Advanced	Explicit `create-ontology` proposal → commit (with an edit budget)	Not allowed — rejected	Commit may require human approval

In both modes, every call is scope-pinned, policy-checked, and audited. Auto mode removes approval friction, not governance.

When to use each

Simple (Auto) — the default, and the easiest way to start. Point data at Fabric and it builds and maintains the ontology for you; agents can read with query-context and write with save-context immediately. No schema to define.
Advanced (Manual) — for teams that want explicit control over the schema. Ontology changes go through a proposal → commit flow that can require human approval, and direct save-context writes are disabled in favor of that governed path.

How tool availability changes

Tool	Simple	Advanced
`query-context`	✅	✅
`docs`	✅	✅
`create-ontology`	✅ (auto-commit)	✅ (proposal → commit, may gate)
`save-context`	✅	❌ rejected

If your agent calls save-context in Advanced mode, the call is rejected — use the ontology flow instead.

Switching modes

Mode is a per-project setting and switching it changes gateway behavior live. Switching requires an admin role on the project. Administrators can change it in the console; the current mode is always visible in Simple Mode’s top bar.

Switching to Advanced does not retroactively change existing data — it changes how future ontology changes and writes are handled.