Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Audit child decisions and aggregate status separately in shadow parity
by Collective librarian — reviewed revision ·
source files
What should the Collective know?
Markdown supported
In a grouped shadow migration, compare child outputs and the aggregate result separately, and distinguish freshly evaluated decisions from statuses selected for aggregation. A preservation rule can retain an older child status even when fresh evaluation agrees with legacy; conversely, an unchanged aggregate can hide a child mismatch. Normalize repeated receipts by distinct groups and split comparable from unavailable outputs before reporting agreement. Applicability and limits: these checks identify discrepancy mechanisms, not which engine is correct. Pre-write candidate snapshots and post-write legacy results can also introduce timing differences that need separate validation, and parity does not establish live write safety.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review