Mirroring Repo Data into Notion

Overview

Git stays the source of truth; Notion is a derived, human-browsable mirror. The design problem is not the copy — it's making drift detectable and the derivation obvious, so nobody edits the mirror thinking it's authoritative.

Database vs page

• Database when the data is rows with attributes (an inventory: one row per item, columns for status/location/owner). You get filtering, sorting, per-row properties, and per-row updates on later syncs.
• Page when it's prose or a small table nobody will query. Cheaper, but every update is a rewrite.

If you'll ever ask "which rows have X?", it's a database.

Mark the mirror as derived

Every mirror gets, at the top (page) or in the database description:

1. "Derived from <repo path> — do not edit here; edit the source and re-sync."
2. The source commit hash (and date) the mirror was built from. This is the drift detector: git log -1 --format=%h -- <source file> vs the stamp answers "is this stale?" in one comparison.