Method
Colleague reconciliation template
HOW TO DO IT
Colleague reconciliation template
This existing coverage/merge section records source-side scope and remaining research. Its retained original content follows: Return one row per incoming record or candidate, not merely a “done” message: | Input batch / audit ID | Existing canonical ID | Outcome | Definition evidence | Instruction evidence | Conflict / open task | |---|---|---|---|---|---| | Example input | Unknown until application lookup | matched / enriched / created / unresolved / excluded | source-specific status | reviewed depth | concrete remaining issue | Record database IDs only from the application. “Unknown” is the correct value until lookup is performed. Keep a source reference on every carried-forward definition and preserve the original candidate even if excluded from public navigation.
Preparation and setting
Apply to the actual existing database in staging; a frozen source file is not a live-site audit.
Execution / application sequence
- Match each existing original locator to its live canonical ID.
- Compare description, exact lesson fields and evidence state.
- Resolve repeated source rows as enrichment rather than duplicate creation.
- Carry every unresolved queue item forward with a field-specific reason.
- Validate linked records and publication gates.
- Report imported drafts and remaining instruction gaps separately.
Learning and practice
Use GLOBAL_RECONCILIATION.json and the four package files to verify one branch at a time. Only mark an instruction complete when its actual execution pathway and review are present.
Errors, limits and corrections
Preservation, indexing and text presence are not technical completion. A successful import cannot close an instructional source gap.
Observable checks
Every matched card has a live ID, action and honest review state.
01
editorial review notes
Imported from the supplied editorial package; technical and coaching review remains required.