Track and adjust revenue split parameters

[CShear]

Summary

Revenue split is set to 85% credits / 5% REGEN burn / 10% operations. These parameters should be monitored and adjusted based on actual costs and market conditions.

Key questions to revisit

• Is 10% ops sufficient? Stripe takes ~3%. At scale, server/email/API costs add up. Monitor actual costs vs ops budget.
• Is 5% burn meaningful? At $2.50/mo Seedling, 5% = $0.125/month for burns. Is this enough to create meaningful REGEN token pressure? May need to increase once ops costs are better understood.
• Should the split vary by tier? Higher tiers could allocate more to credits and less to ops (since ops costs are mostly fixed per subscriber).

Parameters in code

• REVENUE_SPLIT constant in src/services/pool.ts
• Referenced in tests (src/__tests__/pool.test.ts)
• Documented in ROADMAP.md, PLAN.md, analysis.md, pitch decks

When to revisit

• After 100 subscribers: first real cost data
• After 1,000 subscribers: at scale, ops percentage might be adjustable downward
• If REGEN token price changes significantly: burn percentage may need adjustment