Editorial hero image for the core concept of this post. How to match review files and posts without drift

How to match review files and posts without drift


Review systems fail quietly when feedback drifts onto the wrong post.

The fix is to treat every review as a record that must prove identity, not just a comment file.

1. Lock the identity fields

Use the same three fields everywhere: blog id, post number, and slug. A review without all three should be invalid.

2. Make mismatches fail early

When a slug changes, the review file must change too. If not, it should fail the build or be flagged before it attaches.

3. Move reviews with the post

When a post moves from studio to the real blog folder, its review file moves with it. If it stays behind, the link is broken.

Identity chain linking blog id, post id, slug, generated markdown, and review record

What to do first

Write the identity fields on every review and verify them before publishing.

  • blog id + post number + slug must match
  • review file name must match slug
  • review file moves with the post file