Offline-first architecture
Billing, notices and what a lapse stops
ADR-0009 (tentative): billing happens at the quarter turnover and the business then continues or its paid services end; once billed it has until the next turnover to pay. Businesses approaching the profit threshold get two milestone notices with a non-binding estimate of next quarter's fee (the projected price plus a disclosed 15% buffer), only if they use the charged services. A lapse stops only paid features, updates and online extras; the software stays free and books, sales data and retained records are never locked, which the code tests. Grace and dispute lengths are drafts for a lawyer. Threshold detection is local and sends nothing.
Not decided
What to plan for
- Which services are charged is open
- Milestone levels and the buffer are drafts
- No payment flow exists
What the catalog lists
Planned items that match this topic (keyword match; read each as a pointer):
- Low-memory graceful handling L10N-0030
- Grace period & expiry behavior LIC-0009
- Offline licence semantics: updates_until (reserved, enforcement open) LIC-0044
- Fee lapse consequence (open) LIC-0051
- Illustration: about 100 businesses and about 1000 a month of cost (mock units) LIC-0074
- No margin on top of the cost: earnings come from adoption scale later LIC-0094
- Costs must stay bounded because the fee has no cushion LIC-0095
- Rainy-day reserve is a nominal optional cost line shown openly LIC-0102
- Related-party flag on cost lines (owner pay and affiliated companies) LIC-0096
- Related-party cost shown separately and labelled LIC-0097
- Documented basis for a related-party line (optional) LIC-0098
- Public donation lines on the cost page (optional) LIC-0099
Honesty note
Everything listed is a plan or a design principle. No app is released and nothing is audited or certified.