Data Authority and Migration Ratification
Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.
Workflow
- Map current authoritative stores, exact-byte custody, projections, writers, readers, and reconciliation paths.
- Define proposed target authority, allowed writers, read paths, transformations, conflict rules, and data contracts.
- Describe migration phases, compatibility, backfill, cutover, dual-operation limits, contraction, and cleanup.
- Specify reconciliation invariants, thresholds, sampling, quarantine, retry, and evidence ownership.
- Define rollback or roll-forward behavior for code, state, partially migrated data, and downstream consumers.
- Name the decision owner, consulted owners, required evidence, go or no-go gates, and ratification record.
- Keep status proposed until the named owner provides explicit ratification evidence.
Boundaries
- Do not declare a new authority, writer, migration, cutover, or production state ratified without owner evidence.
- Do not execute migrations, enable writes, or change production systems.
- Do not expose private schemas, topology, identities, or customer data in public outputs.
Output
Return Current authority, Proposed contract, Migration phases, Reconciliation, Rollback, Risks, Decision owner, Required evidence, and Status.
1---2name: data-authority-migration-ratification3description: Prepare a proposed data-authority and migration decision record covering owners, writers, readers, cutover, reconciliation, rollback, and acceptance. Use when decision owners need evidence to ratify or reject a migration contract; the skill cannot ratify it.4license: MIT5---67# Data Authority and Migration Ratification89Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.1011## Workflow12131. Map current authoritative stores, exact-byte custody, projections, writers, readers, and reconciliation paths.142. Define proposed target authority, allowed writers, read paths, transformations, conflict rules, and data contracts.153. Describe migration phases, compatibility, backfill, cutover, dual-operation limits, contraction, and cleanup.164. Specify reconciliation invariants, thresholds, sampling, quarantine, retry, and evidence ownership.175. Define rollback or roll-forward behavior for code, state, partially migrated data, and downstream consumers.186. Name the decision owner, consulted owners, required evidence, go or no-go gates, and ratification record.197. Keep status proposed until the named owner provides explicit ratification evidence.2021## Boundaries2223- Do not declare a new authority, writer, migration, cutover, or production state ratified without owner evidence.24- Do not execute migrations, enable writes, or change production systems.25- Do not expose private schemas, topology, identities, or customer data in public outputs.2627## Output2829Return Current authority, Proposed contract, Migration phases, Reconciliation, Rollback, Risks, Decision owner, Required evidence, and Status.30
JovaniPink