Reverse spec drafted

Data Reconciliation

Non-destructive administrative scans and governed resolution of identity, ownership, membership and attribution exceptions.

Observed route/admin/settings/reconciliationFuture Spec 18 →

Current maturitySafe scan shell with no completed run

Evidence confidenceVerified

Last reviewedAugust 4, 2026

Visual evidenceDeferred during UI updates

Current-state summary

Data Reconciliation presents a non-destructive scan for identity, Membership, ownership, Team, attribution and passive-Entity conflicts. The latest status is Not run with zero findings and zero blocking constraints. It offers eleven categories and Open, Acknowledged, Resolved, Ignored and All review states. No scan was run and no resolution workflow was exercised.

Interface inventory

Anatomy and verified behavior

Verification states separate observed behavior from requirements or assumptions.

Element	Current behavior	Verification
Run summary	Not run, zero findings, zero blocking constraints and no completion time.	Verified live
Categories	Duplicate identity, missing profiles/auth links/Memberships/Workspaces, owner count/validity, cross-Workspace Team member, attribution and passive Entity candidates.	Verified live
Review state	Open, Acknowledged, Resolved, Ignored and All.	Verified live
Safety promise	Scans never merge or delete.	Verified UI copy

User journeys

Current flows

Resolve finding

Run read-only scan
Freeze run inputs and rules version
Open finding evidence
Choose governed resolution
Preview effects
Require approval for sensitive changes
Execute idempotently
Verify and audit

State model

Current and expected states

Not run

Current state.

Running

Not evidenced.

Completed

Not evidenced.

Finding open/acknowledged/resolved/ignored

Filters exist; no findings.

Product rules

Non-negotiable boundaries

Scans are read-only and repeatable.
Findings retain evidence and rule version.
Resolution is a separate authorized command.
Merge, ownership and attribution changes require preview and audit.
Ignored findings require reason and may re-open on changed evidence.

Dependencies

Spec 18Supabase identity and Workspace schemaAuditPermissionsMigration aliasesBackground jobs

Known current limitations · 3 mapped

What is missing, broken or unverified

Future Spec 18 owns closure →

No completed run.
No evidence drawer, resolution preview, approval or rollback was reviewed.
No run history or rules version is visible.

Future alignment

Required evolution

01Add immutable run history and rules versions.
02Add evidence-backed finding profiles and safe commands.
03Connect blocking constraints to migration readiness without auto-correction.

Current baseline

Acceptance record

A scan never mutates data.
Every correction is separately authorized and audited.
Run and finding histories remain durable.
Sensitive merges include preview and rollback strategy.

Reverse-spec completeness

Documentation coverage

The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.

Purpose and user outcome

Documented

Roles and access

Documented

Routes and entry points

Documented

Page and component anatomy

Documented

Fields and displayed data

Documented

Primary actions

Documented

Forms and validation

Documented

States and transitions

Documented

Empty, loading and error states

Documented

Responsive behavior

Partial

Accessibility behavior

Partial

Activity and audit events

Partial

Data sources and persistence

Documented

Notifications and automation

Partial

Known defects and limitations

Documented

Reusable component dependencies

Documented

Future-spec conflicts

Partial

Visual and repository evidence

Deferred

Acceptance of current baseline

Documented