The schema version recorded by the database after the migration.
Workflows · Database schema migrations
Migration 0421 waits for the database owner before it runs in production.
CC8.1 evidence for a schema change: the migration, the compatibility checks, the named approver and reason, and the schema version read back.
Example workflow. Execution requires a configured tool with provider permissions for this action; see the connection’s operation reference or bring your company tool to the demo.
Agent request
Apply migration 0421 to the production orders database
An incompatible schema change can block order writes or break the current application release.
- Identity
- migration-agent · Data platform
- Target
- production/orders
- Cost
- Recorded agent cost
- Evidence
- Migration diff, compatibility checks, and rollback statement
SOC 2 CC8.1
Sensitive: waits for a named approver.
The migration diff, the compatibility checks, the Database owner's reason, the schema version before and after, and the CC8.1 test it supports.
Policy decision
Production schema migrations require the Database owner.
Database owner
The action waits until this owner approves or denies it.
Tool call resumes
The migration tool applies the reviewed change and records its result.
Tool call stays blocked
The migration does not run and the current schema remains unchanged.
Execution order
The agent request stops before the connected tool runs.
- 01Migration agent requests the schema change
- 02Deixic checks the database, migration, evidence, and policy
- 03Database owner decides
- 04Connected database tool returns the migration result
- 05Deixic reads the result back and attaches the receipt to the test
Activity history keeps the request, decision, cost, and result.
Keep the procedure for the next request.
Keep the policy and decision history, save the steps and evidence as a skill, and test changes on real sessions; an approval stays specific to its request.