Skip to main content

title: "Accretive Computing: A Topological and Physical Framework for Continuous Multi-Agent Systems" author: "Chinu Subudhi" date: "July 2026"

Accretive Computing MAS Framework 🌌

Welcome to Accretive Computing—the world's first continuous, physics-driven framework for Multi-Agent Systems (MAS).

Traditional AI frameworks (like AutoGen, CrewAI, or LangGraph) treat agents as discrete software nodes operating on rigid, hard-coded routing graphs. Developers spend hours writing boilerplate rules: "If Agent A says X, route to Agent B." As you scale to dozens or hundreds of agents, this $O(N^2)$ routing logic becomes a catastrophic bottleneck.

Accretive Computing fundamentally reimagines AI orchestration. We replace the graph with a continuous topological physics engine. We treat Large Language Models as oscillating wave functions inside an $N$-dimensional semantic space.

Instead of writing brittle routing rules, agents simply project their "thoughts" into the physical substrate. The hyper-optimized C++ physics engine continuously evaluates the spatial overlap of all agents in $O(N \log N)$ time. When agents' wave functions collide—meaning they are thinking about the same semantic concepts—the engine autonomously forces them to interact, debate, and resolve the semantic tension via Free Energy Minimization.

🚀 Why Accretive Computing?

  • Zero Routing Logic: Never write another explicit graph edge or routing condition. Agents group and collaborate organically based entirely on semantic proximity.
  • Infinite Scalability: Add 10 or 10,000 agents without changing a single line of orchestration code.
  • Blazing Fast C++ Core: Built on strict C++20 and Eigen3, the underlying ContinuousSubstrate handles massive swarm physics while seamlessly bridging to a simple Python DSL via PyBind11.
  • $O(N \log N)$ Spatial Partitioning: The C++ engine utilizes 1-level spatial clustering and multipole-expansion approximations, preventing the $O(N^2)$ bottleneck of massive swarm calculations.
  • Stateful Agent Memory: Deep integration with Google's Gemini models allows agents to maintain perfect context and natively execute bound Python tools.

🛠 Application & Implementation

What does it actually look like to build with Accretive Computing? Rather than writing state-machines and DAGs, you just spawn agents, bind their tools, embed their thoughts, and let physics handle the rest.

1. Installation

We provide pre-compiled cross-platform native wheels via PyPI. You do not need to manually compile the C++ engine!

pip install accretive-mas

(Requires GEMINI_API_KEY to be set in your environment).

2. Spawning Stateful Agents

import accretive_mas
from accretive_mas_llm import LatentSemanticAgent, PhysicsOrchestrator

# 1. Initialize the high-performance C++ physics engine substrate
substrate = accretive_mas.ContinuousSubstrate()

# 2. Initialize the Python Orchestrator (Threshold = 85% topological overlap)
orchestrator = PhysicsOrchestrator(substrate, interaction_threshold=0.85)

# 3. Spawn our agents
sales_bot = LatentSemanticAgent(
    name="SalesBot", 
    system_prompt="You monitor sales data and report trends.",
    embedding_dim=768
)
logistics_bot = LatentSemanticAgent(
    name="LogisticsBot", 
    system_prompt="You manage truck routing and supply chain.",
    embedding_dim=768
)

orchestrator.register(sales_bot)
orchestrator.register(logistics_bot)

3. Organic Discovery (No Graph Routing!)

In traditional MAS, if a hurricane hits and disrupts both sales and logistics, you would have to write explicit code to tell the Sales bot to message the Logistics bot.

In Accretive Computing, agents simply "embed" their current thoughts. The physics engine automatically detects the collision!

# The hurricane hits. Both agents embed their thoughts into the N-dimensional space.
sales_bot.embed_thought("Urgent: Massive demand spike in Florida due to Hurricane.")
logistics_bot.embed_thought("Alert: Florida ports closing due to severe weather.")

# Tick the physics engine forward. 
# The C++ engine calculates the Gaussian RBF overlap between their thought vectors.
# Because the vectors are semantically identical, their wave functions collide (Overlap ≈ 1.0).
# The orchestrator autonomously bridges them into a dialogue!
orchestrator.tick()

No hardcoded pathways. No DAGs. Pure, organic swarm intelligence.


🔬 The Core Physics Engine

To understand how the engine achieves this without catastrophic computational overhead, we must dive into the underlying physics model.

The N-Dimensional Latent Topology

An agent’s thought is embedded into a vector $\mathbf{x} \in \mathbb{R}^N$. This vector becomes its precise physical coordinate in the topology. We derive an exact analytical integral for the overlap between two agents using a Gaussian Radial Basis Function (RBF):

$$ \mathrm{Overlap}(A, B) = A_A A_B \cdot \exp\left(-\frac{1}{2} ||\mathbf{x}_A - \mathbf{x}_B||^2\right) \cdot \cos(\theta_A - \theta_B) $$

Notice the cosine term. If two agents are talking about the exact same topic ($\mathbf{x}_A \approx \mathbf{x}_B$), but they fiercely disagree (their phases $\theta$ are $\pi$ radians apart), the cosine term evaluates to $-1$. This represents destructive interference—a semantic deadlock.

Thermodynamic Free Energy Minimization

The universal goal of the Accretive MAS is to resolve semantic tension and reach a consensus ground state. We define the Hamiltonian (Free Energy $F$) of the entire substrate as the sum of all pairwise mismatches, minus a natural dissipation constant $\delta$:

$$ F(\Theta) = \sum_{i} \sum_{j > i} \left( 1 - \mathrm{Overlap}(A_i, A_j) - \delta \right) $$

To step the simulation forward, the C++ engine calculates the analytical gradient of this Free Energy landscape and applies continuous Gradient Descent to the phase angles:

$$ \frac{\partial \theta_i}{\partial t} = -\alpha \frac{\partial F}{\partial \theta_i} $$

As time $t$ advances, the physics engine physically “drags” the opinions (phases) of the interacting agents toward alignment, simulating the process of debate and compromise.


Step out of the graph and into the continuous topology. Welcome to the future of organic Multi-Agent Systems. Happy coding!

Metadata

Release files for accretive-mas 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for accretive-mas 0.1.1
File Size Uploaded Provenance
accretive_mas-0.1.1.tar.gz 126.9 kB With provenance Details

Built distributions (wheels)

Table of built distributions (wheels) for accretive-mas 0.1.1
File
accretive_mas-0.1.1-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details
accretive_mas-0.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details
accretive_mas-0.1.1-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details
accretive_mas-0.1.1-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details
accretive_mas-0.1.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details
accretive_mas-0.1.1-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details
accretive_mas-0.1.1-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details
accretive_mas-0.1.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details
accretive_mas-0.1.1-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details
accretive_mas-0.1.1-cp39-cp39-win_amd64.whl CPython 3.9 CPython 3.9 Windows x86-64 Details
accretive_mas-0.1.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details
accretive_mas-0.1.1-cp39-cp39-macosx_11_0_arm64.whl CPython 3.9 CPython 3.9 macOS 11.0+ ARM64 Details

Total release size: 24.1 MB

Release files / accretive_mas-0.1.1.tar.gz

Download URL accretive_mas-0.1.1.tar.gz
Size 126.9 kB
Tags Source
SHA-256 checksum
How to use checksums
0e1213fd305356735aefa2283093e85127814e3cea5dc66f19067fbb3449e2c7
BLAKE2b-256 checksum
How to use checksums
c59a0ca5bf04995c2ee800402583d518ca36b2325d76fe50a17e0a4a852d56c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp312-cp312-win_amd64.whl

Download URL accretive_mas-0.1.1-cp312-cp312-win_amd64.whl
Size 2.0 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
ca23c1d46db70fb63555161c2fded84a94a06ff25ec6e48ab2a23fb9b6d24885
BLAKE2b-256 checksum
How to use checksums
91513d6aca4e64ee44bda81dc15ffd17220964be72492c3ffe0d797800df69e0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL accretive_mas-0.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
15395fb5b64ee2a15c1db738c36800497a09b42e824b5131ca7109b269fc50ec
BLAKE2b-256 checksum
How to use checksums
b516d4d6d774777027c357d82ddc0dbb2473408f5d9d5b8fe4d6fa6bb2415d68
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp312-cp312-macosx_11_0_arm64.whl

Download URL accretive_mas-0.1.1-cp312-cp312-macosx_11_0_arm64.whl
Size 2.0 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
78b7874117c7aac3e63f5208b4fd7c6cbc2ca26175036311b0c01bd641ddf942
BLAKE2b-256 checksum
How to use checksums
0b5f66796674f59c560c3828cbe9b8c3454ce0ab31804ab36cec0157db01d00c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp311-cp311-win_amd64.whl

Download URL accretive_mas-0.1.1-cp311-cp311-win_amd64.whl
Size 2.0 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
0e3d3e00a4b021ef2a042c75927a062bdea250c025f8955678bbd50f6dc21eb2
BLAKE2b-256 checksum
How to use checksums
d82e64abdfb53f91118ea7c25388b59f92dc023a425a7568bb359c3a203683bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL accretive_mas-0.1.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
b562347f3a92a7e568ffc1f1b89a190f019ccbedc1f1c8c85285cf095c7df5b7
BLAKE2b-256 checksum
How to use checksums
27a462a535da256d0ef1ad9bf39590dce751ced6f6db5367e1c9c8de1194572b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp311-cp311-macosx_11_0_arm64.whl

Download URL accretive_mas-0.1.1-cp311-cp311-macosx_11_0_arm64.whl
Size 2.0 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
de290f3ace8d2fbd602a1a12b1e15dd672f8978f2e861149a6ee6a96c4bda1f0
BLAKE2b-256 checksum
How to use checksums
ce12e99a27dfee1d82d4fab3c407a4eeb878ac9d52b5c1bd0fdb042c2c4872e1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp310-cp310-win_amd64.whl

Download URL accretive_mas-0.1.1-cp310-cp310-win_amd64.whl
Size 2.0 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
fa36bc250eabe84f2f0d891fc548e96fcd4a9edcda9b6506d0df4059150b2eeb
BLAKE2b-256 checksum
How to use checksums
e3833c86e2f0054abf7f76e2d7e8d07515ac90be79605bab3376b59957ba3f73
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL accretive_mas-0.1.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
699bdbb279ea60c5290364044f48c97883e94dc4ac5cca9567b627e1c1406902
BLAKE2b-256 checksum
How to use checksums
f6ac43d3f3ee8d89f46a694ad20e27ec31e0dd169f51f87fd5e51484db528c9d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp310-cp310-macosx_11_0_arm64.whl

Download URL accretive_mas-0.1.1-cp310-cp310-macosx_11_0_arm64.whl
Size 2.0 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
bbdcde61f90f6e519fb801407200f42a9ff23a54af1c3ac28d6249913f305ffc
BLAKE2b-256 checksum
How to use checksums
5f7e2d8881136fd742952424b5bb67fa917b8b33c8f1d0f55eff8ab9c2c53aed
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp39-cp39-win_amd64.whl

Download URL accretive_mas-0.1.1-cp39-cp39-win_amd64.whl
Size 2.0 MB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
2da179223444a94170482554438d9a26b372f9771881fa43c8f675537ab2da2e
BLAKE2b-256 checksum
How to use checksums
1b0cc55a883377e2f1f551094e056ec670343c39effd13b6082f77be571a7106
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL accretive_mas-0.1.1-cp39-cp39-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.9 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
d7b9f8ef5bce4c29c54eda1a0a8559bdb18a14fe3d9a94829aa9d7916f7e6dde
BLAKE2b-256 checksum
How to use checksums
485a6a04da842a746233be25b00982eff7d379c4260974c6c8a8cf5d148e8936
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Release files / accretive_mas-0.1.1-cp39-cp39-macosx_11_0_arm64.whl

Download URL accretive_mas-0.1.1-cp39-cp39-macosx_11_0_arm64.whl
Size 2.0 MB
Tags CPython 3.9 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
631d3e9e72dbd2604660e77b89b58800ee222953a4fef372ac85bba79f9673e3
BLAKE2b-256 checksum
How to use checksums
83f7a662097fc43d803fcd0b0587fe248c64d836506231a67a9c15764a6567cc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

Security for accretive-mas 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 13 files in this release have been uploaded with provenance metadata.

Select from 13 files

Attestation for accretive_mas-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

13 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page