Skip to content
ObliNet2.0

Scientific programme

From a research question to definitions, comparisons and testable evidence.

Research focus

The research concerns alignment of distributed joint activity among participants with different knowledge, goals and authority. It tests how commitment networks and alignment procedures contribute to system-wide outcomes. Record counts and formal consistency are intermediate properties, not final goals.

Three levels of testing

Formal methods examine specification properties under stated assumptions. Synthetic experiments compare coordination methods within a defined environment. Practical pilots test applicability in specific settings. Evidence at one level does not replace testing at another.

Limits and alternative explanations

Benefits may result from extra attention, training, implementation quality or information access rather than commitments. Comparisons therefore match resources and information conditions, examine sensitivity to assumptions and disable mechanisms separately. Scope must follow from evidence.

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.

What to study

Where differences arise: interpreting a promise, having the means to deliver it, changing conditions or checking the result.

What does not prove success

More records, alerts or approvals do not establish benefit. Results and total effort matter.

How to contribute

Suggest a testable hypothesis, comparison method or real process. The detailed programme is in the appendix.

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 now
A RESEARCH PROGRAM

Intelligence is individual.
Coordination is relational.

How can autonomous actors with different goals, knowledge, constraints and Authority form compatible commitments and adapt through feedback?

For researchers

Why can reasonable participants fail to act reliably together? ObliNet proposes a research program on coordination under differing knowledge, goals, expectations and authority. The site connects two areas: examining the grounds for joint action and making delegated authority accountable. It covers commitment networks, local autonomy within hierarchies, propagation of the consequences of change and decision assessment. Hypotheses and proposed measures are distinguished from confirmed results; effectiveness remains to be established through comparative studies.

Coordination within and across management levels

ObliNet investigates coordination both among independent participants and within multilevel hierarchies, with local autonomy bounded by delegated authority. Vertical relationships of direction and execution connect to horizontal dependencies between departments.

Participants may understand a situation differently while also sharing a mistaken assumption. Research should examine both compatible expectations and their grounds: information sources, unknowns, alternative explanations and changing conditions. A revised risk assessment must not silently change a commitment’s terms; revision requires the relevant authority or a previously agreed rule.

A question to investigate

Coordination Science is a proposed interdisciplinary research program, not an already established academic discipline. Its participants may be people, teams, companies, governments and AI agents.

What we need to understand

Commitment formation and interpretation. Commitment Networks. Coordination Failures. Renegotiation. Authority. Human–AI coordination. Each theme requires clear definitions and testable hypotheses.

Coordination is relational: compatibility among autonomous actors.

Four autonomous actors have their own goals, information, Authority and constraints. Commitments, Dependencies, Acceptance and a feedback loop connect peers without a central commander.

This illustration shows coordination among peers. The research also covers multilevel hierarchies, where authority is delegated and dependencies cross management levels.

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.

What a pilot could measure

Interpretation Divergence, Dependency Visibility, Renegotiation Latency and Acceptance Ambiguity. Define denominators and observation windows; also measure Formalization Cost and the candidate Prevented Unrealistic Commitment Rate.

Sometimes the best commitment is the one that was not made.

An explicit refusal or revised proposal can prevent an impossible promise. A pilot should test whether earlier clarification improves coordination enough to justify its cost. No effectiveness claim is assumed.

Read the principles in context ↗

How a result becomes a condition for another action

This illustrative example distinguishes enabling conditions, already confirmed commitments and verifiable results. Work must be delivered for acceptance; confirmed acceptance is one of the payment conditions, alongside funds, timing and authority.

Three rows: work conditions — contractor’s commitment — delivered work; acceptance conditions — review — confirmed acceptance; payment conditions — payer’s commitment — confirmed payment.
Arrows from a result to the conditions for the next action indicate a dependency, not automatic execution.
Text description of the dependencies
  1. Work depends on materials, resources, agreed terms and authority. A contractor’s confirmed commitment is not yet the result of the work.
  2. Delivered work, criteria and the reviewer’s authority enable verification. Acceptance is confirmed separately.
  3. Confirmed acceptance, funds, timing and authority form the payment conditions in this example. Making and confirming the payment is a result that still needs to be achieved.

Meeting the conditions makes action possible but does not guarantee a result. When conditions change, affected dependencies must be checked and changes agreed again; previous commitments do not change automatically.

Open the existing demonstration of revised terms · Discuss research and development