Two days after the registry opened, the framework underneath it reached a state other people could actually use.
SFR 1.0
The SigilForge Rights Framework (SFR) governs everything in this project that is not core code: creative works, brand identity, Creator Rights Records, and the rights infrastructure itself. By July 31 it was paired with a guided workflow. You can start from a repository or a file, get draft records with license conflicts flagged for review rather than guessed at, compose the license, and leave with a Creator Dossier package and artifact hashes.
SFR records also became a distinct product, separate from the free public registry.
The licensing correction
The same morning, two records were fixed:
- VeilDaemon's own rights record was aligned with its Apache 2.0 core. The code is open. Everything that is not code falls under SFR.
- VeilForge's record had said MPL-2.0 and was corrected to proprietary. VeilForge is the studio's private local AI runtime, and its record now says so.
A rights registry that published the wrong license for its own tooling would be a strange first impression, so this was fixed before anyone relied on it.