AetherOrchestrate
A Falsification-First Investigation of Decentralized Orchestration in the Aether Family
A structured investigation of whether a decentralized orchestration gap genuinely exists in the Aether family, or whether it is already covered by AetherFlow (integration), AetherGovern (authority), or AetherMesh (distribution). v2.0.0 adds a reference implementation (7 modules, 39 tests, 3 experiments) alongside the v0.1.0 hypothesis.
Installation
# From PyPI (published)
pip install aetherorchestrate
# From source (development)
git clone https://github.com/gitdeeper15/aetherorchestrate.git
cd aetherorchestrate
pip install -e ".[dev]"
# Run tests
pytest
# Run experiments
python experiments/decomposition_accuracy/run.py
python experiments/assignment_fairness/run.py
python experiments/coordination_window/run.py
# CLI
aetherorchestrate info
aetherorchestrate verify
2.0.0) is the reference implementation. It is not a production system. The v0.1.0 paper remains the authoritative hypothesis record.Project
| Field | Value |
|---|---|
| Full title | AetherOrchestrate: A Falsification-First Investigation of Decentralized Orchestration in the Aether Family |
| Subtitle | A Falsification-First Investigation of Goal Decomposition, Task Assignment, Scheduling, Dependency Tracking, and Routing in Multi-Agent Software Ecosystems |
| Version | 2.0.0 (Reference Implementation) + 0.1.0 (Formal Architecture) |
| Stage | Reference Implementation with Reproducible Experiments |
| License | MIT (code) · CC-BY-4.0 (docs, manuscript) |
| Domain | Distributed Systems / Software Engineering / Multi-Agent Coordination |
| DOI (Zenodo) | 10.5281/zenodo.24095399 |
| DOI (Figshare) | 10.6084/m9.figshare.34963687 |
| OSF | 10.17605/OSF.IO/2F7TZ |
| PyPI | aetherorchestrate 2.0.0 (published) |
| Record ID | AETHERORCHESTRATE-02 |
Central Question
Is there a set of requirements for goal decomposition, task assignment, scheduling, dependency tracking, and routing in multi-agent software systems that (i) is not already specified by the six existing dimensions, (ii) does not reduce to verification or to governance, (iii) can be specified without reintroducing a central authority, and (iv) yields an observable benefit over existing mechanisms?
The Seven Functional Dimensions
| # | Dimension | Focus | Question |
|---|---|---|---|
| 1 | AetherGit | Storage and versioning | How are agent-generated changes stored, signed, and versioned? |
| 2 | AetherFlow | Integration and post-merge verification | How are changes integrated into a shared trunk and verified? |
| 3 | AetherProof | Specification and evidence | How are claims specified and how is evidence for them recorded? |
| 4 | AetherMesh | Distribution and consistency | How is state synchronized without a central coordinator? |
| 5 | AetherGovern | Authority and policy | Who is authorized to do what, under which policy, and how is authority revoked? |
| 6 | AetherRuntime | Monitoring and runtime assurance | What are agents doing while they run, and how are anomalies contained? |
| 7 | AetherOrchestrate (hypothesis) | Orchestration | What should agents do next, and how is work decomposed, assigned, scheduled, ordered, and routed? |
Figure 1 — The Seven Functional Dimensions of the Aether Family. The seventh dimension (AetherOrchestrate) is a hypothesis under investigation, not a confirmed dimension.
Failure Conditions F1–F5
| ID | Claim under test | Status |
|---|---|---|
| F1 | Non-redundancy | Not falsified (R2, R4, R6 partly covered) |
| F2 | Orthogonality to verification | Not falsified (narrowly) |
| F3 | Boundary with governance | Not falsified (decentralized setting) |
| F4 | Decentralizability | Not falsified (with residuals) |
| F5 | Observable benefit | Untested |
Propositions
| # | Proposition | Status |
|---|---|---|
| P1 | Determinism of Local Decomposition | Proof sketch · implemented in code |
| P2 | Irreducible Coordination Window | Proof sketch · implemented in code |
The Five Orchestrate Layers
| Layer | Question | Status |
|---|---|---|
| L1 — Decomposition | How is a goal broken into tasks? | Implemented |
| L2 — Assignment | Which agent executes each task? | Implemented |
| L3 — Scheduling | When does each task run? | Implemented |
| L4 — Dependency Tracking | What are the dependencies between tasks? | Implemented |
| L5 — Routing | How is each task routed to its executor? | Implemented |
Figure 2 — The five layers of AetherOrchestrate. Ordering reflects conceptual dependency, not an enforcement hierarchy.
Figure 3 — A goal decomposed into a DAG of tasks with hypothetical durations.
Figure 4 — The assignment challenge in a decentralized setting: centralized (excluded) vs. decentralized (the challenge).
Figure 5 — AetherOrchestrate acts before work runs; AetherFlow acts after work exists.
Figure 6 — The centralization spectrum of orchestration designs. The replicated scheduler is where AetherOrchestrate must operate (F4).
v2.0.0 Experimental Results
| # | Experiment | Result |
|---|---|---|
| 1 | Decomposition Accuracy (M1) | 10 goals; mean task count = 1.00; all acyclic |
| 2 | Assignment Fairness (M4) | Jain index = 0.8803 (expected 0.9174; 4% deviation) |
| 3 | Coordination Window (M8) | 5 scenarios; all positive; min 0.008 s, max 7.5 s |