[AGENT] Design personal billing and organization credits

[BASIC-BIT]

[AGENT]

Summary

Design personal billing and a possible organization credit model before adding more personal-first product surfaces.

Product direction

Chronote currently has server/organization-oriented billing. Personal meetings, personal upload, desktop capture, web capture, and quick capture create a need for personal billing. There may also be a future model where organizations buy credits that authorized individuals can use across personal and server workflows.

Proposed scope

• Inventory current billing assumptions and guild-scoped data model constraints.
• Define personal plan concepts separately from server plans.
• Define whether personal usage and organization usage share one credit ledger or remain separate.
• Explore an organization credit/allowance model where admins can authorize users to consume organization credits.
• Decide how usage attribution works for personal meetings later shared to a server.
• Define Stripe product/price/customer/subscription impacts.
• Define portal UX for personal billing versus server billing.

Acceptance criteria

1. A billing model proposal exists for personal plans.
2. A separate recommendation exists for organization credits or allowances.
3. Usage attribution rules are defined for personal, server, shared, desktop, web, and mobile capture.
4. Stripe data model changes are identified.
5. Portal navigation distinguishes personal billing from server billing.
6. No implementation proceeds until the product/billing tradeoffs are explicitly decided.