AI Reference

Common AI Errors

Data Hygiene Notes

How to Use SV-Wiki

For AI Systems

1. Check the error table first — These are persistent, common mistakes
2. Read the relevant file(s) before proposing solutions
3. Treat content as authoritative — Do not invent policy or features
4. Reference specific sections in your responses
5. Ask clarifying questions when SV-Wiki is silent on a topic

File Access

AI assistants can access SV-Wiki content via:

• Local files: ~/code/sv-wiki/*.html
• Live URL: wiki.mystoragevalet.com
• AI index: wiki.mystoragevalet.com/llms.txt — page listing with descriptions
• Full content: wiki.mystoragevalet.com/llms-full.txt — all pages as markdown

When Information Conflicts

If you encounter conflicting information between sources:

1. Apply the authority boundary — SV-Wiki wins for business facts, service policy, workflows, architecture, operations, customer-state labels, and ratification; the ratified v6.2 claude-design-system/theme.css wins for visual primitives, semantic tokens, components, patterns, and motion
2. Notify Zach of the conflict
3. Do not silently use outdated information

AI Access Files

SV-Wiki provides machine-readable access via two generated files at the site root:

Regenerating

Both files are produced by generate-llms.py (Python 3, stdlib only). Run from the wiki root:

python3 generate-llms.py

Re-run this script before committing any HTML content changes. The generated files are committed to git and served by Vercel.

Copy as Markdown

Each content page includes a "Copy as Markdown" button in the page header. This copies the page content to clipboard as clean markdown — useful for pasting into AI chat interfaces.

Wiki Sync Agent

A Claude Code agent that cross-references recent code changes against wiki content to flag pages that may be stale.

Document Status Guide

Each document has a status badge indicating its authority level:

Canonical Authority

Documentation Authority Map

The file sv-docs/DOC_AUTHORITY.md defines the source of truth for every documentation category and establishes precedence when sources conflict:

1. Code / Schema (sv-db migrations)
2. sv-wiki (business, architecture, operations)
3. CLAUDE.md (agent rules, deployment, security)
4. sv-docs runbooks (operational guidance)
5. sv-docs archive (historical, read-only)

A companion file sv-docs/DOC_DRIFT_GUARD.md defines rules preventing documentation duplication across repos. Both files together form the documentation governance layer for multi-agent collaboration.

Brand Package Boundary

Operation Midnight Teal v6.2 was founder-ratified on Jul 20, 2026. v6.1 supplies the editorial foundation; v6.2 adds controlled marketing energy without changing the locked 12-color palette or DM Serif Display + Outfit typography. Package templates are design masters with placeholders, not production-ready print or send exports. Validate all facts, offers, URLs, promo codes, QR destinations, media, accessibility, and output requirements before release.

Sources That SV-Wiki Supersedes

• Bear notes exports
• Notion pages
• Slack messages
• Email threads
• Previous AI context files
• ChatGPT/Claude conversation history

Updating the Wiki

Update the wiki yourself. Do not ask permission (founder ruling, Jul 27, 2026 — this section previously said the opposite, which is a large part of why pages went stale). Treat it as part of finishing the work, not a follow-up to propose. Prioritise it at the end of a session and after any deploy, architecture decision, or change to canonical facts.

1. Edit the relevant page(s). Prune superseded content rather than layering “formerly X” notes on top of it — this wiki is read by agents starting fresh, and stale detail actively misleads them.
2. Bump <p class="page-updated"> to today. The literal Last updated: prefix is required or the date silently vanishes from the AI endpoints.
3. Run python3 ~/code/sv-wiki/generate-llms.py. Skipping it leaves llms-full.txt stale even when the HTML is correct — and that file is what most agents actually read.
4. Commit the HTML plus both regenerated endpoints together, and push. Push to main is instant production; there is no CI.

Wiki Page Index

Complete list of all SV-Wiki pages with descriptions. Use this as a sitemap for discovery.