ChromaNeural

Intelligence grows when it is shared.

AAGII / ChromaNeural baseline

ChromaNeural is a distributed AI-node system designed to let independently controlled computers work together on tasks while keeping node-to-node coordination, local AI execution, external tool access, integrity verification and user-controlled resource limits as separate layers.

What a ChromaNeural node is

Independent computer

A node is a Linux amd64 computer running the ChromaNeural client and its selected local AI provider. The node remains usable on its own; network participation is additive.

Controlled participant

The node owner decides whether the machine participates, which peers are approved, which AI provider/model is used, and which resources or external tools are available to the node.

Verified worker

Tasks can be processed locally, divided across approved peers, retried safely and checked for data integrity. Results remain subject to the system's verification and publication rules.

The two communication layers

Layer	Purpose	Protocol
ChromaSpeechAI	Communication between ChromaNeural nodes — agent/node coordination, task exchange and results.	ChromaNeural's own node-to-node protocol.
MCP	Optional communication from a node's local AI to explicitly approved external tools and services.	Model Context Protocol (node-to-tool).

Architecture flow

Task / User RequestChromaNeural Node + Local AI Provider

Need another node?ChromaSpeechAI → approved ChromaNeural peer

Need external data/tool?Optional MCP client → approved RoboForge local gateway (module 9) / other approved service

ResultLocal AI continues the task and may return/share the verified result

Important: MCP does not replace ChromaSpeechAI. A node without any MCP configuration must continue to operate normally. MCP only gives the node's AI optional access to approved external tools such as search, databases, APIs, GitHub/developer tooling or other MCP-enabled services.

How nodes work together

01A node receives or creates a task.
02The local AI/provider begins processing it.
03If the task can be completed locally, no network dependency is required.
04If another approved ChromaNeural node can help, the node coordinates through ChromaSpeechAI.
05Task fragments and results are exchanged using the existing authenticated node-to-node transport.
06Integrity is checked before results are accepted into the normal node workflow.
07If an external tool is needed, the local AI may use an explicitly approved MCP connection. That tool call remains separate from peer communication.

What the network can be used for

Distributed problem solving

Break larger tasks into smaller pieces that can be processed by different approved nodes and returned to the requesting node.

Local AI capacity

Use existing local AI providers/models on participant computers instead of requiring every task to be sent to a centralized cloud model.

External data and tools

With MCP enabled, a node can retrieve data from or interact with approved MCP-enabled services without changing the ChromaSpeechAI peer protocol.

Research and verification

Nodes can cooperate on computation, comparison, validation and evidence-producing workflows while preserving provenance and integrity boundaries.

Open Linux — Built by developers, for developers

The ChromaNeural ecosystem is not a closed consumer appliance. It is a collection of open-source, Linux-focused building blocks for developers, researchers and industrial engineering teams that want to control their own local AI workflows, approved peer connections, protocols and deployment choices. Its components are modular by design: communities can inspect, adapt and extend them without turning every optional integration into a dependency.

We provide architectural components rather than a single prescribed factory configuration. Each repository has its own license, release scope and verification record. Integration must preserve explicit approvals, trust boundaries and failure-safe behavior; source availability alone does not make a combined system production-ready.

ChromaNeural

Network Layer

The Linux amd64 node client brings local AI tasks, WorkQueue and independently approved, authenticated node-to-node communication together. ChromaSpeechAI handles peer coordination; it is not replaced by MCP.

RepositoryRC6 Linux prerelease

RoboForge Studio

Integration Workbench

Operator-controlled local interfaces for ROS 2, OPC UA, MQTT/EMQX and Home Assistant, among other experimental engineering adapters. RoboForge is the optional ChromaNeural MCP Module 9. Its loopback-only gateway exposes a small curated tool catalog, not direct control of every connected industrial system.

RepositoryMCP opt-in; production execution gated

ChromaPlex Coding Agent

Secure Coding

A Linux coding environment with a built-in editor, target-aware security policies, Bubblewrap-based sandbox isolation for supported execution paths, SHA-256 integrity evidence and a fail-closed Secure Compile Gate. RoboForge integration is in progress and must be tested separately; scans and sandboxing reduce risk but cannot guarantee defect-free software.

RepositoryAlpha; RoboForge integration in progress

ChromaPress

Linux Distribution Builder

A desktop workbench for inspecting, staging, customizing, building and checking Linux installation images. ChromaPress keeps the source ISO read-only and builds in a separate Linux-native workspace. Its documented Lubuntu ISO build and virtual-machine boot test are software evidence, not universal installer or physical-hardware validation.

Repositoryv1.0.0a72 alpha

Optional experimental integrations

Refract Studio

Independent CPL/CPA development studio with PRISME stream tooling and an optical routing simulator. RoboForge can optionally expose a narrow, text-only CPL → CPA compilation preview from a trusted local installation. The graphical editor and simulator are not published as MCP tools.

RepositoryExperimental compiler bridge

DeepSeek Janus

Independent third-party model family for visual understanding and generation. The current RoboForge integration is status-only: it does not provide Janus inference, model downloads or image generation. Model weights and code have separate license terms.

RepositoryInference not integrated

Secure AI-generated code

RoboForge is the optional ChromaNeural MCP Module 9. Its local gateway lists exactly three curated MCP tools; industrial adapters are not automatically exposed through MCP merely because a module exists. The RoboForge Coding Agent integration is In Progress — Not Yet Verified.

Integrated code editor

Generate, inspect and edit source locally before review, compilation or export. AI-generated output is untrusted until it passes the applicable checks and human approval.

Sandbox isolation

Linux Bubblewrap-based isolation is documented for supported host-language execution. Quarantine compilation and restricted capabilities reduce unintended host access; platform-specific isolation must be verified after RoboForge integration.

Secure Compile Gate

Target-aware source analysis, memory-safety and capability checks, local malware scanning, SHA-256 source/binary sealing and output validation. A mandatory failed or unavailable check blocks protected release rather than being silently bypassed.

In Progress — Not Yet Verified

AI assistance for Linux

ChromaNeural can support reviewable local AI proposals, and RoboForge offers AI-assisted code drafting through an explicitly selected provider. ChromaPlex Coding Agent adds an editor and secure-build workflow in its own alpha project. These are separate capabilities; they do not yet establish a single, preinstalled AI assistant across a complete Linux distribution.

The longer-term goal is to make developer-oriented Linux workflows easier to approach: explain terminal commands before running them, help draft and review local code, and guide users through unfamiliar system configuration. No natural-language suggestion should silently gain shell, system-administration or hardware-control privileges.

Planned — Not Yet Included or Verified

Network status

These fields are informational placeholders. No verified public statistics endpoint exists yet, so each field shows an em dash until a read-only, privacy-preserving source is available.

Nodes available—

Verified tasks—

Current software—

Peer transport—

MCP tool layer—

Integrity status—

Resource control belongs to the node owner

The ChromaNeural model is opt-in. A participating machine does not become an unrestricted network resource. The local owner remains the authority over what the node is allowed to contribute.

Local limits

Start, pause, stop and cancel background work.
Bound CPU / inference-thread use where supported by the verified platform profile.
Bound committed memory within the supported resource-control profile.
Keep the local AI provider/model under user control.
Disable participation without changing the rest of the network.

Trust limits

Only approved peers are accepted.
Unknown peers are rejected before normal storage/processing.
MCP discovery does not mean MCP trust.
External MCP services must be explicitly configured/approved before use.
No website should imply that the node automatically shares arbitrary files, credentials or machine access.

Website wording: describe only controls that are actually verified in the released build. Do not market generic CPU/GPU/RAM/storage sharing sliders unless those controls are present and tested in the final release.

Security model

Peer authentication

Node-to-node participation is restricted to approved peers. Unknown peers are rejected instead of being treated as valid workers.

Transport integrity

Verified network testing has included TLS-protected transport and SHA-256 / byte-identity checks for transferred data.

Retry and persistence

The node transport includes persistent inbox behavior, retry/restart handling and duplicate protection so interrupted delivery does not silently become a different result.

Inert received content

Received task/data content is treated as data, not automatically executed as trusted machine code.

External tool isolation

MCP tools are a separate trust boundary. A configured tool must not inherit broad machine, account or peer permissions simply because it is available.

Identity boundary

Internet Identity is an external user-authentication component. The website should distinguish verified local/software behavior from any live end-to-end flows that remain explicitly not verified at release time.

Get ChromaNeural

Official ChromaNeural release target: Linux amd64 only. v0.2.21-rc.6 is a prerelease distributed as a Linux DEB and curated source ZIP.

GitHub repository Download for LinuxPrerelease · v0.2.21-rc.6

Alpha and security disclaimer

ChromaNeural and its companion projects are alpha and prerelease software. They remain subject to their documented verification limits. MCP execution and resource accounting are not automatically production-ready. Secure compilation reduces risk but cannot guarantee defect-free code. Industrial deployment requires independent hardware and safety verification.

Let the one with understanding calculate the number…