AN EXPLORATION OF WHAT COMES NEXT
What if the
next company
was a network?
Independent people. Shared objectives.
A new way to come together, create value,
and carry the experience forward.
We made communication cheap.
Organizing is still expensive.
A message can travel around the world in a second. Turning an idea into a team that can deliver it still takes interpretation, judgment, negotiation, and shared understanding.
Connect information.
Make communication possible across distance.
Connect participants.
Make discovery and exchange more accessible.
Connect meaning.
Help turn an incomplete objective into a shared, executable structure.
A WORKING CONCEPT
Semantic coordination cost.
The effort required to clarify an objective, identify the capabilities it needs, evaluate evidence, agree on commitments, and keep independent contributions aligned.
What becomes possible if AI can reduce that effort?
THE ORGANIZING IDEA
The organization is temporary.
The network remembers.
A project can end without its useful evidence, relationships,
and reusable capabilities disappearing with it.
An objective appears.
An organization takes shape.
A Networked Firm begins with an outcome. People and resources assemble around it, agree on contributions, work together, and preserve what they learn.
01 / BEGIN WITH INTENTION
Make the objective legible.
Clarify the desired outcome, constraints, available resources, and what successful completion would look like.
AI may help interpret and prepare. Participants retain authority over selection, commitments, amendments, and acceptance.
FROM THE THESIS TO THE RULES
Agents draft.
People commit.
The whitepaper asks what becomes possible when coordination gets easier. Protocol v0.2 sets out how independent people make commitments, share credit, resolve disputes, and carry their history forward.
Nothing binds a participant without their own consent. Every material assumption an agent makes must be disclosed and acknowledged before an agreement is accepted.
What v0.2 adds
Built from the unpublished v0.1 working draft, a test agreement, and a one-on-one review.
- 01 / CO-CREATION
Two ways to work together.
Supply mode covers a contributor’s deliverable. Joint mode lets co-creators share obligations, approve together, and agree on credit and exit terms before work begins.
- 02 / DRAFTING AUTHORITY
Make the assumptions visible.
Agents list the choices they made. Participants acknowledge material assumptions individually; agents never accept commitments on their behalf.
- 03 / SHARED HISTORY
One log. A common account.
Each project keeps an append-only log. Status is computed from records and consent. Amendments cite the exact version they change.
- 04 / CONSEQUENCES
Commitments have a dispute path.
Paid work uses milestone escrow, unless explicitly waived. The dispute route, reviewer, and thresholds are fixed at signing. A neutral provider holds the money.
- 05 / TWO-WAY TRUST
Conduct travels with context.
Owners and contributors are equally visible through facts computed from the log. Facts travel with explanations and repair records, never scores or ratings.
- 06 / OPEN GOVERNANCE
No single gatekeeper.
Participants hold their history. The protocol commits to open discovery and neutral stewardship once two independent implementations exist. The query interface remains for v0.3.
- 07 / CONFORMANCE
Test coordination first.
The pilot profile logs consent inside one application and exports JSON. The full profile adds cryptographic identity, hashes, and signatures for portability. Both apply the same rules.
v0.2 has not yet run on a real project. Legal enforceability, data protection, practical escrow integration, and other operational questions remain open for pilots and v0.3.
Pawar, D. (2026). Networked Firm Protocol (Version 0.2). Zenodo. https://doi.org/10.5281/zenodo.23188282
Make contribution
explicit.
Every temporary organization needs more than a list of names. It needs a shared understanding of who provides what, under which terms, and how completion is accepted.
THE CONTRIBUTION AGREEMENT
Contribution Agreement
Research assistant / Evaluation methodology
Build a specialist research assistant.
Design an evaluation framework.
Independent domain researcher.
What is being provided?
An evaluation framework, a documented test set, and a review of the assistant against the agreed criteria. Dependencies and exclusions are recorded before work begins.
The infrastructure
between collaborators.
The first product could be small: four surfaces that help a real project form, establish terms, and preserve accepted contributions. Work continues in the tools people already use.
From idea to a shared brief.
Build a research assistant that helps specialists find and evaluate relevant literature.
A working prototype, a documented evaluation, and a clear account of its limitations.
Source attribution
Permitted data use
Specialist review
Inspectable retrieval
Reviewed evaluation set
Documented failure cases
A useful next question
Which capabilities and existing assets would make this objective feasible?
Capabilities, with their evidence.
Start with what the outcome requires. Inspect the sources behind every capability claim.
Retrieval engineeringSource: repository · Role: maintainer
Artifact linkedDomain evaluationSource: prior project · Role: specialist reviewer
Context recordedLiterature datasetAsset: research corpus · Condition: permitted reuse
Terms to inspectResearch interfaceSource: portfolio · Role: product designer
Artifact linkedEvidence before reputation
AI interpretations stay linked to their sources and can be challenged.
A formation people can inspect.
Compose a feasible group of people and assets. Expose trade-offs before anyone commits.
Confirm asset licensing, reviewer availability, milestone criteria, and the process for changes.
Proposals become commitments through consent
Recommended formations and draft agreements require participant acceptance.
Carry the contribution forward.
After closure, preserve what was accepted, which rights remain, and what can be reused.
Specialist evaluation framework
- Role
- Domain researcher
- Evidence
- Evaluation report & review record
- Rights
- As defined in the accepted agreement
- Visibility
- According to participant permissions
- Context
- Scope, amendments & limitations preserved
Portable evidence, contextual judgment
A contribution record helps the next project inspect relevant experience.
One possible interface for an open protocol. This workspace illustrates the whitepaper’s proposed product surfaces; it does not implement Protocol v0.2. Early coordination can remain human assisted.
One project ends.
The next starts with context.
Accepted work creates inspectable history. That history can help future collaborators understand what happened, which capabilities were demonstrated, and which constraints matter.
An objective.
A formation.
An outcome.
Project closesArtifacts & provenance
Accepted contributions
Rights & reusable assets
Relationships & context
A new objective.
A new formation.
A stronger starting point.
Future possibilityEvidence over ranking.
Context over abstraction.
Contestability over permanence.
The future is an
open question.
AI can improve coordination inside firms too. The comparative question is when temporary networks can compete with the continuity, accountability, and governance of permanent organizations.
01Can formation become faster and more credible?
+
Measure the time from an incomplete objective to a mutually accepted team, unresolved capability requirements, and the human effort spent on coordination. Compare this with an appropriate existing approach.
02Do explicit agreements prevent misunderstandings?
+
Track agreement amendments, accepted contributions, and disputes. Test whether structured terms improve clarity around scope, rights, reward, and acceptance without creating more administration than they save.
03Does portable evidence help the next collaboration?
+
Observe whether previous contribution records change formation decisions. Preserve source provenance, permissions, and the ability to contest errors. Evaluate whether newcomers still have viable paths into the network.
04When should a temporary team become a firm?
+
Repeated collaboration, specific investments, durable dependencies, and tacit knowledge may favour a permanent organization. A useful network should help recognize that boundary. Voluntary repeat formation is an early signal worth testing.
FROM CONCEPT TO EVIDENCE
- PUBLISHED
Establish the thesis
Whitepaper v1.0
24 September 2026 - PUBLISHED DRAFT
Specify the mechanics
Protocol v0.2
6 October 2026 - PROPOSED
Test a first collaboration
Use the pilot profile.
Observe coordination and consent. - EVIDENCE LED
Refine the open protocol
Pilot evidence and review
inform v0.3.
The model and proposed architecture have not yet been empirically validated. Temporary organizations are one possible form; their suitability depends on the work.
OPEN THE WHITEPAPER ↗CONCEPTUAL WHITEPAPER / VERSION 1.0
The Networked Firm
AI, Coordination, and the Emergence
of Temporary Organizations
The argument, intellectual foundations, proposed protocol, limitations, and falsifiable propositions behind the concept.
Pawar, D. (2026). The Networked Firm: AI, Coordination, and the Emergence of Temporary Organizations (Version 1.0) [Working paper]. Zenodo. https://doi.org/10.5281/zenodo.22931577
Start with the idea.
The short film introduces the question.
The paper develops the argument.
A WIDER ORGANIZATIONAL DESIGN SPACE