Architectural rules + design system + feed design for the mobile app. Gate system, verification levels, vote-state behavior, share system, VOTD overlay lifecycle, and the authoritative feed-order table. (Root file alongside CLAUDE.md.)

Canonical public-web voice (Rule #23) — third-person VOTD voice, loaded-term avoidance, headline discipline, the "voice"/"vote" framing, and where each rule applies. Vote-item copy voice is referenced out to policies/voice.md.

Canonical word choices, naming conventions, app-side type/enum reference, and prompt copy strings across all surfaces. The authority on what to call things. (Database schema now lives in schema.md.)

Feed module structure, statistical significance model, insight series taxonomy, data publishing rules by stage, and open strategic questions for investors and civic partners.

How source material attaches to a vote item — tiers (link, preview, file, carousel), data model, community research contributions, domain trust signals and blacklisting. (Absorbed the former add-research-rules stub.)

watchOS design intentions, architecture, and hard-won learnings — layout lessons, brand rules, complication behavior, and the WidgetKit refresh constraints.

Canonical app-store listing copy — names, subtitles, descriptions, and keyword sets for App Store / Play Store.

The V2 Postgres data model, rebuilt from live introspection — the publication-path spine (workshop_* → sourced_queue → master_votes_cal_v2 → votes), core-table columns, live enums, foreign keys, RLS posture, legacy/frozen tables, and the mobile verification/access model.

Signup-time identity verification (the entry gate) merged with vote integrity (what happens after the gate) — the 3-step ladder, cost analysis, scaling tiers, and the cryptographic-commitment path to binding-election-grade guarantees.

Trust and quality signal system for the admin — editorial signals on proposals, anomaly signals on users and voting patterns, user trust score model, and editorial workflow/assignment.

Canonical admin-app reference — the steady-state patterns established in the 2026-05-16 rebuild (react-query reads, optimistic mutations, realtime subscriptions, approve_draft RPC, v5 responsive layout) + the new-page checklist.

Older per-page wired/mock/stub reference, role model, environments, queue structure, editor actions. Consolidation into admin-architecture.md is parked until admin work settles (see backlog).

Current-state audit of the V2 pipeline — script inventory, what changed in the write-side cutover, and what's deprecated. The canonical "what's live now" curation reference.

The plan for the V2 publication path — how approved sourced_queue rows reach master_votes_cal_v2 and the app, plus the deferred follow-ons (tally trigger, mock_id→uuid, CDN caching).

Canonical reference for promote-v2-unified.mjs — per-geo capacity, gap-filling, fast-track cascade, and 25/25/50 tier calibration. The nightly sourced_queue → master_votes_cal_v2 promotion.

How search-result density feeds the engagement score — the SERP probe, locale handling, and scoring contribution.

How press coverage feeds scoring — the press probe, outlet/recency weighting, and the press-as-floor mechanic.

Step-by-step runbook for activating a new county — jurisdiction setup, source feeds, harvesters, and the go-live checklist.

Consolidation index for the scheduling + jurisdiction story — cadence, per-geo capacity, tier mix, and how it ties to the promoter and vote-URL work.

Tier-rollout principles — how Federal/State/Local tiers phase in and the coverage model. (Scoring mechanics within are historical; live scoring is in policies/scoring.md.)

The web-app rollout — v1 mobile-anchored, v2 web-native verification. Phasing and what ships at each stage.

Canonical, human-readable vote-URL scheme (jurisdiction-hierarchy slugs). Shipped 2026-05-31 — the structure behind votd.io/votes/<slug>.

Setup runbook for the Cloudflare Zero Trust gate in front of admin.votd.io.

Android/iOS build environment recipe + gotchas (Java 17, Node 22, typedRoutes flip, device authorization) and the open build bugs.

Retrieving and reading crash logs from a physical device — Xcode Console, pulling .ips files, common crashes + fixes, and the current watch-bridge state. (Absorbed the former crash skill.)

Canonical record of all domains, external accounts, Supabase projects, iOS bundle IDs, edge functions, Android build & Play distribution, and key infrastructure decisions.

Category strategy — what VOTD is, the "missing instrument" thesis, and how it's positioned relative to civic-tech.

Full competitive analysis — the consumer civic-app cohort AND the tiered gov-tech / polling / deliberation field. Why VOTD's exact cell has no incumbent.

Turnout evidence base — the defensible baseline, turnout by cycle type, and real Sacramento data points. (Competitive cut now lives in competitive-landscape.)

Pitch language + investor target map.

Advisor/team one-pager copy.

Community-facing one-pager copy.

Post-vote amplification strategy — turning tallies into civic signal and engagement.

Sacramento GTM + growth strategy.

Launch / signal / raise sequencing + go-no-go thresholds.

All-up launch execution plan — 4 tracks × 2-week sprints. Companion to the interactive launch tracker.

Legal-entity decisions (Delaware PBC, Atlas/Clerky).

Live backlog — the § Active section is canonical. Parked items carry enough context to pick up cold.

Structured, scored, prioritized front door to the backlog — readable index that links by code to each full write-up.

Rolling QA checklist — new build sections prepended at the top, carry-forward items tracked across builds.

Canonical FAQ source — generates PublicFAQ + InternalFAQ + in-app faqData. Stays at docs/ root because the FAQ build pipeline reads it.

The in-repo markdown front door to the docs library (the markdown sibling of this page), organized by the same folder structure.

Living reference for all color tokens — brand palette, warm neutral ramp, topic category colors, semantic tokens, and the rogue hardcoded value tracker.

All design explorations in one file — Design System, Vote Card, Feed Screen, Splash, Topic Palette, Share Poster/Panel/Personas/All.

Candidate colors for the Android system-nav strip below the white tab bar — three screens × seven palette candidates.

Rendered preview of the TestFlight invite landing in an iPhone 15 frame. Mirrors the production HTML from the Supabase invite edge function.

Early visual spec for the component + layout system — card shells, typography scale, spacing, color usage, interaction patterns.

Reusable instruction sets Claude loads before working on specific areas. All live in .claude/skills/ (consolidated June 2026).

Docs moved to archive/ in the June 2026 reorg, preserved in dated subfolders. Retired but recoverable.