Business model
How source access and fees may work
The prototype does not implement payment. The intended model ties access and support to version records, access records, license terms, and Project Room records.
Principles
- Publishing and inspection should stay low-friction.
- Paid access should be attached to rights, version, and delivery records.
- Support fees should reflect setup, adaptation, and additional checks around a Build.
Section 1
Source access
A Build can become a source access listing when the User can inspect what they receive.
Source access
A User may receive a repository, ZIP, setup notes, and update terms tied to a specific BuildVersion.
Starter kits
Starter kits should explain what is reusable, what must be replaced, and which provider accounts are required.
Consultation-led Builds
Some agents or internal tools depend on customer data and permission design, so access may be scoped through a Project Room.
Section 2
Entitlement records
Entitlement is the product memory of who can access what.
Tie access to BuildVersion
The User's rights should refer to the version, license terms, delivery artifact, and support option in effect at the time.
Keep support separate
Setup help, provider configuration, extra checks, and custom changes should be room-scoped rather than implied by source access.
Record acceptance
Delivery and acceptance records matter more than a generic download confirmation.
Section 3
Future fees
Fees should match the source access, setup, and review value the Registry provides.
Access fee
A percentage fee may apply when a User receives source access or a starter kit through the Registry.
Project Room fee
A room fee may apply to setup, adaptation, additional checks, and acceptance records.
Pro plans
Builder and User plans may support analytics, private shelves, team review, verification workflows, and procurement records.
Guides
Product note
These guides are product copy, not legal terms. Source access, refund, access-control, and delivery policies should be separated before production implementation.