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.
The ObliNet concept
Commitments as coordination infrastructure serving system-wide goals.
Local rationality and shared outcomes
A decision can be justified for one department yet incompatible with others’ work. Centralization helps resolve conflicts, but passing decisions between levels can delay responses and lose context. Decentralization retains local knowledge but requires alignment of interdependent actions. The research concerns combining autonomy with system effectiveness, not abandoning management.
Combining the strengths of both approaches
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.
Proposed mechanism
Participants clarify who will deliver what to whom, by when, under which conditions and authority, and against which acceptance criteria. Known resources and dependencies are to be checked before confirmation. An event may reveal a risk; revision requires consent or previously established authority. Detection is not guaranteed to be complete, and unknown conditions are explicit.
From task tracking to compatible actions
Task tracking records completion of assigned actions. ObliNet additionally investigates compatibility of expectations, conditions and dependencies before and after commitments are made. Existing tools may support these operations; comparisons must account for their actual use. No uniqueness claim is made here.
Autonomy and the limits of alignment
Autonomy means a real ability to propose terms, give a reasoned refusal and choose actions within legitimate authority. It does not imply that local interests automatically align with system-wide goals. Conflicts must be addressed, with assessment of pressure, burden distribution and actual freedom of choice.
Compatibility is not success
Formal compatibility of commitments does not guarantee achievement of shared goals. Even a fulfilled network can rely on incorrect information, omit important dependencies or deliver only intermediate outcomes. Acceptance of an individual task and organizational success are assessed separately.
Freedom, responsibility and cooperation
People make their own decisions, but the consequences of their actions can affect others, including people they neither know nor deal with directly. ObliNet’s philosophical motivation is to preserve human autonomy while developing ways to align interdependent actions, extending responsible autonomy through transparent and verifiable commitments. Not all responsibility reduces to voluntary commitments: third-party rights, public constraints and the interests of people outside the agreement must also be considered. This is the project’s value basis; it does not itself establish the proposed mechanism’s effectiveness.
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.
Clarify
What work is included? Who buys materials? What counts as finished? AI can suggest questions; people check the answers.
Confirm
Customer and contractor confirm the same conditions. An AI suggestion does not create consent.
Connect
Completion depends on tile delivery. This dependency must be recorded, or the system may not know about it.
Report a change
The tiles are late. Someone must report this or provide data through an agreed connection. Ready-made integrations are not promised.
Agree on the next step
Participants choose a new date or another option. An alert does not automatically change their agreement.
Check the result
The customer checks the work against agreed criteria. Disputes need people and a procedure chosen in advance.
Why not just use a chat?
You can agree in a chat without ObliNet. The proposed addition is one current record of conditions and links to other agreements. It is useful only if it reduces searching, repetition and errors enough to justify the extra work.
Appendix: 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 nowTHE MISSING LAYER
Make commitments explicit,
connected and verifiable.
Who may legitimately expect what from whom, under what conditions, by when — and what depends on it?
Current stage of development
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 skills trainers
ObliNet aims to help organizations accomplish their tasks more effectively: identify conditions that could block work, prevent errors, and agree on preventive action before a problem spreads through dependencies.
Coordination also depends on how participants act: whether they notice their own tension, check assumptions about others, and attend to the current situation. We created three standalone trainers to practise intentional shifts in state, perspective, and attention. Choose the skill you want to practise.
I choose my STATE
Distinguish tension, activity, and relaxation, and practise moving between them intentionally. The aim is to widen the choice of responses, rather than remain in one “correct” state.
I choose my POINT OF VIEW
Move between “Self”, “Other”, “Observer”, and “Coordinator”: clarify your goals, check assumptions about the other person, notice how the interaction unfolds, and choose the next joint step.
I choose to BE HERE AND NOW
Bring attention back to the other person’s words, the surroundings, and your own sensations, so that action is informed by current evidence as well as expectations and inner dialogue.
An example at work
When a delay becomes likely, a manager notices their irritation, asks about the contributor’s difficulties, and checks with them what is missing: information, resources, authority, or another team’s output. They then agree on the next step and, when needed, revise related commitments. This illustrates the intended use of the skills; it is not a report of a demonstrated training outcome.
The trainers complement work on ObliNet mechanisms as experimental tools for preparing participants. Transfer to real work and its effects on errors and delays remain to be tested. They do not replace competence, good faith, resources, or clearly allocated authority.
Each trainer opens as a separate app. Access depends on that app’s sharing settings.
From a desire to a commitment
A desire is not yet an agreement. A Proposal becomes a Confirmed Commitment only when the relevant parties sufficiently clarify and confirm it under the relevant Authority conditions.
- Commitment Formation
- Desire
- Intention
- Proposal
- Promise
- Confirmed CommitmentThe transition
- Commitment Lifecycle
- Execution
- Acceptance
- Consequences
Desire, Intention, Proposal and Promise precede Confirmed Commitment. This transition separates formation from Execution, Acceptance and Consequences.
AI notices. People commit.
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 confirmation 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.
- AI detects
- Human clarifies
- Parties confirm
- ObliNet records
AI notices. People commit.AI interprets. Humans authorize.
Authority and commitment
Authority defines who may legitimately act or create commitments on whose behalf. A Mandate is a bounded delegation of that Authority. A Confirmed Commitment defines the relational undertaking another actor may legitimately rely on.
- Authority
- Commitment
- Execution
- Acceptance
- Consequence
A commitment, in plain language
Who will deliver? To whom? What outcome? By when? Under which conditions? What must happen first? Who accepts completion? A shared record makes these questions answerable.
Clarity without rigidity
A material change calls for Renegotiation and confirmation of revised terms. The original commitment, the change, its reason and the affected Dependencies remain visible. Recording a claim does not prove that it is true; Evidence and Acceptance still matter.
One coordination layer.
Different participants.
The same work, a more connected process
The proposed improvement comes from replacing repeated searches, explanations and manual updates with shared confirmed information and connected dependencies. Existing tools may already provide some of these functions; their actual use is the baseline.
| Operation already performed | Proposed method with ObliNet |
|---|---|
| Find the current agreement | Retrieve confirmed conditions with their source and revision history. |
| Explain a task to another participant | Reuse the agreed outcome, conditions and relevant context. |
| Check whether work can start | Compare known prerequisites, authority and resource availability. |
| Find the consequences of a delay | Follow recorded dependencies to identify affected commitments. |
| Agree on a change | Prepare options and obtain decisions from the authorized, affected parties. |
| Compile status reports | Build current views from work events instead of repeated manual summaries. |
What is demonstrated, and what remains to be built
The experimental platform tests individual commitment checks and dependency mechanisms. The homepage demonstrates a fixed scenario. Automatic capture from workplace systems, continuous event updates and end-to-end revision workflows are target capabilities whose integration and effectiveness still need to be tested in a pilot.
Compare with the coordination people already perform →