Initial app scaffolding

Kicked off the PublishingPolicy build this week. The stack is Next.js 16 with Supabase on the backend and Tailwind CSS 4 for styling — same foundation we're using across several projects because it scales well and keeps infrastructure simple.

The design philosophy here is transparency-first. Every design decision is oriented around making publishing policies easy to create, easy to read, and easy to compare. No paywalls, no gated content. If the whole point is accountability, the tool itself has to be open.

The biggest early decision was how to structure the policy creation flow. Publishing policies vary wildly — from correction policies to disclosure requirements to editorial independence standards. Rather than a blank form, we went with a wizard approach: sector-specific templates that pre-populate relevant commitments, which publishers can then customize. 31 templates across 7 categories cover everything from investigative journalism to educational publishing.

The data model is organized around the three pillars — Identity, Commitments, and Accountability. Each sector template maps to specific commitments, and each commitment generates corresponding malpublish definitions. That linkage is the architectural core of the whole system.

Supabase handles auth and data storage, Vercel handles hosting and deploys. More to come as the wizard takes shape.