File ORB-specific rate card (analog to AMS's #4804)

[JSONbored]

Problem

No ORB-specific pricing/rate-card issue exists — #4804 is confirmed 100% AMS/Rent-a-Loop-scoped (different milestone, different blocked-by chain, "Part of #4778"), with no relationship to ORB's own hosted-SaaS pricing at all. Decided: file the ORB analog now, as decision-scoping work, ahead of when a real free-tier user base exists to convert.

Area

Product decision, ORB Cloud Readiness cluster.

Proposal

Set an ORB-specific rate card informed by #4919/#4920's billing work and the now-decided crypto-native payment direction (matching AMS, per the maintainer's 2026-07-21 decision) — published alongside onboarding docs once ready.

Deliverables

• A published ORB rate card, once a real free-tier user base exists to convert (per the maintainer's own already-stated sequencing) — this issue holds the decision-scoping work now, doesn't force early publication.

Resources

• Pricing model & rate card #4804 (the AMS analog — same shape, different product, not merged with this)
• Integrate a billing SDK #4919, Design a quota/plan/subscription/invoice data model #4920 (ORB billing this rate card depends on)

Boundaries

Business decision — no numbers invented here, matches #4804's own boundary convention.

maintainer-only — business decision, not a build task.

[linear-code]

JSO-5424