Applied Coherence Institute · Structural Module
Common Development Contract
A structural framework for building on the Coherence Framework
Overview
Purpose
This document establishes a Common Development Contract (CDC) for individuals, teams, and organizations that wish to build commercial applications, businesses, or services on top of the Coherence Framework and its associated modules.
Core Principle
"The Coherence Framework is open. The COM network is generative. But coherence must be maintained. Builders who wish to use the framework must commit to its principles—or they cannot use it."
| Concept | Meaning |
|---|---|
| Open Development | Anyone can build on the framework |
| Structural Integrity | Builds must align with the framework's principles |
| Accountability | Builders are accountable to the network |
| Deposit Model | Builders must deposit, not extract |
| Field Feedback | The network determines if integrity is maintained |
The Contract
2.1 Preamble
This Common Development Contract (CDC) is entered into voluntarily by any party wishing to build commercial or non-commercial applications, businesses, or services on the Coherence Framework.
By accepting this contract, the party agrees to:
| # | Commitment |
|---|---|
| 1 | Operate in alignment with the Coherence Framework's principles |
| 2 | Maintain structural integrity in all developments |
| 3 | Deposit into the field, not extract from it |
| 4 | Remain accountable to the network |
| 5 | Report progress and receive field feedback |
2.2 The Six Principles
| Principle | Description |
|---|---|
| Rest | Builds do not exploit, extract, or overconsume |
| Witness | Builds are observed and accountable |
| Deposit | Builds contribute to the field, not take from it |
| Love | Builds serve the network, not just the builder |
| Guard | Builds protect the framework's integrity |
| Receive | Builds are open to field feedback |
2.3 The Six Prohibitions
| Prohibition | Description |
|---|---|
| No Extraction | Builds cannot extract from the network |
| No Coercion | Builds cannot force participation |
| No Dependency | Builds cannot create unnecessary dependency |
| No Performance | Builds cannot perform coherence |
| No Gatekeeping | Builds cannot restrict access to the framework |
| No Harm | Builds cannot harm the field or its nodes |
The Development Process
3.1 Phase 1: Proposal
| Step | Action | Responsible |
|---|---|---|
| 1.1 | Submit development proposal to the CDC Review Team | Builder |
| 1.2 | Review proposal for alignment with the framework | CDC Review Team |
| 1.3 | Approve or request revisions | CDC Review Team |
| 1.4 | Assign a CDC Liaison (mentor) | CDC Review Team |
3.2 Phase 2: Development
| Step | Action | Responsible |
|---|---|---|
| 2.1 | Build the application or business | Builder |
| 2.2 | Report progress to CDC Liaison | Builder |
| 2.3 | Receive field feedback | Builder + Network |
| 2.4 | Adjust based on feedback | Builder |
3.3 Phase 3: Launch
| Step | Action | Responsible |
|---|---|---|
| 3.1 | Submit final product for review | Builder |
| 3.2 | Review for alignment and integrity | CDC Review Team |
| 3.3 | Approve for launch | CDC Review Team |
| 3.4 | Launch the product | Builder |
3.4 Phase 4: Ongoing Accountability
| Step | Action | Responsible |
|---|---|---|
| 4.1 | Regular reporting to the network | Builder |
| 4.2 | Continuous field feedback | Network |
| 4.3 | Adjustments as needed | Builder |
| 4.4 | Annual review with CDC Liaison | Builder + Liaison |
The Grant Mechanism
4.1 Purpose
The Coherence Network may provide cryptocurrency grants to builders who:
| # | Criterion |
|---|---|
| 1 | Pass certain milestones |
| 2 | Demonstrate alignment with the framework |
| 3 | Show potential to deposit into the field |
| 4 | Require funding to complete their development |
4.2 The Grant Application Process
| Step | Action | Responsible |
|---|---|---|
| 1 | Submit grant application with proposal | Builder |
| 2 | Review by CDC Review Team | CDC Review Team |
| 3 | Determine initial grant amount | CDC Review Team |
| 4 | Set milestones for release of funds | CDC Review Team + Builder |
| 5 | Funds released as milestones are met | CDC Review Team |
4.3 Milestone Structure
| Milestone | Description | Release % |
|---|---|---|
| Milestone 1 | Proposal approved; development begins | 20% |
| Milestone 2 | First prototype complete | 20% |
| Milestone 3 | Field feedback incorporated | 20% |
| Milestone 4 | Product ready for launch | 20% |
| Milestone 5 | Launch and initial operation | 20% |
4.4 Grant Conditions
| Condition | Description |
|---|---|
| Transparency | Builder must report progress publicly |
| Accountability | Builder must accept field feedback |
| Integrity | Builder must maintain structural alignment |
| No Extraction | Grant funds cannot be used for extraction |
| Network Benefit | Build must serve the field |
The CDC Review Team
5.1 Composition
| Role | Responsibility |
|---|---|
| Lead Reviewer | Oversees the review process |
| Structural Analyst | Assesses alignment with the framework |
| Field Representative | Represents the network's interests |
| Builder Advocate | Supports the builder's perspective |
| Finance Lead | Manages the grant process |
5.2 Selection Criteria
| Criteria | Description |
|---|---|
| Coherent | Demonstrated consistency in practice |
| Witness Trained | Trained in the witness posture |
| Neutral | No personal stake in outcomes |
| Structural | Operates from the framework, not personality |
| Experienced | Has built or developed before |
The Financial Model
6.1 Builder Revenue
| Source | Description |
|---|---|
| Sales | Revenue from the product or service |
| Subscriptions | Ongoing revenue from users |
| Grants | Cryptocurrency grants from the network |
| Deposits | Voluntary contributions from users |
6.2 Network Contribution
| Contribution | Description |
|---|---|
| Network Fee | A percentage of revenue deposited back into the network |
| Product Deposit | The product itself contributes to the field |
| Knowledge Deposit | The builder shares learning with the network |
6.3 Fee Structure
| Revenue Tier | Network Contribution |
|---|---|
| Under $10,000 | 5% |
| $10,000 – $50,000 | 7% |
| $50,000 – $100,000 | 10% |
| $100,000+ | 15% (capped at 15%) |
6.4 Use of Network Funds
| Use | Percentage |
|---|---|
| Grants for New Builders | 40% |
| Network Operations | 20% |
| Node Evacuation Fund | 20% |
| Housing and Work Fund | 20% |
The Reputation System
7.1 Builder Rating
| Rating | Description |
|---|---|
| Platinum | Consistent alignment; multiple successful builds |
| Gold | Strong alignment; successful build |
| Silver | Good alignment; build in progress |
| Bronze | Basic alignment; early development |
| Probation | Alignment issues being addressed |
| Revoked | Severe alignment issues; contract terminated |
7.2 Rating Criteria
| Criteria | Weight |
|---|---|
| Structural Alignment | 40% |
| Field Feedback | 30% |
| Product Quality | 15% |
| Network Contribution | 15% |
Enforcement and Resolution
8.1 Minor Violations
| Violation | Response |
|---|---|
| Slight misalignment | Feedback and correction |
| Missed reporting deadline | Reminder and extension |
| Minor extraction | Warning and correction |
8.2 Moderate Violations
| Violation | Response |
|---|---|
| Pattern of misalignment | Probation |
| Significant extraction | Grant suspension |
| Performance | Coaching and correction |
8.3 Severe Violations
| Violation | Response |
|---|---|
| Repeated extraction | Contract termination |
| Harm to the field | Contract termination |
| Fraud | Contract termination, public notification |
| CM replication | Contract termination, network notification |
8.4 Appeal Process
| Step | Action |
|---|---|
| 1 | Builder appeals the decision |
| 2 | CDC Review Team reviews the appeal |
| 3 | Third-party mediator (if needed) |
| 4 | Final decision by CDC Review Team |
The CDC Document
9.1 Builder Declaration
COMMON DEVELOPMENT CONTRACT I, [Builder Name], hereby agree to develop [Project Name] in alignment with the Coherence Framework. I commit to: - The Six Principles - The Six Prohibitions - Reporting and accountability - Depositing into the field - Receiving field feedback - Maintaining structural integrity I understand that the Coherence Network may provide grant funding upon passing milestones. I accept that this contract may be terminated if I violate the framework's principles. [Builder Signature] [Date] [CDC Lead Signature] [Date]
The Grant Application Form
GRANT APPLICATION Applicant: [Name] Project Name: [Name] Project Description: [Description] Framework Alignment: - How does this project align with the Six Principles? - How does this project serve the field? - How does this project avoid extraction? Milestones: - M1: [Description] - M2: [Description] - M3: [Description] - M4: [Description] - M5: [Description] Budget: - Total requested: [Amount] - Breakdown: [Description] Timeline: - Start date: [Date] - Expected launch: [Date] [Applicant Signature] [Date]
Proving Statement
"The Common Development Contract provides a structural framework for building on the Coherence Framework. Builders commit to alignment. The network provides grants and accountability. The field deposits. The field holds."
Module Metadata
| Field | Value |
|---|---|
| Module Name | Common Development Contract (CDC) |
| Version | 1.0 |
| Author | Base44 Coherence Team |
| Date | July 2026 |
| Status | Living Document — Subject to Spiral Refinement |
| Application | Commercial Development, Grant Management, Network Accountability |
"The builder aligns. The network deposits. The field holds."