Hierarchical management
Shared goals → priorities → task allocation
Provides a structure for shared goals, priorities and accountability. Possible limits include overloaded leadership, delays between levels and reduced initiative.
Scientific overview and preserved demonstrations
Materials from earlier versions are preserved in full. Current statuses and limitations are listed in the Research register.
Shared outcomes through aligned activity
ObliNet is a research infrastructure for improving the alignment of distributed joint activity through explicit, interconnected and verifiable commitments.
Shared goals and autonomous decisions
ObliNet seeks to combine the strengths of hierarchical and distributed management: shared goals, priorities and accountability with autonomy, initiative, flexibility and local knowledge. Explicit interconnected commitments are proposed as a way to reduce alignment delays and incompatible decisions. This is a research hypothesis, not an established advantage.
Research hypothesis
The ObliNet hypothesis is that aligning interdependent commitments can improve the achievement of system-wide goals while accounting for resources, time and total coordination costs and preserving participants’ autonomy. This is a positive research proposition; its scope and effect size remain to be established experimentally.
Outcomes matter more than record counts
The primary criterion is actual achievement of system-wide goals specified in advance by an authorized party. Goals, criteria and constraints are not derived from the commitment network. Assessment includes quality, resources, elapsed time, total costs and autonomy, as well as the distribution of benefits and burdens.
The commitment network is a means of coordination
Commitments connect expected outcomes, conditions, authority and known dependencies. Their value lies in their contribution to joint activity, not in confirmation counts. The illustrative scenario below runs in the browser with fixed data and does not change real agreements.
Three approaches: what to retain and what to test
Distributed management
Local knowledge ↔ autonomous decisions
Supports autonomy, flexibility and initiative. A possible limit is that locally justified decisions may conflict over deadlines, resources and dependencies.
Coordination with ObliNet — a hypothesis
Shared goals ↔ commitments ↔ autonomous action
Proposes connecting shared priorities and autonomous action through explicit commitments. Reductions in delays, burden and misalignment remain to be tested against formalization costs.
This simplified comparison does not rank the approaches. ObliNet is a proposed coordination infrastructure compatible with different authority structures; it is not a third type of authority distribution.
Earlier materials and demonstrations
Earlier materials and demonstrations are preserved for continuity. Conceptual descriptions below do not establish implementation or effectiveness; current statuses and artifacts are listed in the results register.
How can this help me?
The proposed approach: clarify the result and conditions before committing, see dependencies, agree on changes and check completion. It cannot force people to keep promises or replace dispute resolution.
At home: “Will you pick up our child?”
“Yes.” But when, from where, and who can step in if there is a delay? A short clarification can reveal different assumptions.
At work: one delay affects everyone
A supplier delivers parts by Wednesday, production assembles the order by Friday, and the customer checks it. If parts arrive late, changing a date is not enough: people need to agree on what happens next.
Work with a contractor or teamA coordination desk for city needsAI actionsResearch or developmentOrganized group purchasing for people and businesses
The city knows its residents’ problems. But does it know who is ready to help solve them?
A proposed city coordination desk connects needs and wishes with people’s and organizations’ capabilities. Residents, civic groups, businesses, nonprofits and institutions can take part — including those based in other cities.
CONNECTED RESPONSIBILITY
The network
serves shared outcomes.
When one commitment changes, the next people need to know.
Delay the materials to see the consequences travel through the graph.
What happens next?
ObliNet makes affected dependencies visible. People then clarify the impact and confirm revised terms; a delay does not silently rewrite their agreement.
DEPENDENCY GRAPHILLUSTRATIVE EXAMPLE
A · Supply materialsConfirmedMaterials provider · Wednesday
↓ enables
B · Deliver the workReadySupplier · Friday
↓ enables
C · Accept the resultWaitingClient confirms the result
↓ triggers
PaymentPendingUnder the agreed payment terms
One shared view. Three connected commitments.
From a delay to revised terms
Illustrative walkthrough: fixed data and rules, no live AI or external systems. The controls demonstrate the intended sequence; they do not change a real agreement.
Original terms
- Source event
The example assumes materials arrive Wednesday.
- Dependency check
Delivery on Friday depends on those materials. Acceptance and payment depend on completion.
- Authorized revision
Use the delay button above to introduce a changed condition.
- Updated shared view
The original confirmed terms remain in force.
The proposed workflow reuses the agreement and its dependencies to prepare a revision. Real time savings require a comparison with the existing process.
What works now?
Available tools, experimental mechanisms and plans are listed separately.
How can I try it?
Start with the example. If it matches a problem you face, describe one case in the form below.
Prepare for a conversation
Standalone exercises to notice your state, consider another perspective and refocus attention. You can use them independently. They do not manage commitments; improved joint work remains a research hypothesis.
What we are testingAppendix: detailed explanation and principles
Optional reading. This also describes proposed mechanisms and future capabilities; a description does not mean a feature is available. See “What works now” for the current status.
What works nowWe often make agreements — but we don’t always understand them the same way
ObliNet helps participants clarify agreements, account for dependencies and carry joint work through to a verified result.
ObliNet helps make agreements explicit
More than “we agreed”:
who → what → for whom → by when → under what conditions → how the result is verified.
Crucially, it shows which other commitments fulfilment depends on.
If conditions change, the system helps participants see:
- what can no longer be fulfilled;
- who is affected;
- what needs to be renegotiated;
- which new agreement now applies.
From agreement to a verified result
ObliNet connects:
needs → capabilities → agreement → commitments → execution → verification of the result.
This creates a network that shows not only who promised what, but also who is entitled to expect what, from whom, under which conditions — and what depends on that commitment being fulfilled.
This is the ObliNet commitment network.
FROM CONVERSATION TO COORDINATION
One sentence.
A clear commitment.
A commitment can exist long before there is a contract — and many coordination failures begin there.
THE CONVERSATION
“I’ll deliver Friday if the materials arrive Wednesday.”
The condition belongs with the promise.PROPOSED STRUCTURE For people to confirm
- Responsible party
- Supplier
- Expected result
- Deliver the work
- Deadline
- Friday
- Condition
- Materials arrive by Wednesday
- Dependency
- Materials delivery
- Acceptance
- Client confirms the result
- AI detects
- Human clarifies
- Parties confirm
- ObliNet records
- Dependencies are tracked
AI suggests the structure. People confirm it. ObliNet tracks what depends on it.
AI notices. People commit.AI interprets. Humans authorize.
Two actors clarify a possible commitment and confirm one commitment object. Dependencies connect it to Execution, Acceptance and Outcome.
THE COORDINATION CYCLE
Each outcome informs
the next commitment.
Why can reasonable participants fail to act reliably together?
They may rely on different information and assumptions, and interpret goals, authority and working conditions differently. Even sound individual decisions can be incompatible. ObliNet proposes making consequential differences explicit, checking the basis of expectations and connecting actions through explicit commitments.
ObliNet addresses two connected problems: coordinating action when participants understand the situation differently, and making the use of delegated authority accountable.
Understand the situation and coordinate actionCheck information and assumptions, compare options and clarify conditions and dependencies so participants understand what they can reasonably expect.
Make the use of authority accountablePreserve decisions, their grounds and consequences so those who delegated authority and authorized reviewers can assess its use.
Earlier materials describe prototypes and proposed ObliNet mechanisms. Their implementation scope, alignment with the new architecture and readiness for end-to-end experiments require versioned, reproducible artifact checks. Browser scenarios checked in this edition are listed in the results register.
Coordination is already part of your work
People clarify requirements, agree on deadlines, check readiness, allocate resources, revise plans and accept results every day. This work is spread across conversations, documents, systems and participants’ memory.
ObliNet is designed to make these same operations more rational: reuse confirmed conditions, preserve dependencies and coordinate changes without repeatedly reconstructing the agreement.
See which operations can change →CHOOSE YOUR PERSPECTIVE
What does ObliNet
mean for you?
Different responsibilities.
A shared need for clear commitments.
PERSPECTIVE
Citizen
Can I see how delegated power is being used?
Explore this perspective ↗PERSPECTIVELeader
Can I explain what I knew and why I chose?
Explore this perspective ↗PERSPECTIVEBusiness / Organization
Can we prevent misunderstandings before they cost us?
Explore this perspective ↗PERSPECTIVEAI Developer
What may an agent promise on our behalf?
Explore this perspective ↗PERSPECTIVEResearcher
How do autonomous actors coordinate under uncertainty?
Explore this perspective ↗PERSPECTIVEInvestor / Partner
Can ObliNet become the coordination layer for humans, organizations and AI agents?
Explore this perspective ↗BETWEEN CONVERSATION AND EXECUTION
The layer we
keep leaving implicit.
Who committed to what, under which conditions, and what depends on it?
Understand the commitment layer ↗| Messaging | What was said |
|---|---|
| Task management | What needs to be done |
| Contracts | Legally formalized agreements |
| Payments | Value transferred |
| ObliNet | Commitments, authority and dependencies |
Introductions for different audiences ↗
THE LONG-TERM DIRECTION
From Intelligence to Coordination
Intelligence helps a participant reason: understand a situation, compare options and draw well-founded conclusions.
Coordination helps participants act reliably together: agree on who does what and when, account for dependencies and confirm completion.
Earlier materials describe prototypes and proposed ObliNet mechanisms. Their implementation scope, alignment with the new architecture and readiness for end-to-end experiments require versioned, reproducible artifact checks. Browser scenarios checked in this edition are listed in the results register.
Before a commitment is confirmed, its feasibility is checked: authority, resources, conditions and dependencies on other participants. After confirmation, execution, changing conditions and acceptance of the result against agreed criteria are tracked.
AI helps participants formulate, check and align commitments, and assess evidence of their fulfillment.
The authority to enter into or confirm commitments, and to accept fulfillment, remains with the relevant authorized participants.
Explore the principles ↗