Skip to main content

Canonical Record Review Checklist

Use this as a human gate before publication.

Identity​

  • Canonical ID is stable and unique.
  • Alternative names and acronyms are captured.
  • Corridor boundaries are explicitly defined.
  • Included and excluded branches are justified.
  • Strategic level L1/L2/L3 is justified.

System representation​

  • Major geographic segments are present.
  • Functional links explain end-to-end movement.
  • Material modal transfers are represented.
  • Critical assets are linked.
  • Geometry precision is declared.

Flows and capacity​

  • Flow families are evidenced.
  • Observed vs projected flow values are separated.
  • Units and periods are explicit.
  • Nominal capacity is not presented as effective corridor capacity.
  • Missing data are disclosed.

Bottlenecks and dependencies​

  • Each bottleneck identifies the constrained function.
  • Material system effect is evidenced.
  • Dependencies identify consequence and substitutability.
  • Ownership/control are not conflated.

Projects​

  • Major projects have evidenced status.
  • Local asset change is explicit.
  • Functional-link effect is explicit.
  • Corridor-level effect is justified rather than assumed.
  • Counter-effects and adjacent constraints are documented.
  • Expected and observed impacts are separate.

Transformation​

  • Hypothesis is stated before conclusion.
  • At least two transformation dimensions show change.
  • At least two segments/links are affected.
  • Operational evidence exists.
  • Persistence or irreversible investment is demonstrated.
  • Alternative explanations are tested.
  • Invalidation conditions are listed.

Evidence​

  • Important statements have IDs.
  • Material statements link to evidence packages.
  • Contradictory evidence is preserved.
  • Promotional claims are labelled as such/expected.
  • Source locators permit rapid reinspection.

Editorial and publication​

  • First screen passes the thirty-second test.
  • Confidence is distinct from performance.
  • Observed/expected/scenario are visually distinguishable.
  • Public exports validate.
  • Internal/restricted data are absent from build.
  • Version history and last review date are visible.