DP17 - Financial Sustainability
Patches and comments are scoped to the whole document family, not to a single revision. When you open a revision, highlights show what still applies to that revision body; anything anchored to text a later revision removed is listed as needing re-anchoring, and anything that can no longer be merged at all is marked obsolete. See all patches.
Comparing Revision 00 (original) with Revision 01. Struck-through text was removed; highlighted text was added.
# DP17 – Financial Sustainability
*Transparent, non-extractive funding that keeps governance, safety, and maintenance alive over time*
<!-- dp-local-version: 1.0 | standardized: 2026-07-27 -->
## 1. Purpose of This Draft
This financial system layer ensures that sustainability is not just declared, but structurally maintained across time, incentives, and scale.
## 6. Funding Models
DP17 does not prescribe a funding model. It requires that whichever models are used be disclosed, evaluated against system values, and combined so that no single dependency can quietly capture or collapse the system.
### 6.1 Model catalogue and tradeoffs
- **Direct payment (subscriptions, usage fees):** clearest alignment between payer and beneficiary; risks exclusion and paywalled participation - **Membership and cooperative dues:** durable and governance-aligned; risks under-provisioning relative to infrastructure cost - **Grants and philanthropy:** enables public-interest work; risks episodic funding and donor priority drift (3.2) - **Protocol, zone, or marketplace fees:** scales with activity; risks rent extraction if unchecked (DP6) - **Commercial services and support:** funds maintenance from those who capture most value; risks two-tier quality - **Sponsorship and underwriting:** flexible; requires disclosure boundaries and non-influence guarantees - **Commons funding (matching, quadratic, retroactive rewards):** funds shared infrastructure; risks popularity bias over criticality - **Endowment and reserve income:** stabilizes maintenance; requires transparent stewardship and drawdown rules (5.7) - **In-kind and institutional hosting:** lowers cost; creates dependency that must be disclosed as a risk
Failure mode: **model opacity**, where participants cannot tell which of these actually pays for the system.
### 6.2 Selection criteria
Model choice is evaluated against behavioral consequence, not revenue alone: whether the model rewards degradation of trust or agency, whether it funds non-visible assurance work, whether it concentrates control, whether it survives a downturn, and whether it is legible to the people it depends on (5.1, 5.3).
Failure mode: **revenue-first selection**, where behavioral consequences are assessed after commitments are made.
### 6.3 Portfolio construction
Sustainability comes from blended, deliberately structured funding: a stable base for maintenance and assurance, variable revenue for growth, reserves for shocks, and declared concentration limits per source (5.5, 5.7).
Failure mode: **accidental portfolio**, where the mix is the residue of opportunity rather than a design choice.
### 6.4 Contributor and maintainer compensation
Funding models must account for the people who sustain the system: maintainers, moderators, stewards, translators, and support roles, with visible compensation pathways rather than reliance on volunteer surplus (5.4, DP20).
Failure mode: **volunteer subsidy**, where core infrastructure depends on uncompensated labor until it fails.
### 6.5 Disallowed and constrained models
Some models are incompatible with the meta-layer's stated values: surveillance advertising, undisclosed data brokerage, dark-pattern conversion funnels, and revenue that grows as safety or agency declines (5.9, DP4).
Failure mode: **boundary laundering**, where prohibited models re-enter through partners, intermediaries, or exceptions.
### 6.6 Transition and wind-down planning
Funding models change. Each model declares how a transition would be handled: notice periods, service continuity, data portability, and honest relabeling of commitments that depended on it (DP16).
Failure mode: **cliff dependency**, where the end of one funding source ends the system.
## 7. Token Ecosystems
Token mechanisms are permitted but not privileged. DP17 treats them as one financial instrument among many, subject to stricter disclosure because their failure modes are fast, reflexive, and difficult to reverse.
### 7.1 Utility grounding
Any token must have a defined function in the system beyond price appreciation: access, coordination, contribution accounting, resource metering, or settlement. Function precedes issuance.
Failure mode: **function retrofitting**, where utility is invented after distribution to justify existence (3.7).
### 7.2 Governance separation
Financial holding must not silently convert into governance authority. Where tokens inform governance, DP17 requires caps, delegation limits, reputation or contribution weighting, and protected decisions that capital cannot override (DP3, DP12).
Failure mode: **plutocratic drift**, where legitimacy tracks holdings rather than participation.
### 7.3 Allocation and vesting disclosure
Initial allocations, treasury share, team and investor portions, vesting schedules, unlock cliffs, and incentive emissions are published before participants take on exposure.
Failure mode: **hidden overhang**, where undisclosed unlocks transfer value away from later participants.
### 7.4 Treasury transparency and constraints
Treasury holdings, denomination and volatility exposure, runway, allocation policy, and reallocation authority are visible and bounded, with assurance budgets ring-fenced from market conditions (5.11.2, Section 9).
Failure mode: **treasury opacity**, where reserves are claimed but neither verifiable nor constrained.
### 7.5 Speculation containment
Systems limit reflexive dynamics that convert price movement into product direction: no incentive programs that reward volume without utility, no roadmap commitments contingent on token price, and explicit separation between market communications and roadmap claims (DP16).
Failure mode: **price-driven roadmapping**, where market attention sets engineering priorities.
### 7.6 Exit, redemption, and continuity
Participants must understand what the instrument entitles them to, what it does not, how to exit, and what happens to their access, contributions, and records if the token mechanism is wound down.
Failure mode: **trapped participation**, where exit costs are discovered only under stress.
### 7.7 Compliance and jurisdictional posture
Regulatory classification, jurisdictional constraints, tax treatment, and consumer protection obligations are addressed explicitly rather than deferred, including how obligations differ across participating regions.
Failure mode: **regulatory improvisation**, where compliance risk is transferred to participants.
### 7.8 Non-token alternatives
Where a token adds financial risk without functional necessity, DP17 expects the simpler mechanism. Credits, fees, memberships, and pooled funds are legitimate and often preferable answers to the same coordination problem.
Failure mode: **instrument inflation**, where tokenization is adopted for fundraising narrative rather than system need.
## 6.8. Governance, Accountability, and Agency Surfaces
DP17 requires that financial signals are not only visible but **actionable, contestable, and enforceable** within governance (DP3, DP8).
- **non-actionable transparency** (visible but no leverage) - **accountability gaps** (no actor responsible for correction) - **governance capture** (funding control overrides community decisions)
## 7.9. Incentives and Power Analysis
Financial systems create and amplify power. DP17 addresses how incentives **distort behavior under pressure** and how to realign them with system integrity (DP9).
- **incentive inversion** (harmful behavior is profitable) - **credibility arbitrage** (short-term gains from inflated claims) - **capture dynamics** (decision power tracks capital rather than legitimacy)
## 8.10. Community Signals Informing DP17
Community signals are not just sentiment; they are **early indicators of financial misalignment and coordination risk**. DP17 treats these signals as inputs to system design and ongoing monitoring.
Observed signals and implications:
- **Concern about extractive monetization** → signals hidden revenue dependencies; requires clearer revenue classification and disclosure (5.1, 5.11.3)
- **Demand for fair compensation** → indicates gaps in value distribution; requires explicit allocation policies and contributor compensation pathways (5.2, 5.6)
- **Frustration with unstable funding cycles** → indicates weak reserves and diversification; requires contingency planning and runway visibility (5.5, 5.7)
- **Desire for community-controlled resources** → indicates legitimacy gaps; requires participatory budgeting and governance linkage (Section 6)8)
- **Skepticism of “free” services** → indicates perceived hidden costs; requires explicit mapping from revenue to behavior (5.1, 7)9)
- **Concern about safety underfunding** → indicates risk externalization; requires ring-fenced budgets for assurance (5.4, 7)9)
Operationalization:
- Convert recurring signals into **metrics** (e.g., % budget to maintenance, % revenue from non-extractive sources)
- Attach **confidence ratings** to funding streams based on signal alignment (Section 6)8)
- Feed signals into **governance triggers** (e.g., review when safety budget falls below threshold)
Failure modes:
- **signal neglect** (warnings ignored until failure) - **performative response** (surface-level changes without structural correction)
## 9.11. Non-Goals and Explicit Boundaries
DP17 does not prescribe a single economic ideology or eliminate markets. It defines **hard boundaries on misleading or harmful financial behavior** in the meta-layer.
- **methodology masking** (jargon obscures lack of commitment) - **selective disclosure** (only favorable financial information is shown) - **narrative protection** (truth suppressed to maintain perception)
## 10.12. Minimum DP17 Alignment (Non-Normative) (Non-Normative)
Minimum alignment defines the threshold at which financial signals are **reliable enough to coordinate real work**. Below this threshold, systems may publish numbers but do not provide trustworthy sustainability.
Systems that omit binding, allocation visibility, or change memory SHOULD NOT be considered aligned with DP17.
## 11.13. Open Questions and Future Work
DP17 requires further work to standardize how financial integrity is measured and enforced across diverse contexts.
These should be explored through ML-Drafts, pilots, and comparative implementations.
## 12.14. Relationship to Other Desirable Properties
DP17 is a cross-cutting layer that conditions whether other DPs remain viable over time.
- **DP6 (Commerce):** Defines revenue mechanisms; DP17 ensures those mechanisms are transparent and non-extractive. - **DP9 (Incentives):** Aligns economic signals with desired behaviors; DP17 verifies that alignment holds under pressure. - **DP3 (Governance):** Requires budget authority and visibility to make legitimate decisions. - **DP15 (Security & Provenance):** Security work must be funded and evidenced; DP17 ensures it is not starved. - **DP16 (Roadmaps):** Commitments must match funding reality; DP17 binds milestones to resources. - **DP20 (Ownership & Surplus):** Determines how value returns to communities; DP17 ensures flows are visible and fair.
If DP17 fails, other DPs degrade into promises without resources.
## 13.15. Foresight and Failure Design
DP17 assumes systems will face **financial stress, growth pressure, and adversarial manipulation**. The goal is not to avoid failure, but to make it **visible, bounded, and repairable**.
A mature system treats financial failure as a **learning loop**, not a hidden defect.
## 14.16. Path Toward ML-RFC
Advancement requires operational evidence that financial integrity can be implemented and audited.
Key steps:
- **Standardize financial schemas:** revenue types, budget categories, funding states, and confidence levels
- **Define reporting formats:** periodic disclosures with comparable fields across systems
- **Create verification artifacts:** links from budgets to receipts, audits, and outcomes (DP15)
- **Test governance integration:** demonstrate budget approval, reallocation, and audit pathways (Section 6)8)
- **Run adversarial tests:** simulate capture, subsidy gaming, and funding shocks
- **Demonstrate cross-system coherence:** shared projects maintain consistent funding signals (DP7)
Promotion criteria should include the ability for participants to **inspect, compare, and challenge** financial claims over time.
## 15.17. Closing Orientation
DP17 is where the meta-layer demonstrates respect for resources and power.
Published: 2026-08-08
Pages: 8 | Words: 3941
What changed:
Synced from the book local rail (content/local/dpN.md), which carries the current working text for this chapter: expanded sections, renamed and renumbered headings, and editorial cleanup since the last revision. Published as a new revision so prior revisions stay intact.
Published: 2026-08-05
Pages: 8 | Words: 3926
What changed:
Numbered section headings and cross-reference fixes for collaborative review
Published: 2026-08-04
Pages: 8 | Words: 3926
What changed:
Synced from the book local rail (content/local/dpN.md), which carries the current working text for this chapter: expanded sections, renamed and renumbered headings, and editorial cleanup since the last revision. Published as a new revision so prior revisions stay intact.