Chapter 1 of 11
The proposed network economy
How can independent businesses create and earn together without giving up their independence?
Illustrative examples only. These are possible commercial arrangements, not current offers, agreed pay, promised work, forecasts, or evidence of customer results. All amounts are USD, before tax.
Independent businesses. Shared operating power.
Intent’s wider ambition is a production network where independent people and firms combine relationships, expertise and reusable systems to deliver work that none needs to own alone.
A proposed federation of independent businesses, temporary delivery teams and maintained common assets, coordinated through explicit agreements and accountable roles.
What can we coordinate together while keeping each participant’s business, judgment and customer obligations clear?
This is a V1 institutional design for discussion and bounded experiments. It is not an adopted constitution, investment offer, compensation plan or claim of an operating marketplace. “DAO-type” describes the ambition for distributed coordination here; it does not assume blockchain, tokens, pooled ownership or autonomous legal authority.
Six questions every arrangement must answer.
| Dimension | Question | What needs an explicit record | Boundary |
|---|---|---|---|
| Contribution | What did this participant actually bring? | Consented relationships, discovery, selling, domain judgment, engineering, assurance, operation, teaching, IP or infrastructure. | A referral, ongoing account stewardship and delivery are different contributions, even when one participant performs all three. |
| Authority | What may this participant decide or commit? | A role mandate naming scope, budget, decision limits, escalation, expiry and who can revoke it. | Reputation, community status and technical skill do not automatically authorize spending, contracting or speaking for every participant. |
| Earning | What event creates an obligation to pay? | The payer, recipient business, work or success event, calculation basis, cap, acceptance, cancellation treatment and payment date. | Attribution is not a payable invoice. Company receipts are not personal take-home pay, and a shared opportunity is not guaranteed revenue. |
| Rights | What remains independent, and what is permitted to be shared? | Pre-existing customers and IP, newly created work, data permissions, licenses, brand permission and publication consent. | Participation does not transfer an entire customer book, create automatic equity or authorize publishing a customer’s confidential work. |
| Risk | Who must act when the work, money or relationship fails? | Named contracting entities, delivery owners, acceptance duties, funding gaps, remediation, insurance and liability boundaries. | A network label does not absorb liability. Independence must reflect the actual working relationship, not merely the agreement’s wording. |
| Exit | How can a participant leave without stranding the customer? | Notice, active commitments, earned unpaid amounts, credential revocation, lawful data return, handover, license survival and dispute resolution. | Leaving is not permission to abandon accepted work, erase a debt, copy confidential data or claim perpetual income from later unrelated projects. |
Four parts of the proposed institution.
| Part | Job | Authority | Possible funding |
|---|---|---|---|
| Independent businesses V1 proposal | People and firms retain their own customers, identity, assets and choice of engagements. | Each business controls its own commitments and authorizes participation for a bounded scope. | Its own business funds its own obligations unless another payer explicitly agrees otherwise. |
| Shared operating layer V1 proposal | Intent can maintain qualification, technical standards, discovery support, contracting coordination, evidence records and shared tools. | Specific stewardship mandates identify what Intent may decide; the network is not assumed to vote on or own Intent’s company. | A priced operating service, an agreed engagement contribution or an opt-in asset budget could fund this work; the choice remains open. |
| Engagement teams V1 proposal | The smallest suitable team forms around a customer outcome, then operates, hands over or dissolves when that scope ends. | The selected prime, customer sponsor and named delivery lead have different powers that the scope makes explicit. | The actual payer funds authorized work. Supplier due dates, acceptance events and collections remain separate. |
| Maintained common assets V1 proposal | Permitted skills, components, evaluation methods and teaching material can make later work faster and more dependable. | Maintainers govern a defined asset under its license and mandate, not every product or participant using it. | Maintenance requires a budget and an owner. Open publication, commercial licensing and customer-funded work are distinct choices. |
The estate supplies different kinds of leverage: Labs and Evals create evidence; Demos make work inspectable; Learn transfers capability; tools and skills distribute reusable work; products serve repeated needs. Those assets can strengthen an engagement without making every asset owner a party to its entire revenue.
The common assets need economics of their own
A reusable skill is not free to maintain simply because it can be copied. Decide which rights are shared, which work is paid and who can stop an unsustainable commitment.
- Licensed public asset
- Publish only work whose owners permit it. Fund optional implementation, assurance or support separately from the public license.
- Jointly funded component
- Buy a defined common build or maintenance period with scoped customer adaptations. Set acceptance and cancellation rules before shared spending.
- Commercial asset or license
- Retain agreed proprietary rights and price permitted use, redistribution or white-label operation explicitly. No automatic royalty to every network participant.
- Deliberate reinvestment
- Choose a maintenance or learning budget from genuinely available funds after obligations, tax and working-capital needs. Record one allocation once; a reserve is not a second earned margin.
Who approves these budgets and whether any participant has a vote are design decisions. A reputation score must not silently become ownership, voting power or a financial entitlement.
Borrow mechanisms. Test our own model.
These precedents show ways to coordinate independent participants. They do not prove that Intent’s design will attract demand, distribute value fairly or operate profitably.
Enspiral: autonomy with explicit mandates
Its handbook shows how autonomous people and ventures can maintain shared decision processes and distinguish core operations from collaborative funding.
Useful discipline: Borrow the discipline of documented mandates, separate budgets and clear ownership of collective decisions.
Limit: Enspiral’s foundation separates governance shareholding from dividends and is not designed to absorb venture risk. Intent has not adopted that ownership structure or its decision rules.
Documented institutional design; no claim that this proves Intent’s margins or guarantees democratic decision-making will be fast.
- Enspiral Handbook: Decisions Agreement — A published governance mechanism, not evidence that Intent has adopted it or that consensus guarantees commercial performance.
- Enspiral Handbook: Foundation purpose and structure — Its ownership and reinvestment rules are specific to Enspiral. They are not an Intent ownership or profit-sharing model.
- Enspiral Handbook: Financial Agreement — The agreement describes governance, not audited profitability or a transferable contribution rate.
Open Collective: shared administration needs a responsible entity
Fiscal hosting supplies groups with money handling and financial administration through a named legal organization.
Useful discipline: Make the custodian, approval authority, reporting duties and exit path visible when any common budget is proposed.
Limit: A major host announced dissolution in 2024; the platform explained that hosts were separate organizations. Shared software does not remove an operator’s financial fragility.
The platform did not know the host’s exact reasons for closing. Intent is not announcing a fiscal host, nonprofit structure or custody service.
- Open Collective: Fiscal hosting — Intent is not claiming fiscal-host status, charitable treatment or authority to hold other parties’ funds. A commercial network needs its own structure.
- Open Collective: Statement on the Foundation’s dissolution — The platform said it did not know the exact reasons for the host’s decision. This is not evidence that every host or the software platform failed.
CoTech: complementary firms can present a common capability
Its public network combines technology services with member forums, mentoring and shared professional relationships.
Useful discipline: Build a discoverable capability network without assuming every engagement must run through one company or erase the identity of its delivery firms.
Limit: CoTech’s current membership is for UK worker cooperatives. Intent’s proposed international mix has different ownership, eligibility and contracting questions.
A visible operating federation and published service offer; no guarantee of member utilization, sales or profit.
- CoTech: Cooperative Technologists — Its public service presence demonstrates a federation mechanism, not a guaranteed source of projects or an audited margin for each member.
- CoTech: Membership — Intent’s proposed international mix of individuals and independent firms is different. These eligibility and ownership rules are not being imported.
Three experiments that fit this industry.
LLM capabilities, APIs and agent workflows change quickly. The opportunity is to make deployment, assurance, maintenance and handover easier to coordinate—not to promise that automation removes their costs.
A workflow that can change operators
Test whether an independent delivery team can hand a real AI workflow to another qualified operator without rebuilding it or depending on the original builder.
- Buyer
- A customer that wants continuity and supplier choice.
- Payer
- The customer buys a bounded implementation and transfer exercise; future operation is separately agreed.
- Who earns
- The original builder, independent reviewer and receiving operator earn for distinct accepted work.
- Who decides
- The customer authorizes the transfer; each operator controls its own acceptance and risk. A reviewer records evidence rather than awarding legal authority.
Bounded test: One workflow, two willing firms, a licensed deployment package, a rollback plan and an explicitly funded handover. No promise that every customer can switch every supplier instantly.
Evidence: Measure whether the second operator can deploy, evaluate, observe, roll back and recover the workflow using the agreed package. Record transfer effort, defects and unresolved dependencies.
Stop or change: Stop expansion if undocumented dependencies, unsupported licenses or unaffordable transfer effort prevent safe operation.
The first engagement pays for usable evidence and portability. Repeatable transfer materials can become a licensed or maintained common asset with the owners’ consent.
A shared AI change-response service
Let a small set of independent firms jointly buy maintenance for a non-confidential evaluation and compatibility suite when models, APIs or agent harnesses change.
- Buyer
- Firms repeatedly supporting the same integration or workflow pattern.
- Payer
- Opt-in firms purchase a defined maintenance window and deliverables under an agreed budget.
- Who earns
- Maintainers earn for releases; independent reviewers earn for validation; a coordinator earns for actual scheduling and administration.
- Who decides
- Contributors decide the budget mandate through the agreed process; maintainers decide implementation inside it. Customer deployment approval stays with the customer’s operator.
Bounded test: One reusable integration, a fixed period, capped spend, permitted test data and no unlimited emergency-support promise. A sponsor gets no hidden editorial veto.
Evidence: Compare total upkeep and regression-detection effort with the firms’ previous separate work. Count genuine adopters and paid renewals separately from downloads.
Stop or change: End or reprice if the funded capacity cannot cover the declared maintenance scope, review independence fails or no firm chooses to renew.
A shared operating service earns from a concrete maintenance job. It needs no network-wide token or claim on participating firms’ unrelated revenue.
A paid option on verified delivery capacity
Test whether a customer or prime will pay a specialist firm to reserve a small, time-limited capacity window after a paid discovery decision.
- Buyer
- A prime or customer whose deployment timing is uncertain but delay would be costly.
- Payer
- The party requesting the reservation pays an agreed capacity option; implementation is another scope if activated.
- Who earns
- The firm earns for a genuine reservation commitment; the specialist earns under its own firm’s arrangement; qualification and coordination are separately priced when needed.
- Who decides
- The firm controls what it commits. The buyer alone activates its purchased option within its terms; a network directory cannot commit anyone’s time.
Bounded test: One named capability window, explicit availability evidence, cancellation/expiry rules and no double-booking. Any credit toward later delivery must be written down.
Evidence: Test whether buyers value reserved capacity, whether the firm actually honors it and whether reservation income covers the opportunity cost of keeping the slot available.
Stop or change: Stop if customers will not fund the reservation, capacity is represented twice or standby obligations exceed the firm’s ability to deliver.
This separates a useful capacity promise from unpaid community membership. The reservation is a limited commercial service, not a tradeable claim on a person.
The choices that still need to be made.
| Decision | Standard for a useful answer |
|---|---|
| What exactly is Intent authorized to coordinate? | Name the service, payer, decision scope and accountable entity before adding network-wide authority. |
| What earns a delivery or stewardship mandate? | Use relevant evidence, actual availability and role fit; allow reassessment, challenge and expiry. |
| Who pays for the common operating layer? | Test a specific service fee or opt-in budget against delivered value before adopting any general contribution rule. |
| Which decisions need participant voice, and which need one owner? | Separate consultation, delegated authority, legal control and economic rights; do not treat them as one membership benefit. |
| What can be reused, and what stays with its creator or customer? | Define background IP, project work, data, licensing and publication permissions at the relevant asset boundary. |
| Does this network make a real engagement better? | Start with one funded experiment. If coordination costs exceed its customer and participant value, simplify the structure. |
A shared vision can coexist with clear project authority. Governance should make it possible to decide, deliver, challenge and leave; it must not replace the search for an actual customer and a useful paid outcome.
Research, evidence boundaries and diagram method
This is a proposed operating model illustrated with constructed numbers. The sources below establish program mechanisms and constraints; none establishes the scenario rates, Intent revenue, individual compensation or a guaranteed source of projects.
- Anthropic: Services Track and Partner Hub — Distinguishes practice standing from referral credit and deal protection. Does not establish any scenario fee, Intent tier, inbound work or cash entitlement. Checked 2026-10-12.
- OpenAI Partner Network — Shows an official build, co-sell and delivery program. No claim of Intent enrollment, procurement approval, referral rate or awarded work. Checked 2026-10-12.
- AWS Partner Central: Creating a fund request — Separates funding approval, cash claims, invoices and credits. Eligibility and program terms apply; the customer-paid discovery example is not an AWS award. Checked 2026-10-12.
- AWS Marketplace: Managing disbursements — Explains why accepted work and available cash can occur at different times. A marketplace example only; other procurement and payment routes have their own terms. Checked 2026-10-12.
- Microsoft: Manage co-sell opportunities — Supports a customer-consent gate before sharing contact details in co-sell. Does not grant another firm ownership of an account, a universal commission or guaranteed seller help. Checked 2026-10-12.
- Langfuse: Self-hosted pricing — A public example separating open-source software from paid enterprise capabilities and support. This is an offer structure, not evidence of Intent demand, profitability or transferable pricing. Checked 2026-10-12.
- GitHub Sponsors: Sponsorships, fees and taxes — Shows a distinct sponsorship route for eligible open-source contributors. Sponsorship is not a guaranteed sale, support contract or license transfer; no sponsorship is assumed in the ledgers. Checked 2026-10-12.
- AWS Marketplace: Channel Partner private offers — Distinguishes approved resale from ordinary vendor consumption. This does not authorize resale of an arbitrary model, API, dataset or contributor’s software. Checked 2026-10-12.
Diagram method: Cathryn Lavery’s open-source Diagram Design, using its Sankey, waterfall, bar, line, architecture and layer-stack references in Intent’s established visual style. The selected chart grammar explains the relationship; the worked examples supply the data.
Apply it to a real workflow.
Start with a customer problem, the people who can help, and a clearly bounded first piece of work.
Request an outcome