Reference library: rules

These rules apply to anyone working on the reference library: Vick, Claude, Codex or another agent. Read them before touching a page. If a rule gets in the way, ask Vick rather than work around it.

1. Where things live

The catalogue contains external inspiration and references. Authored Auspicious layouts, project mockups, component internals and personal palette artboards stay outside the searchable catalogue; existing files are retained. The images belong to other brands and are for internal reference. Vick decided on 22 October 2026 to put the library on the portal, open like /research/ but hidden from search engines (a noindex meta tag and an X-Robots-Tag header). The portal build copies the images in from the local folder at build time, so they never enter git. Anything committed to git stays in its history for good.

2. Identity

• Every image is identified by its Figma node id, written 1759:3431 in data and 1759-3431 in file names. Ids never change, and every fix attaches to one.
• Every record keeps its Figma link, its page and its section.
• Duplicates are linked to the first copy, never deleted. The record lists every place the image appears.

3. Tags

• Tags come only from vocab.json. Vick approved it on 21 October 2026, including light values "studio" and "none".
• The vision pass proposes tags. It never invents new words. manifest.py rejects any tag outside the vocabulary, and the run stops until it is remapped.
• Changing the vocabulary needs Vick's approval and a note in STATUS.md.
• For the Images 360 pass, Vick authorized suitable vocabulary additions on 22 October 2026. Document each addition and its reason in STATUS.md; do not force a space, element, material or packaging form when the image does not support it. This is scoped approval for that pass.
• Source brand: a legible label beats the Figma section name. If neither shows a brand, the source is "Unknown", never a guess.
• Rights are "reference only" unless Vick says otherwise.

4. Corrections

• A correction made by a person is stored separately from the machine tags (corrections.json, keyed by node id) and wins over them.
• Re-running a page never overwrites a person's correction.
• A broken export is re-rendered for that node alone and marked export: per-node render.

5. Scope and cleanup

• Work on one Figma page at a time. Claim it in progress.json (the run entry) before starting, keep it updated at every stage, and clear it when done (see keeping progress). Two agents never work on the same page at once.
• A session tidies only what it created: its own worktree, its scratch files, its own pages in the library. Older libraries in the repo (research explorer, mockups, ingredients, packaging, ofform) are not touched without Vick's say-so.
• Never delete a page's images or manifest without Vick's approval.

6. Figma

• Read-only. The library never changes the Figma file.
• No generate_image or other AI-credit tools without asking Vick first.

7. Publishing and handover

• Publish to the same artifact URL every time, so the link Vick has keeps working.
• Every publish or design update ends with the link in the message to Vick, and a line in the progress.json log with the date and what changed.
• Code goes on a claude/* or codex/* branch and a pull request. Vick merges.
• Merging to main deploys the library app (Vercel project studio-library, Git deploys). It has no custom domain yet, so there are no live-domain rules here; the Auspicious portal's rules no longer apply to the library.
• A catalogue change reaches the app only after npm run publish:data sends the new data to the image store, followed by a deploy.