Mythadis separates demonstrated capability from active development, research direction, and aspiration.
State what is true now.
Mythadis Swarm is an early private research and engineering project. The purpose of this page is to provide a clear, current record of what has been demonstrated, what is being built, and what remains unproven.
Publish a field report showing source-grounded response behavior against fixed demo data.
In Active Development
What is being built now
IN ACTIVE DEVELOPMENT
Data Parcels
A self-describing, content-addressed data model intended to preserve identity, context, provenance, relationships, and integrity.
IN ACTIVE DEVELOPMENT
Archive Health
A system for distinguishing healthy, degraded, at-risk, and unrecoverable archive states.
IN ACTIVE DEVELOPMENT
Mythadis Agent Foundations
Early work toward a participant-facing Agent with explicit local resource and policy boundaries.
IN ACTIVE DEVELOPMENT
Mission Control Foundations
Initial orchestration capabilities for agents, health, roles, missions, storage, compute, and validation.
IN ACTIVE DEVELOPMENT
Distributed Data Path
Continued validation of storage, transfer, verification, and recovery across multiple nodes.
Research Directions
What remains a research direction
Swarm Compute at meaningful scale
Coordinated compute across many participants remains unclaimed.
RESEARCH DIRECTION
Must prove: Scheduling, workload isolation, verification, recovery, security, and measurable efficiency.
Concordance Engine
A future system for reasoning over agreement, disagreement, evidence, and unresolved claims.
RESEARCH DIRECTION
Must prove: Reliable evidence handling, dissent preservation, traceable outputs, and validation across real use cases.
Aegis
A future safety, policy, and trust boundary for coordinated intelligence.
RESEARCH DIRECTION
Must prove: Threat modeling, enforceable policy boundaries, auditability, and failure behavior.
Public Agent distribution
The Mythadis Agent is not publicly available.
FUTURE GATE
Must prove: Local safety, installation, update behavior, privacy boundaries, and clear operator control.
Mission Swarms
Mission Swarms remain future work, not demonstrated public outcomes.
FUTURE GATE
Must prove: Mission definition, participant roles, evidence flows, coordination loops, and measurable outputs.
Large-scale archive preservation
The current prototype does not claim permanent archive preservation.
RESEARCH DIRECTION
Must prove: Durability, recovery, integrity, redundancy, governance, and long-running operation.
Cross-institution coordination
Coordination across institutions remains a future research and partnership challenge.
RESEARCH DIRECTION
Must prove: Governance, permissions, data boundaries, trust model, and repeatable collaboration workflows.
Public volunteer network
No public volunteer network currently exists.
FUTURE GATE
Must prove: Safety, onboarding, incentives or motivation model, support, governance, and abuse resistance.
Boundary of the Claim
What we are not claiming
Mythadis Swarm is not production-ready.
No public volunteer network currently exists.
The Mythadis Agent is not publicly available.
Mythadis does not currently operate at global scale.
Mythadis has not demonstrated humanity-scale mission outcomes.
Mythadis does not currently solve longevity, climate, pollution, medicine, or public science.
AI agreement is not treated as proof.
Distributed storage is not described as permanent.
Decentralized architecture is not presented as automatically secure or trustworthy.
No investment return or token model is being promoted.
The purpose of these boundaries is not to make the vision smaller. It is to make future proof meaningful.
The first swarm
Current private trials use heterogeneous systems.
Current private trials use a small collection of heterogeneous systems, including Linux and macOS nodes with different processor, memory, storage, and network characteristics.
These environments are used to test discovery, connectivity, stability, data movement, recovery, and increasingly coordinated work.
PRIVATE TEST ENVIRONMENT / CONCEPTUAL VIEW
Linux nodemacOS nodeContainer nodeLocal storageControl surfaceEvidence catalog
Validation Model
How capability becomes a claim
Define the bounded capability.
Declare the test conditions.
Run the test.
Preserve logs, outputs, and artifacts.
Record limitations and dissent.
Publish an appropriate Proof entry or Relic.
Update Current State only after validation.
A capability enters this page only when there is evidence that it exists under defined conditions.
Current Priorities
What is being proven next
Three-node distributed data-path validationLong-running node stabilityRecovery under node lossAgent role clarityMission Control observabilityData Parcel contractArchive Health measurementReproducible deployment
Each priority must produce bounded evidence before it advances the public claim.
Update Policy
A living record
Current State is intended to change as evidence changes.
Capabilities may advance, remain experimental, become contested, or be removed when later evidence shows that an earlier interpretation was incomplete.
CURRENT STATE VERSION / 0.1LAST REVIEWED / JULY 2026STATUS / PRIVATE R&DRELATED RELEASE / MWEB-009LINK / PROOFANNALS / RESEARCH DIRECTION
Help test what comes next.
Mythadis is interested in engineers, researchers, systems thinkers, and mission partners who value ambitious goals, explicit limitations, and evidence-based progress.