A clean repository boundary is enough until dynamic data has a real shape. The useful question is not whether the idea sounds persuasive. It is whether it helps someone understand the work, make a decision, or complete a task with less friction.
What is happening
Adding tables before the records and workflows are understood creates migration cost without product value.
This tends to become visible at the boundary between the organization and the person encountering it for the first time. Internal familiarity hides effort that remains obvious to a customer, reader, applicant, or collaborator.
A practical response
Put content lookup behind a Python interface now. Replace its file-backed implementation with PostgreSQL when the data model and operations are known.
The aim is a smaller, clearer system: one source for the record, one visible hierarchy, and one next action that behaves as expected. That approach improves the immediate page and makes later application or database work easier to add without rebuilding the public surface.