# XV. Economics ### Part 15 — Economics and Sustainability #### 1. Public-Good First Economic Doctrine 1.1 **Purpose.** The economic model sustains an R\&D commons and enterprise-grade observatory platform without compromising neutrality, rights safeguards, or the non-executing perimeter. 1.2 **Firewall principle.** Revenue mechanisms shall not create:\ 1.2.1 pay-to-play governance influence;\ 1.2.2 procurement steering or implied endorsements;\ 1.2.3 conditional suppression or distortion of findings; or\ 1.2.4 regulatory perimeter confusion (i.e., treating platform outputs as compliance determinations or certifications). 1.3 **Separation of concerns.** The Guild’s economics are structured to ring-fence:\ 1.3.1 **public-good outputs** (open education, open reference implementations, public methods, and baseline benchmarks);\ 1.3.2 **enterprise sustainment** (commercial API access, private tenants, integration support, and reliability posture); and\ 1.3.3 **integrity functions** (review, red-team, safety gating, record discipline, and correction operations). 1.4 **No monetization of coercion.** The Guild shall not accept funding conditioned on:\ 1.4.1 removal of lawful research outputs;\ 1.4.2 selective enforcement or non-enforcement;\ 1.4.3 preferential benchmark parameters; or\ 1.4.4 access to Restricted materials not justified by role and need-to-know. *** #### 2. Contribution Recognition System 2.1 **Overview.** The Guild operates a Contribution Recognition System (CRS) that acknowledges work and sustains operations through a transparent combination of earned credits and purchased platform credits, while remaining strictly non-custodial and non-financial-instrument in character. 2.2 **Non-currency, non-security, non-transfer posture.** CRS units:\ 2.2.1 are not money, not a security, not a financial product;\ 2.2.2 are not transferable outside approved contribution contexts;\ 2.2.3 do not confer ownership, governance control, or profit rights; and\ 2.2.4 exist to meter access and recognize contribution under published rules. 2.3 **Three credit types.**\ 2.3.1 **vCredits (Validation Credits).** Earned through verification, peer review, red-team activity, benchmark integrity work, reproducibility replication, and safety gating.\ 2.3.2 **pCredits (Platform Credits).** Purchased for commercial or enterprise access to platform capabilities (e.g., API calls, private tenant features, advanced monitoring, integration capacity).\ 2.3.3 **eCredits (Ecosystem Credits).** Earned through open-source engineering, documentation, education content, accessibility improvements, ontology maintenance, and community support. 2.4 **Ledger posture.** CRS may be tracked in internal systems and auditable logs; it is not required to be on-chain and shall not use any mechanism that creates the appearance of tradable tokens. *** #### 3. Issuance, Earning, and Redemption Rules 3.1 **Issuance by rule.** Credit issuance shall be:\ 3.1.1 rule-based and published;\ 3.1.2 tied to verifiable work products and records;\ 3.1.3 reviewed for gaming risk; and\ 3.1.4 subject to correction and revocation where misrepresentation is discovered. 3.2 **Earning requirements.** Credits are earned only where:\ 3.2.1 a contribution is accepted through defined processes;\ 3.2.2 the contribution meets quality and safety gates;\ 3.2.3 provenance and authorship are documented; and\ 3.2.4 conflicts are disclosed and managed. 3.3 **Redemption and use.** Credits may be used for:\ 3.3.1 prioritized review queues (within neutrality constraints);\ 3.3.2 access to advanced tooling, compute quotas, or dataset tiers;\ 3.3.3 participation in replication sprints, clinics, and lab resources; and\ 3.3.4 training pathways or credential tracks as defined in education programs. 3.4 **No access-for-favor.** Credits shall not be redeemable for:\ 3.4.1 preferential benchmark outcomes;\ 3.4.2 suppression of findings;\ 3.4.3 procurement influence; or\ 3.4.4 private operator intelligence beyond lawful and permitted collection doctrine. 3.5 **Expiry and clawback.** The CRS shall maintain:\ 3.5.1 expiry schedules where necessary to reduce stockpiling and gaming;\ 3.5.2 clawback for fraud, plagiarism, or handling breaches; and\ 3.5.3 corrective adjustments published by record where system errors are discovered. *** #### 4. Subscription and Commercial Access Model 4.1 **Subscription logic.** Commercial subscriptions and enterprise agreements may provide:\ 4.1.1 API access tiers;\ 4.1.2 private tenant deployments;\ 4.1.3 integration interfaces (SIEM/SOAR/GRC/CI/CD);\ 4.1.4 support and reliability posture as disclosed; and\ 4.1.5 access to enterprise-grade Assurance & Evidence Pack pipelines where permitted. 4.2 **No certification.** Subscriptions do not confer certification, regulatory compliance determinations, or privileged standing in Guild governance. 4.3 **Procurement neutrality.** Commercial agreements shall:\ 4.3.1 avoid exclusivity requirements that impair neutrality;\ 4.3.2 avoid restrictions on publishing methods; and\ 4.3.3 prohibit “marketing claims” that imply endorsement or certification. 4.4 **Safety-first scaling.** Growth in commercial access shall not outrun:\ 4.4.1 review capacity;\ 4.4.2 red-team capacity;\ 4.4.3 correction operations; and\ 4.4.4 handling discipline. *** #### 5. Sponsorship, Grants, and Partner Funding 5.1 **Acceptable funding forms.** The Guild may accept:\ 5.1.1 unrestricted sponsorships;\ 5.1.2 restricted grants tied to public-good outputs (methods, education, open reference code);\ 5.1.3 in-kind support (compute, storage, datasets) subject to valuation rules and influence controls; and\ 5.1.4 research partnerships consistent with neutrality and the non-executing perimeter. 5.2 **Prohibited conditions.** Funding shall be rejected where it includes:\ 5.2.1 veto or editorial control over research results;\ 5.2.2 benchmark parameter influence;\ 5.2.3 “right to approve” publications;\ 5.2.4 coercive constraints on contestability or correction; or\ 5.2.5 requirements to target or disadvantage competitors. 5.3 **Influence caps.** The Guild shall enforce sponsor concentration controls including:\ 5.3.1 maximum share of annual budget from any single sponsor class;\ 5.3.2 diversification targets;\ 5.3.3 separation between sponsors and reviewers; and\ 5.3.4 publication of sponsor categories and totals at a minimum level of transparency consistent with handling and safety. 5.4 **Sponsor visibility and non-endorsement.** Sponsor recognition must:\ 5.4.1 avoid “powered by” or “approved by” phrasing that implies control;\ 5.4.2 be decoupled from benchmark results; and\ 5.4.3 be recorded with a non-endorsement notice. *** #### 6. Anti-Gaming, Fairness, and Integrity Controls 6.1 **No pay-to-play.** The Guild prohibits:\ 6.1.1 paid fast-tracking that bypasses safety gates;\ 6.1.2 purchasing governance influence;\ 6.1.3 purchasing Restricted access without role justification; and\ 6.1.4 purchasing favorable treatment in benchmarks or quality markings. 6.2 **Benchmark and dataset capture resistance.** Economic controls must support:\ 6.2.1 reviewer rotation;\ 6.2.2 separation of benchmark authorship from sponsor influence;\ 6.2.3 tamper evidence for benchmark parameter changes; and\ 6.2.4 published appeals and correction pathways. 6.3 **Equitable participation.** The CRS and subscription model shall preserve:\ 6.3.1 pathways for low-resource participants;\ 6.3.2 scholarship/waiver mechanisms for public-interest contributors; and\ 6.3.3 global inclusion measures (language, accessibility, time-zone-aware cadence). *** #### 7. Financial Governance and Transparency Minima 7.1 **Ring-fencing and purpose limitation.** Funds and resources must be tracked to support:\ 7.1.1 public-good outputs;\ 7.1.2 platform operations; and\ 7.1.3 integrity functions. 7.2 **Transparency minima.** The Guild shall publish, at minimum and subject to handling constraints:\ 7.2.1 pricing logic categories (not necessarily individual contracts);\ 7.2.2 credit issuance rules;\ 7.2.3 sponsor categories and aggregate totals;\ 7.2.4 high-level cost model (compute/storage/operations) and allocation logic; and\ 7.2.5 any material changes to the economics model via recorded amendment. 7.3 **Audit posture.** Financial operations shall be auditable in a manner consistent with:\ 7.3.1 record discipline;\ 7.3.2 correction and supersession; and\ 7.3.3 conflict and influence controls. *** #### 8. Termination, Transition, and Continuity 8.1 **Continuity of open outputs.** In any wind-down scenario, the Guild shall prioritize continuity of:\ 8.1.1 open-source reference implementations;\ 8.1.2 open education content; and\ 8.1.3 public methods and baseline benchmarks, subject to safety constraints. 8.2 **Non-reliance transition discipline.** Any discontinuation of services must include:\ 8.2.1 deprecation notices;\ 8.2.2 alternative access pathways where feasible; and\ 8.2.3 correction and archival pointers to avoid reliance traps. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.therisk.global/organization/cooperation/nexus-guilds/future-of-web/xv.-economics.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.