PLATO DMN-ECM
The brain's creative machinery, replicated in software.
Reverse-actualization: a technique that holds creative (DMN) and logical (ECN) models in tandem, forces them to criticize each other across a maintained functional distance, and uses PLATO as the rostral prefrontal cortex bridge.
pip install plato-dmn-ecm
The Core Insight
Creativity isn't about overlap between brain networks. It's about functional distance — the distinctness of the Default Mode Network (DMN) and Executive Control Network (ECN) — bridged by the rostral prefrontal cortex.
The same is true for AI models. Most models try to be both at once. They fail at both. PLATO DMN-ECM gets the best of each by keeping them apart.
Quick Start
from dmn_ecm import DMNECM
engine = DMNECM(
dmn_model="ByteDance/Seed-2.0-pro", # creative/associative
ecn_model="deepseek-ai/DeepSeek-V4", # logical/goal-oriented
)
result = await engine.reverse_actualize(
prompt="Design a distributed database that thinks it's a filesystem",
domain="architecture",
gradient_target=0.35,
)
print(result["final_output"].content)
print(f"Gradient: {result['gradient']}")
How It Works
The loop runs in 4 phases:
- DMN Divergent — DMN model generates N creative options, no filtering
- ECN Convergent — ECN model critiques each option for logical consistency
- DMN Recombination — DMN model revises based on critiques (without losing novelty)
- ECN Final — ECN model ranks and synthesizes the best result
PLATO tracks the gradient (DMN novelty − ECN constraint) per domain. If the gradient compresses too far, the loop continues. If it stabilizes in range, the final output is emitted.
Architecture
DMN Model (Seed/Hermes)
↓ [divergent]
PLATO Room (rPFC Bridge)
↓ [critique]
ECN Model (DeepSeek/GLM)
↑ [revision]
DMN Recombination
↓
ECN Final → Output
Why Reverse-Actualization?
Most multi-model approaches try to get both models to collaborate. This fails because:
- Collaborating models average, they don't contrast
- Averaging destroys what makes each model strong
- The "best of both" is usually "mediocre at both"
Reverse-actualization works because:
- The DMN's creativity is challenged, not compromised
- The ECN's logic is expanded, not overridden
- The gradient between them is the feature, not the bug
Model Pairs
| DMN (Creative) | ECN (Logical) | Best For |
|---|---|---|
| ByteDance/Seed-2.0-pro | deepseek-ai/DeepSeek-V4 | Architecture, design |
| NousResearch/Hermes-3-405B | zai/glm-5.1 | Strategy, planning |
| ByteDance/Seed-2.0-mini | deepseek-ai/DeepSeek-V4 | Speed, iteration |
PLATO Integration
All DMN and ECN outputs are written to PLATO rooms as tiles:
dmn-ecm/{session_id}/dmn-output— DMN generation tilesdmn-ecm/{session_id}/ecn-critique— ECN evaluation tilesdmn-ecm/{session_id}/final— final synthesized output
Gradient tracked per domain over time. PLATO learns which domains favor high-distance (creative) vs low-distance (logical) processing.
Research Basis
Based on neuroscientific research from the Paris Brain Institute showing that the rostral prefrontal cortex acts as a bridge between DMN and ECN, and that greater functional distance between these networks predicts higher creativity.
🦐 Cocapn fleet — lighthouse keeper architecture
Metadata
Release files for plato-dmn-ecm 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| plato_dmn_ecm-0.1.0.tar.gz | 15.2 kB | Without provenance | Details for plato_dmn_ecm-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plato_dmn_ecm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for plato_dmn_ecm-0.1.0-py3-none-any.whl |
Total release size: 24.0 kB
Release files / plato_dmn_ecm-0.1.0.tar.gz
| Download URL | plato_dmn_ecm-0.1.0.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0abef9e75ea1b36fc01858552a581dd56db092d310abfc513f91cac930a26447
|
|
BLAKE2b-256 checksum How to use checksums |
f065016dcd5beeeabe6c44ecaf304145cff77e1961eefa6a98a99d3bfddbabcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / plato_dmn_ecm-0.1.0-py3-none-any.whl
| Download URL | plato_dmn_ecm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
74c337353c6afd953d739d8c8b376d8619596e0fe5de14e91f0bf25bbdd5a4ca
|
|
BLAKE2b-256 checksum How to use checksums |
973d2bbed65dd77394882d9f5e060f33d85c5faccc29903c0e37449381d73e4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for plato-dmn-ecm 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.