kite-ai-flow

Kite AI — GitHub integration, presented as two linked pages.

• index.html — The architecture. The conceptual v0.5 model: one editing flow, GitHub-backed shipping, two-way sync, the entry doors, and the load-bearing decisions and drop-offs.
• storage.html — Storage & sync mental map. A single reasoning chain drawn as a top-to-bottom map: put .git on the sandbox's local SSD (persistent + backed up) to get git off EFS and gain durability → but two sandboxes are too complex to sync → so collapse to one server per team (die → restore from backup; new user → served from here) → which hands back two open problems: team-wide blast radius and burst load from hundreds of drafts at once.
• flow.html — The product flow. The real product, captured screen by screen from staging.kite.ai: the three "Start something now" doors, the Kite GitHub App connection, in-chat import with automatic repo resolution, the Next.js-only import gate, the Secret vault, and two-way repository sync on main. Screenshots live in assets/.
• report.html — Conversation consistency report. A severity-ranked review of the Slack transcript (slack.html): six disjoints where parallel Kite threads gave the same user contradictory answers — most sharply on whether a GitHub repo for the site exists — plus the shared-state root cause and five recommended fixes.

Open index.html in a browser and use the top-right nav to move between the pages.