Phase 4 optional ecosystem gate

Commercial add-on machine

Credits, revenue share, complex add-on billing, and paid ecosystem upsells stay outside this phase.

Deferred surfaces

Required gates

Completed gates

Community

closed

Membership

closed

Deferral rule

The pricing blueprint says not to build a complex credits or add-ons machine too early.

Reopen checklist

1Keep add-on demand in pricing, support, and sales feedback until packaging is intentionally reopened.
2Avoid workflow access that depends on client-side add-on state.
3Require server-side entitlement checks before any paid extension can affect permissions.

Back to deferral boundary

Allowed now

Keep knowledge base, training, partner services, migration-pack readiness, and governed deeper intelligence visible as the useful Phase 4 ecosystem layer
Collect future demand signals through existing public-site contact, demo, pricing, and knowledge-base events
Document the deferred community and membership boundary so the roadmap does not imply a launch feature
Keep any future community analysis separate from tenant, owner, and operator workflow permissions

Still closed

Community forum or discussion feed
Membership tiers, subscriptions, or association benefits
Public developer marketplace
Vendor marketplace or partner discovery
Complex credits or commercial add-on engine

Audit rule

If reopened later, community or membership work must prove tenant isolation, explicit permissions, privacy posture, moderation ownership, billing boundaries, bilingual support, and auditability before any implementation starts.

Next controlled step

Do not open community or membership work until the blueprint is intentionally revised; the next roadmap step should return to production hardening, real customer feedback, or a new source-of-truth phase.