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.

LATEST RELEASE / 08 OCT 2026Swahast Protocol v0.3Agents draft. People commit.
AI, COORDINATION & TEMPORARY ORGANIZATIONSCONCEPT PAPER 001 / 2026SCROLL TO EXPLORE
01 / THE THESISFROM INTENTION TO ORGANIZATION

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.

01 / THE INTERNET

Connect information.

Make communication possible across distance.

02 / DIGITAL PLATFORMS

Connect participants.

Make discovery and exchange more accessible.

03 / THE AI HYPOTHESIS

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.

02 / THE LIFECYCLEEXPLORE THE EIGHT STAGES

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.

ANATOMY OF A TEMPORARY ORGANIZATION01 / 08

01 / BEGIN WITH INTENTION

Make the objective legible.

Clarify the desired outcome, constraints, available resources, and what successful completion would look like.

ILLUSTRATIVE RESEARCH PROJECT

AI may help interpret and prepare. Participants retain authority over selection, commitments, amendments, and acceptance.

02.1 / THE SPECIFICATIONSWAHAST PROTOCOL · VERSION 0.3

SWAHAST / स्वहस्त / ONE’S OWN HAND

Agents draft.
People commit.

An open protocol for temporary collaborations. Independent people agree on contributions, share credit, resolve disputes, and carry their history into the next project.

Only people can commit. Every material assumption an agent makes must be disclosed and acknowledged before an agreement is accepted.

Published as the Networked Firm Protocol through v0.2. Swahast names the protocol; The Networked Firm remains the founding research essay.

What changed in v0.3

A new name, established terminology for each party’s commitments, an explicit contribution statement, and expanded related work. The v0.2 rules carry forward unchanged; the record field and template names follow the rename.

Party positions on conflicts and intent declared before drafting are new questions for v0.4, rather than new rules.

THE CONTRIBUTION / SECTION 14

Three elements brought together.

The building blocks have precedents. v0.3 states a narrow contribution in how these elements work together across a collaboration.

  1. 01 / INSPECTABLE DRAFTING

    Acknowledge the assumptions.

    Agents disclose the choices they made in fixed material categories. Each material assumption must be acknowledged before the people involved consent.

  2. 02 / CO-CREATION

    Agree on shared credit.

    Joint agreements let co-creators share obligations, approve together, and set structured credit in advance, alongside supply agreements for deliverables.

  3. 03 / TWO-WAY CONDUCT

    Carry facts with context.

    Permanent conduct facts are computed from a shared project log for owners and contributors alike. They travel with explanations and repair records, without scores or ratings.

A specification to test.

No version has yet run on a real project. Legal enforceability, data protection, practical escrow integration and other operational questions remain open for pilots and v0.4.

CITE SWAHAST V0.3

Pawar, D. (2026). Swahast Protocol (Version 0.3). Zenodo. https://doi.org/10.5281/zenodo.23231563

Protocol version history

Each release retains its own document, name and DOI.

  1. CURRENT / V0.3

    Swahast Protocol

    8 October 2026 · 27 pages

    Renamed from Networked Firm Protocol. Clarifies the contribution and commitments terminology, expands related work, and carries forward v0.2’s rules.

  2. ARCHIVE / V0.2

    Networked Firm Protocol

    6 October 2026 · 25 pages + 4-page decisions appendix

    Introduced joint mode, disclosed assumptions, a shared project log, escrow and two-way conduct. Preserved under its original published name and DOI.

    CITE THE ORIGINAL V0.2

    Pawar, D. (2026). Networked Firm Protocol (Version 0.2). Zenodo. https://doi.org/10.5281/zenodo.23188282

Read the founding whitepaper v1.0
03 / THE ECONOMIC PRIMITIVEA GRAPH OF COMMITMENTS

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.

Objective↓Capability↓Contributor or asset↓Terms↓Outcome

THE CONTRIBUTION AGREEMENT

SWAHAST / CA—001ILLUSTRATIVE · DRAFT

Contribution Agreement

Research assistant / Evaluation methodology

OBJECTIVE

Build a specialist research assistant.

CAPABILITY

Design an evaluation framework.

CONTRIBUTOR

Independent domain researcher.

01 / SCOPE

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.

04 / THE PLATFORMA DESIGN STUDY, GROUNDED IN THE PAPER

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.

ILLUSTRATIVE WORKSPACE
PROJECT / 001 CONCEPT EXAMPLE

From idea to a shared brief.

Build a research assistant that helps specialists find and evaluate relevant literature.

DESIRED OUTCOME

A working prototype, a documented evaluation, and a clear account of its limitations.

CONSTRAINTS

Source attribution
Permitted data use
Specialist review

ACCEPTANCE CONDITIONS

Inspectable retrieval
Reviewed evaluation set
Documented failure cases

A useful next question
Which capabilities and existing assets would make this objective feasible?

PROPOSED PRODUCT SURFACES · WHITEPAPER §21EXPLORE THE FOUR VIEWS ↑
A COORDINATION LAYER

One possible interface for an open protocol. This workspace illustrates the whitepaper’s proposed product surfaces; it does not implement Swahast Protocol v0.3. Early coordination can remain human assisted.

05 / PERSISTENT MEMORYTHE NETWORK REMAINS

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.

TEMPORARY ORGANIZATION / A

An objective.
A formation.
An outcome.

Project closes
PERSISTENT NETWORK

Artifacts & provenance

Accepted contributions

Rights & reusable assets

Relationships & context

TEMPORARY ORGANIZATION / B

A new objective.
A new formation.
A stronger starting point.

Future possibility

Evidence over ranking.

Context over abstraction.

Contestability over permanence.

06 / THE RESEARCH AGENDAA HYPOTHESIS TO TEST

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.

01

Can 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.

02

Do 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.

03

Does 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.

04

When 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

  1. PUBLISHED

    Establish the thesis

    Whitepaper v1.0
    24 September 2026

  2. PUBLISHED DRAFT

    Name the open protocol

    Swahast Protocol v0.3
    8 October 2026

  3. PROPOSED

    Test a first collaboration

    Use the pilot profile.
    Observe coordination and consent.

  4. EVIDENCE LED

    Refine the open protocol

    Pilot evidence and review
    inform v0.4.

The model and proposed architecture have not yet been empirically validated. Temporary organizations are one possible form; their suitability depends on the work.

07 / GO DEEPERTHE FOUNDING PAPER
Cover of The Networked Firm: AI, Coordination, and the Emergence of Temporary Organizations, by Devashish PawarOPEN 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.

Author
Devashish Pawar
Published
24 September 2026
Format
25 pages · Working paper
Licence
CC BY 4.0
CITE THE PAPER

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

A BRIEF INTRODUCTION

Start with the idea.

The short film introduces the question.
The paper develops the argument.

A WIDER ORGANIZATIONAL DESIGN SPACE

What would you build
if you could assemble
the right capabilities?

Explore the model