Authority Boundary Review
Make authority claims explicit and verify them against operational behavior rather than diagrams alone.
Workflow
- Inventory relevant stores, queues, files, APIs, caches, and projections.
- For each artifact, identify:
- what fact or bytes it owns
- who may write it
- who reads it and for what decision
- whether it is authoritative, derived, cached, archival, or proposed
- Trace create, update, delete, retry, replay, backfill, and reconciliation paths.
- Locate the ratified contract: code, schema, policy, ADR, configuration, or live provider state. Label unratified documents as proposals.
- Test disagreement scenarios. State which source wins, how conflicts surface, and whether repair is automatic, manual, or absent.
- Identify ambiguous dual writers, irreversible projections, missing version checks, or reads that bypass the declared authority.
- Separate documentation corrections from physical migrations, writer changes, backfills, or deployments.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Provide an authority matrix with Artifact, Owned fact, Class, Writer, Readers, Conflict rule, and Evidence. Follow it with confirmed boundaries, contradictions, proposed changes, and unresolved decisions.
Do not call a migration complete from schema or code changes alone. Writer cutover, historical data, reconciliation, deployment, and live reads require separate evidence.
Example
Synthetic example; not an observed client result.
Input: Orders are written to a ledger and copied into a search index.
Output: The ledger owns order state; the index is a projection. Repair stale search documents from the ledger unless an approved contract says otherwise.
Authority and projections
flowchart LR
Writer[Authorized writer] --> Store[Authoritative store]
Store --> Pipeline[Projection process]
Pipeline --> Index[Search index]
Pipeline --> Cache[Cache]
Store --> Reconcile[Reconciliation evidence]
Index --> Reconcile
Cache --> Reconcile
A projection can be rebuilt from its authority under an approved contract.
Neither a cache hit nor a matching total grants the projection write authority.
1---2name: review-data-authority3description: "Maps sources of truth when asked which database owns a value, which copies are projections, or who may write during migration; distinguishes proposed ownership from approved authority."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/review-data-authority7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-quality"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Authority Boundary Review1617Make authority claims explicit and verify them against operational behavior rather than diagrams alone.1819## Workflow20211. Inventory relevant stores, queues, files, APIs, caches, and projections.222. For each artifact, identify:23 - what fact or bytes it owns24 - who may write it25 - who reads it and for what decision26 - whether it is authoritative, derived, cached, archival, or proposed273. Trace create, update, delete, retry, replay, backfill, and reconciliation paths.284. Locate the ratified contract: code, schema, policy, ADR, configuration, or live provider state. Label unratified documents as proposals.295. Test disagreement scenarios. State which source wins, how conflicts surface, and whether repair is automatic, manual, or absent.306. Identify ambiguous dual writers, irreversible projections, missing version checks, or reads that bypass the declared authority.317. Separate documentation corrections from physical migrations, writer changes, backfills, or deployments.3233## Output3435Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3637Provide an authority matrix with `Artifact`, `Owned fact`, `Class`, `Writer`, `Readers`, `Conflict rule`, and `Evidence`. Follow it with confirmed boundaries, contradictions, proposed changes, and unresolved decisions.3839Do not call a migration complete from schema or code changes alone. Writer cutover, historical data, reconciliation, deployment, and live reads require separate evidence.4041## Example4243Synthetic example; not an observed client result.4445Input: Orders are written to a ledger and copied into a search index.4647Output: The ledger owns order state; the index is a projection. Repair stale search documents from the ledger unless an approved contract says otherwise.4849## Authority and projections5051```mermaid52flowchart LR53 Writer[Authorized writer] --> Store[Authoritative store]54 Store --> Pipeline[Projection process]55 Pipeline --> Index[Search index]56 Pipeline --> Cache[Cache]57 Store --> Reconcile[Reconciliation evidence]58 Index --> Reconcile59 Cache --> Reconcile60```6162A projection can be rebuilt from its authority under an approved contract.63Neither a cache hit nor a matching total grants the projection write authority.