Architectural rules and design decisions for the mobile app. Gate system, verification levels, vote state behavior by user type, share system, VOTD overlay lifecycle, and signup flow navigation.

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

Canonical word choices, naming conventions, and prompt copy strings across all surfaces. The authority on what to call things — authentication vs. verification, profile vs. account, and exact CTA strings per screen.

Specification for how source material is attached to a vote item — tiers (link, link preview, file, carousel), data model, community research contributions, domain trust signals and blacklisting.

Rules and UX spec for the community research contribution flow — link preview with OG fallback chain, file upload, pending state, and domain validation.

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

Supabase schema for both prototype and live environments — tables, RLS policies, key design decisions, voter verification state machine, feature access by verification level, and profiles field reference.

Editorial dashboard reference — role model across three growth phases, environment isolation, queue structure and item states, editor actions, and all outstanding decisions from the build sessions.

End-to-end pipeline for how votes get from real-world government agendas into the platform — two-pass automated sourcing, editorial review queue, jurisdiction-scoped review tiers, source trust management (whitelist/greylist/blacklist), and admin tooling requirements.

Canonical record of all domains, external accounts, Supabase projects, iOS bundle IDs, edge functions, and key infrastructure decisions with dates and rationale.

Comprehensive audit of the centralized gate system — every entry point, gate type, return-to behavior, and pending action replay. Covers VOTD overlay, vote-item, votes tab, profile, and feed.

Exact commands to run before every TestFlight archive. Covers normal builds, icon updates, and native dependency changes.

How to retrieve and read crash logs from a physical device — Xcode Console method, pulling .ips files, reading crash output, and a table of common crashes and their fixes.

Open iOS build bugs and session notes. Note: this file is scheduled for consolidation — the session diary content will be trimmed, leaving only the two open bugs.

Log of significant build milestones with what shipped in each. Tracks the progression from early prototypes through the centralized gate system and share panel redesign.

Rolling QA checklist. New build sections prepended at the top. Covers all changes since Build 24, with carry-forward items tracked across builds.

Intentionally deferred features — parked with enough context to pick up quickly when the time comes. Not forgotten, just not current priority.

Unique per-tester TestFlight invite system. Cloudflare Worker proxies branded URLs to Supabase edge function, which validates tokens, tracks clicks, and redirects to TestFlight. Includes leak detection and response playbook.

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

All design explorations in one file with sidebar navigation. Covers Design System, Vote Card, Feed Screen, Splash, Topic Palette, Share Poster, Share Panel, Share Personas, and Share All Comps.

Early visual spec for the full component and layout system — card shells, typography scale, spacing, color usage, and interaction patterns. Source of truth for feed rebuild work.

Reusable instruction sets that Claude loads before working on specific areas. Feed skill is mandatory before any feed engine work.

End-of-session checklist — commits and pushes all work, updates the QA punchlist, scans the conversation for undocumented decisions (domains, services, architecture calls, terminology), verifies infrastructure.md is current, and commits any doc updates. Prevents decisions from living only in the chat transcript.