Studio Dispatch · Development record

Creator Rights Records, Phase One

· Creator Rights · Infrastructure

← Development record

Creator Rights went from prototype to merged in one day. It was built that day but not launched. The public opening came on July 29.

What merged

  • A registry prototype, then a locked publication lifecycle, so a record cannot jump from draft to public without passing through the states in between.
  • A Stripe publication boundary. Paid record issuance crosses a verified payment line, and nothing skips around it.
  • JSON records, VeilLink APIs, and a database schema with row-level security.
  • The first published records, including the TTRPG releases and Book One, which is marked as a licensed digital release.
  • A Creator Rights portal with QR assets for issued records, and server-side QR export with the SigilForge brand art embedded.

The licensing scope was reworked the same afternoon. The dual-layer model of Apache 2.0 for core code and the SigilForge Rights Framework for everything else was harmonized the next day.

Why say "built, not launched"

A system that describes who holds what rights should be precise about its own dates. July 27 is when the code merged. July 29 is when the public could use it.

Registry goes live Creator Rights