Circle Thrice · System
Design Registry
Every discrete design carries a permanent ID — CT-family-number, e.g. CT-TS07. The number is an identity, not a rank: it is never reused or renumbered, so an ID means the same design forever — in this chat, with clients, in notes. This page is the ledger of record; open any listed page to see live ID badges and fidelity checks in place.
draft option under review
proposed awaiting Ivy's approval
locked chosen — must not change
superseded replaced, kept for the record
drift locked design changed — audit flag
two lock types: canon (built from ct-canon.js) · fingerprint (content snapshot)
Protocol
1
One ID per discrete design, assigned once. Each grouping on an exploration page gets the next free number in its family. IDs are permanent — deleting or reworking a design never frees its number.
2
Lock on your word. Say lock CT-TS07 — the design's content fingerprint is snapshotted as the baseline, status flips to locked, and it can no longer change silently. unlock CT-TS07 reverses it; superseding keeps the old ID on the books.
3
Audit on the page. Every registered page shows ID badges (click one to copy the ID) and a panel at bottom-right with counts. If a locked design's live fingerprint stops matching its baseline, its badge turns DRIFT — you'll see it before a client does. The Manifest button copies the page's full audit as JSON to paste to me.
4
Canon is locked by construction. Components generated from ct-canon.js (header, rail, tabs…) can't drift per-page because pages don't hand-author them — their ledger entries carry canon instead of a fingerprint.