The Operator Model
Autonomous project management under a revenue-share model. A partnership, not employment — operators run validated technology stacks bounded by the Oxiverse Constitution.
This is how the model works. It is not a contract to sign — it is the operating structure Oxiverse follows when a project is handed to a team.
The Build Cycle
Oxiverse works in a 6-month Solo Sprint: a project goes from raw concept to a fully functional, validated product with stable architecture and initial traction. Once complete, the project is handed fully to the Operator team for operations, growth, and execution.
Operators are encouraged to invent new monetization strategies, provided they strictly adhere to the Oxiverse Constitution and the OCL License. The core SaaS remains free; monetization is built through premium plugins, Sovereign Commerce (affiliates), or Developer APIs.
Team Structure & Exclusivity
A team is composed of a maximum of five (5) full-time members, with one member designated as the "Leader" each month. Members must not hold other paid jobs; personal trading and investments are the only permitted exemptions.
The team is responsible for a minimum 5% revenue increase every six months.
Revenue Distribution
The split is calculated on Net Revenue = Gross Revenue minus Operating Costs (infrastructure, hosting, tooling, and any direct operational spend).
30% is retained by Oxiverse Systems LLP for core R&D and non-monetized services. The ORDP (Oxiverse Revenue Distribution Protocol) is then applied to the remaining 70% to distribute it among the team via peer voting.
The End-of-Month Cycle
Day 1 — AI summarizes commits; members report monthly targets vs. achievements.
Day 2 — Anonymous peer voting on a points-based portal. Members allocate points to others (max 30% to any one person); all allocated points must be used fully.
Day 3 — Allocation of base funds and performance bonuses. The member with the highest peer evaluation points is designated as the Leader for the following month.
Licensing & Intellectual Property
All Oxiverse services are governed by the Oxiverse Community License (OCL) Oxiverse Community License (OCL) v1.2. Core Oxiverse logic — including the cognitive architecture and core engines — must remain under OCL Oxiverse Community License (OCL) v1.2.
The core software remains the property of Oxiverse Systems LLP. Derivatives and extensions created by the team are subject to Section 6 of the OCL (Contributions).
Performance Checks & Termination
The 5% Rule — every six months, the team must show a 5% revenue increase over the prior period.
If the target is missed twice, the handoff is reopened and the team's access is revoked to allow a new team to manage the project.
A 10-day notice period is required for any member leaving the team to ensure operational continuity.
Any violation of the Constitution or OCL License results in immediate termination of the arrangement and cessation of all rights to the revenue split.
The Oxiverse Constitution
Every monetization path, feature update, and operational decision must respect these hard limits. Violation of any point terminates the handoff immediately.
- ✕No Display Advertising: No banner ads, native ads, video ads, or any impression-based monetization. Ever.
- ✕No User Data Sales: No selling search history, click data, profiles, or inferred interests.
- ✕No Behavioral Targeting: No cross-site tracking or building advertising profiles.
- ✕No Surveillance Capitalism: No third-party analytics (e.g., Google Analytics, Meta Pixel).
- ✕No Search Manipulation: No paid placements or sponsored results masquerading as organic.
- ✕No Dark Patterns: No tricks to extract consent or nag screens for monetization.
- ✕No Venture Capture: Oxiverse Systems LLP-controlled; no investor pressure to pivot to surveillance.
- ✕No AI Training on User Data: No training models on user queries without explicit, revocable opt-in.