Preparing the next view without exposing private workflow data.
Database engineering · Phased project
Turn unbounded document metadata into a queryable contract
A fictional records portal stores every property in one JSON column. Queries disagree about missing values, and malformed records make ordinary filters fail.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
33h + setup
Suggested stack
PostgreSQL · Prisma · TypeScript · JSON Schema
Recommended next step
Start with AMETA-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice relational/JSON boundaries, versioned validation and query semantics.
What the team gains
Review a data model that stays inspectable while allowing controlled variation.
Before you start
Create synthetic document metadata with malformed and legacy versions.
Use migrations and a local query API.
Delivery agreement
Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.