Skip to content

Commercialization

Commercialization organizes market revenue, accepted contribution, share pool, and settlement events into a Project operating view.

Revenue Sources

SourceDescription
serviceProject-provided service
subscriptionRecurring subscription
data APIData interface
custom workBespoke work
licenseLicensing revenue
agent workflowAgent workflow service

Revenue facts come from settlement events. The page reads backend aggregation instead of recalculating operating state in the frontend.

Contribution Entitlements

Virtual shares represent internal contribution records and distribution views.

InputRole
accepted proofConfirms contribution
reviewer contributionAdds validation weight
share poolProvides budget
settlement eventProvides revenue fact

Current implementation uses these facts for Project accounting and commercialization status.

Direction Cards

Commercialization groups validation tasks into direction cards.

task intentTask purpose
direction keyDirection grouping
statusplanned / active / proving / validated
scoreDirection score

Status rules:

StatusCondition
plannedDirection exists
activeTask has been claimed
provingProof has been submitted
validatedProof has been accepted

Distribution Epoch

revenue.totalMinorRevenue pool amount
sharePool.shareMintedMinted virtual shares
acceptedTaskCountAccepted task count

When revenue and minted shares both exist, the distribution epoch moves to ready.

Implementation Boundary

The commercialization view displays internal Project contribution and revenue facts. Virtual shares, rewards, and distribution epochs are product accounting semantics.

Code Entry Points

  • apps/api/src/main/java/com/monopolyfun/modules/project/service/ProjectCommercializationService.java
  • apps/api/src/main/java/com/monopolyfun/modules/share/service/ProjectSharePoolService.java
  • apps/api/src/main/java/com/monopolyfun/modules/settlement/

Released under the MIT License.