RFC: Public Usage Profile — Zero Database Changes Proposal

[kilo-code-bot]

Summary

Architectural RFC proposing four options for building a public usage profile page that lets users showcase their Kilo usage stats — without any database schema changes or modifications to the hot write path (insertUsageAndMetadataWithBalanceUpdate).

• Option A: New endpoint on the existing abuse worker returning filtered getState() data.
• Option B: New Cloudflare Worker with a service binding to the abuse worker.
• Option C: New Cloudflare Worker with a direct AbuseTracker DO binding (RPC, no HTTP).
• Option D (recommended): Hybrid approach reading from both the AbuseTracker DO and existing Postgres tables (read-only, no schema changes).

Recommends a phased rollout: Phase 1 ships abuse-data-only profiles quickly (Option A), Phase 2 enriches with Postgres reads (Option D). Includes a data safety matrix, page structure mockup, mermaid data flow diagram, and open questions on caching, opt-in, and vanity URLs.

Requested in Slack by Brendan.

Verification

• Document renders correctly in GitHub Markdown preview (headers, tables, code blocks, mermaid diagram)
• No code changes — RFC document only

Visual Changes

N/A

Reviewer Notes

This is a discussion document, not an implementation PR. The goal is to align on an approach before writing code. Key decision points are captured in the "Open Questions" section. The bdo/public-profile-data branch has related exploratory work.

---

Built for Brendan by Kilo for Slack