Go-Dark

Overview

Go-Dark (Phase 12) happens on the go-dark date set on the wave during Wave Planning. It captures any changes in the source system since the initial ingestion and confirms the final data set is accurate before production migration. It involves all teams — Engineering pulls the fresh data, Implementation and the branch re-validate.

Fresh data pull

On the go-dark date, the ingestion team pulls fresh data for all entities from the source system, so the migration reflects the latest state rather than the state at initial ingestion.

Critical validations

Once the fresh data is in, re-check the data most likely to have changed:

• Owner AR balances — verify account-receivable balances match the source system.
• Delinquency statuses — confirm delinquency flags are current and accurate.
• Member roster — verify no new owners or tenants were added since the initial pull.
• Financial transactions — confirm recent transactions were captured.

Using the app on fresh data

The app supports this re-validation:

• Use the Review dashboards and the Financial Reconciliation panels in Validation to confirm the fresh data matches expectations.
• Re-run the Validation Wizard where needed. Validations completed before the fresh pull will show a stale indicator, prompting a re-check.

Completion

Go-Dark is complete when the fresh data is validated and the critical balances are reconciled. The final data set is then ready for Production Migration & Go-Live.

Planned: additional algorithmic go-dark validations built into the app to automate what remains manual — automated AR balance reconciliation, delinquency status verification, and delta detection between the initial and fresh data pulls.