Ecosystem Product and Sustainability Strategy¶
Status: Strategic commercial and community boundary; does not change current licensing or create paid services.
Durable Product Boundary¶
| Offering | Scope |
|---|---|
| Open | Forgevena local client, ForgeRegistry protocol and package format, local registry, resolver, SDK, core trust verification, offline workflows, and export. |
| Enterprise | Private registries, approvals, compliance packs, organization policy, fleet governance, enterprise integrations, support, and long-term maintenance. |
| Managed | Optional hosted ForgeHub, managed registries, publisher operations, fleet services, support, and explicitly consented analytics. |
The open client remains useful, private, complete, and offline-capable. Export and federation prevent hosted lock-in.
Prohibited Monetization¶
- Mandatory accounts, telemetry, or cloud dependencies.
- Surveillance advertising or sale of behavioral data.
- Hidden paid placement or payment-influenced trust scores.
- Artificial degradation of the local client.
- Captive package formats or non-portable policy and evidence.
Clearly labelled sponsorship may fund ecosystem operations but cannot alter organic ranking, moderation, certification, or security evidence.
Community Governance¶
Registry and marketplace rules are public. Namespace, moderation, appeals, ownership transfer, vulnerability response, and deprecation processes have accountable owners and published service targets. Major protocol changes use public RFCs and interoperability evidence.
Operating Economics¶
Track registry storage and bandwidth, signing and scanning, moderation, support, compatibility testing, mirrors, incident response, documentation, and maintainer time. Pricing should align with optional organizational value rather than restricting open local operation.
Maintainer Sustainability¶
Measure bus factor, ownership gaps, review load, release duty, support burden, incident duty, and succession readiness. Critical packages require transfer and escrow plans. Automation reduces repetitive labor but does not hide decision accountability.
Success Metrics¶
- Open adoption and task success without an account.
- Enterprise renewal based on governance and support value.
- Managed-service reliability without local-client dependency.
- Maintainer load, review latency, incident response, compatibility freshness, and ecosystem trust.
- Registry portability, export success, mirror diversity, and air-gap adoption.
Review Rules¶
Commercial boundaries are reviewed annually against the Platform Constitution. Any telemetry, ranking, certification, or hosted-boundary change requires an RFC, privacy review, threat model, public explanation, and rollback path.