Direct changes stay possible
A person with the right permission can change a Mart view or a Vault table directly, so the people you trust most can react to a business need at once.
Platform
Four eyes
Four eyes where you want them.
A change to the Mart, the Vault or a Sandbox view can start as a proposal. The platform checks it against the current state, and a person with the right permission applies it under their own name. For people this is a choice. For the AI Assistant it is the only way.
The foundation
Your team decides how much review it wants.
Review steps are optional for people, and your team decides where to use them. Software teams know the pattern as a pull request, and auditors as the four-eyes principle.
Review where you want it
A team can require that every Mart change goes through a Mart Plan, or keep drafts and plans as an option for the changes that need a second look.
Applied under a person's name
Whoever applies a change, directly or from a proposal, does it under their own name. The audit trail records who did it.
Not optional for the AI Assistant
In SchemaVortex the AI Assistant can only propose. It cannot publish, approve or discard. A person applies every change, and everything the assistant does is recorded in the AI Assistant log.
How it works
The four steps of a change
Every proposal goes through the same four steps. It does not matter if it is one view or a whole plan, or if a colleague or the AI Assistant wrote it.
Approver a person with the right permission, never the AI Assistant
1
Step 1
Propose
The change is written down as a Mart Plan, a Vault draft or a Sandbox draft. Nothing is applied yet.
2
Step 2
Check
The platform checks the proposal against the current Mart or Vault. A change made in the meantime shows up as a conflict. If the table's columns changed after a draft was written, the draft must be opened and saved again.
3
Step 3
Apply
A person with the right permission publishes or approves it under their own name.
4
Step 4
Record
The audit trail records who applied which change and when.
Three kinds of proposal
Vault draft
Mart Plan
Sandbox draft
Vault draft
A Vault Lifecycle Manager applies the draft.
When a Vault table is set up or changed, the change can be saved as a draft instead of applied right away. Any Vault Manager can write a draft. Only a Vault Lifecycle Manager can apply it, under their own name. If the table's columns changed after the draft was written, the draft must be opened and saved again before it can be applied.
How the Vault worksMart Plan
Several view changes are published together.
A Mart Plan groups new views, changed SQL and disabled views into one named set of changes. If a view changed in the meantime, this shows up as a conflict, which must be resolved before the plan can be published. Only a Mart Publisher can publish a plan. The AI Assistant can write a plan but cannot publish it.
How the AI Assistant is governedSandbox draft
The Sandbox view's owner reviews what the BI team proposes.
Business users keep their own logic in Sandbox views. The SQL is stored in the platform, not in a report, and the lakehouse serves it. A Sandbox Assistant can propose a change to any of these views as a draft. The draft does nothing until the owner approves it. The change is recorded once, under the person who approved it.
See a proposal reviewed and published.
A short live demo: the AI Assistant writes a Mart Plan, the plan is checked against the live Mart, and a person publishes it under their own name.