Skip to content

Method

Evidence model for the connected library

This existing coverage/merge section records source-side scope and remaining research. Its retained original content follows: Use separate dimensions rather than one “complete” flag: | Dimension | Suggested values | Meaning | |---|---|---| | Definition evidence | missing / name-only / source-definition / conflict | Is the identity and meaning established? | | Instruction evidence | missing / pointer / written-summary / demonstration-reviewed | What teaching material was actually reviewed? | | Source depth | index / synopsis / full-written / reviewed-media | What part of the source was accessed? | | Editorial review | pending / passed / revision-needed | Has the draft been checked? | | Coaching review | pending / passed / revision-needed | Has a qualified reviewer assessed instruction? | | Database reconciliation | unknown / matched / enriched / created / excluded / unresolved | What actually happened in the application? | These are proposed mappings to existing fields, not a requirement to migrate the schema. A performance report may confirm a named execution while leaving instructional evidence missing.

HOW TO DO IT

Evidence model for the connected library

This existing coverage/merge section records source-side scope and remaining research. Its retained original content follows: Use separate dimensions rather than one “complete” flag: | Dimension | Suggested values | Meaning | |---|---|---| | Definition evidence | missing / name-only / source-definition / conflict | Is the identity and meaning established? | | Instruction evidence | missing / pointer / written-summary / demonstration-reviewed | What teaching material was actually reviewed? | | Source depth | index / synopsis / full-written / reviewed-media | What part of the source was accessed? | | Editorial review | pending / passed / revision-needed | Has the draft been checked? | | Coaching review | pending / passed / revision-needed | Has a qualified reviewer assessed instruction? | | Database reconciliation | unknown / matched / enriched / created / excluded / unresolved | What actually happened in the application? | These are proposed mappings to existing fields, not a requirement to migrate the schema. A performance report may confirm a named execution while leaving instructional evidence missing.

Preparation and setting

Apply to the actual existing database in staging; a frozen source file is not a live-site audit.

Execution / application sequence

  1. Match each existing original locator to its live canonical ID.
  2. Compare description, exact lesson fields and evidence state.
  3. Resolve repeated source rows as enrichment rather than duplicate creation.
  4. Carry every unresolved queue item forward with a field-specific reason.
  5. Validate linked records and publication gates.
  6. 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.