Skip to content
Conduit

mcp server

Project-World-Model

Eradicating integration debt via L3 Causal Digital Twins and a 'Team of Rivals' counterfactual simulation architecture. Stop reacting, start predicting.

petripaananen/Project-World-Modelcommunitylistedunreviewed

Set up

Runs on your computer. Pick your agent and operating system.

This project does not publish an install method we can turn into a config. Follow the README instead.

README

synced Oct 29, 2026

🌍 Project World Model (PWM) Framework

Autonomous Causal Digital Twin & Self-Improving Multi-Agent Production Management

Python 3.12 License: Apache 2.0 Tests Passing Gemini 3 Ready JEPA & RSI Powered GCP Scale-to-Zero

Stop reacting, start predicting. Moving enterprise software production from association-level tracking (Agile / Scrum / Kanban) to self-calibrating, causal world model simulation.


📖 Theoretical Foundation & Academic Grounding

The Project World Model (PWM) framework solves the "Paradox of Agility": the phenomenon where exponential code and asset generation by generative AI models creates massive, unmanageable integration debt that completely overwhelms linear, human-driven Scrum and Kanban workflows.

PWM resolves this by operating as a Causal Digital Twin (CDT). Operating an asynchronous 24-hour Agent Verification Engine (AsyncThink), PWM autonomously models, detects, simulates, and resolves integration debt across version control, sprint backlogs, and team communication before conflicts reach production.

🎓 Academic Research Foundation

The framework is conceptually and empirically validated by Petri Paananen's Master's Thesis:

"Itseohjautuvat työnkulut videopeliteollisuudessa: tekoälyn maailmanmallit tuotannon johtamisen viitekehyksenä"
(English: "Emergent Workflows in the Video Game Industry: Leveraging AI World Models as a Framework for Production Management")
Jyväskylä University of Applied Sciences (JAMK, 2026)
Permanent URN: URN:NBN:fi:amk-2026052919003


🚀 What's New in PWM (Recent Major Innovations)

PWM has recently integrated state-of-the-art breakthroughs in non-generative self-supervised world models and recursive self-improvement:

1. ⚡ Orthogonal Predictive Factorization (OPF) — JEPA-Anything (arXiv:2609.20800)

Monolithic latent state representations risk entangling conflicting signals. PWM decomposes its 64-dimensional latent project state $\mathbf{s} \in \mathbb{R}^{64}$ into $K=4$ orthogonal factor subspaces of rank $r=16$ ($d = K \times r = 64$) with lossless orthonormal synthesis:

  • Topology ($\mathbf{c}_{\text{topology}} \in \mathbb{R}^{16}$): Graph connectivity, cyclic dependencies, PR-issue blast radius, code churn.
  • Velocity ($\mathbf{c}_{\text{velocity}} \in \mathbb{R}^{16}$): Sprint throughput, commit frequency, cycle time lag, WIP accumulation.
  • Coordination ($\mathbf{c}_{\text{coordination}} \in \mathbb{R}^{16}$): Developer handoffs, communication sentiment, cross-team blockers.
  • Architecture ($\mathbf{c}_{\text{architecture}} \in \mathbb{R}^{16}$): Interface rot, modular coupling, API boundary stability.
  • Guaranteed Geometry: Includes automated Gram matrix audits ensuring $|W W^T - I|_F < 10^{-6}$ for true subspace independence.

2. 🔄 Recursive Self-Improvement (RSI) Engine — RSI-Anything (arXiv:2610.13912)

Embodying the closed-loop cycle $\text{Propose} \to \text{Predict} \to \text{Select} \to \text{Evaluate} \to \text{Learn} \to \text{Retain}$:

  • "Predict-Before-Evaluate" Pre-Screening Filter (Layer 3): Candidate strategies generated by Worker agents are pre-simulated in OPF latent space before incurring LLM critique costs. The system objectively selects the strategy with lowest predicted risk and latent energy ($E = |\mathbf{s}' - \mathbf{s}|_2$).
  • Gated "Retain" Firewall (Layer 4): Enforces an automated 4-stage firewall before any proposal is retained:
    1. Anti-Strategic Dishonesty: Critic agent detects shortcut-taking or hidden complexity.
    2. NVIDIA NemoClaw Sandbox Clearance: Isolated micro-sandbox blocks unauthorized syscalls and privilege escalation.
    3. Latent Risk Tolerance: Rejects any intervention where predicted latent risk exceeds $0.90$.
    4. CRR Economic Budget Ceiling: Vetoes proposals if Compute-to-Rework Ratio exceeds $0.30$ ($\text{CRR} > 0.30$). Vetoed proposals transition to RETAIN_VETOED and are routed to human Scenario Strategists.
  • Factorized Experience Replay Buffer (Layer 2): Rolling 100-step transition buffer tracking factorized grounding errors with online gradient adaptation.

3. 🧠 Gemini 3 Thought Signature Circulation

Upgraded to support Google's Gemini 3 family (gemini-2.5-pro, gemini-2.5-flash, and preview variants) with Thought Signature Preservation, allowing multi-turn debates between Worker, Critic, and Opponent agents to circulate internal reasoning chains without loss of nuance.

4. 🌐 Interactive 3D DTO Garden (Babylon.js Digital Twin)

An interactive 3D spatial digital twin built with Babylon.js and modular low-poly PBR assets:

  • Visual Conflict Mapping: Integration debt appears as weathering boulders, sprint velocity as flowing fountains, and work packages as blossoming foliage.
  • Autonomous AI Gnome Avatars: Real-time obstacle-avoiding agent statues navigating between work sockets with steering separation and deadlock recovery.
  • Dynamic Weather System: Project stress maps directly to 3D weather (sunny clear skies for healthy low-risk sprints vs. stormy overcast skies during critical merge conflicts).
  • Live Mouseover Telemetry: Raycast hover tooltips displaying real-time agent thought states, PR numbers, and risk scores.

5. 📊 Deterministic Flow & Stakeholder Analytics

  • Flow Metrics: Automated Little's Law throughput ($L = \lambda W$), WIP drift analysis, cycle time percentiles, and bottleneck velocity flags.
  • Stakeholder Dynamics: RACI matrix balance scoring, cognitive load indices, and cross-discipline communication friction detection.

6. 🌐 Universal Domain-Agnostic Causal Digital Twin (CDT)

PWM has transitioned from a software-centric model into a 100% domain-agnostic causal world model capable of simulating any dynamic project system (software, residential construction, EPC megaprojects, R&D):

  • Universal Ingestion & Bipartite Hypergraph Inducer (Layer 1): Formulates all production events as $(A, O, P, \mu)$ tuples (ActorNode, ArtifactNode, OperationType), inducing typed bipartite hypergraphs with SHA-256 Merkle chain verification without hardcoded domain semantics.
  • Continuous Latent System Identification ($\mathbf{z}_{\text{env}}$) & Event Clock (Layer 2): Replaces wall-clock time with an intrinsic Riemannian event clock: $$\Delta \tau_k = 1 \iff |\mathbf{s}t - \mathbf{s}{t-1}|2 \ge \theta{\text{flux}} \lor \Delta t > \tau_{\max}$$ and infers four physical invariants: $\mathbf{z}{\text{env}} = (\gamma{\text{rev}}, \kappa_{\text{coupling}}, \tau_{\text{latency}}, \sigma_{\text{exo}})^T$ (reversibility $\gamma_{\text{rev}}$, coupling $\kappa_{\text{coupling}}$, latency $\tau_{\text{latency}}$, and exogenous volatility $\sigma_{\text{exo}}$). Conditioned JEPA transitions strictly preserve the OPF Gram matrix condition $|W W^T - I|_F < 10^{-6}$.
  • Asymmetric Quasimetric Latent Energy & Worst-Case Risk ($\text{CVaR}_{0.95}$) (Layer 3): $$E(\mathbf{s}, \mathbf{s}') = \sqrt{(\mathbf{s}'-\mathbf{s})^T G(\mathbf{z}{\text{env}}) (\mathbf{s}'-\mathbf{s})} + (1 - \gamma{\text{rev}}) \cdot \max(0, \Phi(\mathbf{s}') - \Phi(\mathbf{s}))$$ Symmetric Euclidean distance is maintained for reversible software git operations ($\gamma_{\text{rev}}=1.0$), while irreversible physical construction steps incur non-Euclidean lock-in penalties. Multi-trajectory rollouts rank strategies using Conditional Value at Risk: $$\text{CVaR}{0.95}(L) = \mathbb{E}[L \mid L \ge \text{VaR}{0.95}(L)]$$
  • Neuro-Symbolic Auto-Formalizer Retain Firewall (Layer 4): A deterministic constraint formalizer extracts PRECEDENCE ($t_A \prec t_B$), CAPACITY_LIMIT ($\sum \text{load}i \le L{\max}$), and MUTUAL_EXCLUSION ($\neg(t_A \land t_B)$) constraints from work manifests and verifies satisfiability (Gate 2b) with minimal counterexample traces, vetoing non-conforming strategies before evaluation.
  • Universal Telemetry in 3D DTO Garden (Layer 5): High-resolution telemetry binding rendering low-reversibility boulder scaling ($\gamma_{\text{rev}} < 0.6$) and live hover inspector cards displaying System ID ($\mathbf{z}{\text{env}}$), Quasimetric Energy ($E{\text{quasi}}$), $\text{CVaR}_{0.95}$, and constraint status.

🎨 5-Layer System Architecture

graph TD
    subgraph L1["Layer 1: Ingestion & Observation"]
        Git["Git / GitHub Ingestion"]
        Track["Linear / Jira Backlogs"]
        Comm["Slack / Communication Logs"]
        Merkle["Merkle-Chained Audit Log"]
        Git & Track & Comm --> Merkle
    end

    subgraph L2["Layer 2: Latent Simulation Core"]
        GraphJEPA["Graph-JEPA Topological Encoder"]
        LeJEPA["LeJEPA + SIGReg Regularizer"]
        OPF["Orthogonal Predictive Factorizer (K=4, r=16)"]
        CRR["Compute-to-Rework Engine (CRR)"]
        Calib["WorldModelCalibrator (Trajectory Buffer)"]
        Merkle --> GraphJEPA --> LeJEPA --> OPF
        OPF --> CRR
        OPF --> Calib
    end

    subgraph L3["Layer 3: Agentic Orchestration"]
        WorkerFactory["Worker Agent Factory"]
        Workers["Specialist Agents (QA, Build, Art, General)"]
        PreScreen["Predict-Before-Evaluate Pre-Screening Filter"]
        WorkerFactory --> Workers --> PreScreen
    end

    subgraph L4["Layer 4: Validation & Firewall"]
        Critic["Gemini Critic Agent"]
        Opponent["Dialectical Opponent Agent"]
        NemoClaw["NVIDIA NemoClaw Sandbox"]
        RetainGate{"Gated Retain Firewall"}
        PreScreen --> Critic & Opponent --> NemoClaw --> RetainGate
    end

    subgraph L5["Layer 5: Scenario Strategist Interface"]
        WebDash["FastAPI WebSocket Dashboard"]
        Garden["3D Babylon.js DTO Garden"]
        Human["Human Scenario Strategist (Veto Power)"]
        RetainGate -->|APPROVED| Garden & WebDash
        RetainGate -->|RETAIN_VETOED| Human
    end

    Calib -.->|Feedback Online Learning| L2

Detailed Layer Breakdown

LayerComponentCore Responsibilities
Layer 1: Observationpwm.layers.layer1_observationIngests Git commits, PRs, Linear/Jira tasks, Slack messages, MS Project XML, and universal production telemetry via HypergraphInducer into a unified bipartite dependency graph with SHA-256 Merkle tamper-proofing.
Layer 2: Simulationpwm.layers.layer2_simulationHouses the GraphJEPAEncoder, LeJEPASimulator with SIGReg, OrthogonalPredictiveFactorizer, continuous latent system identification ($z_{\text{env}}$), intrinsic event clock, and WorldModelCalibrator. Computes counterfactual rollouts and tracks CRR budgets.
Layer 3: Orchestrationpwm.layers.layer3_orchestrationDecomposes debt items and runs the AsyncThink protocol. Uses the Predict-Before-Evaluate pre-screening filter with asymmetric quasimetric latent energy and $\text{CVaR}_{0.95}$ risk ranking in latent space before evaluation.
Layer 4: Validationpwm.layers.layer4_validationHosts the multi-agent consensus loop (Critic + Opponent + Artistic Integrity) and executes the Gated Retain Firewall with Gate 2b Neuro-Symbolic deterministic constraint formalization and NemoClaw sandbox isolation.
Layer 5: Interfacepwm.dashboardReal-time WebSocket web dashboard, 3D DTO Garden with System ID & Quasimetric telemetry hover card, CLI terminal HUD, and human-in-the-loop decision routing.

🤖 The Multi-Agent Organization

PWM organizes its AI agents into three specialized functional tiers matching Thesis Kuvio 6 & 7:

                          ┌────────────────────────┐
                          │   Scenario Strategist  │ (Human-in-the-Loop)
                          └───────────┬────────────┘
                                      │ Overrides / Veto
                                      ▼
         ┌─────────────────────────────────────────────────────────┐
         │             Strategic & Flow Orchestration              │
         │  PlannerAgent  │  PortfolioAgent  │  StakeholderAgent   │
         │  ScrumMaster   │  KanbanFlow      │  BudgetGuard        │
         └───────────┬─────────────────────────────────┬───────────┘
                     │ Directives                      │ Audits
                     ▼                                 ▼
┌──────────────────────────────────────────┐   ┌───────────────────────────────┐
│        Specialist Worker Agents          │   │   Dialectical & Quality Guard │
│  MergeConflictWorker  │  QAWorker        │◄──┤  CriticAgent (Gemini 3 Pro)   │
│  BuildWorker          │  ArtIntegration  │   │  OpponentAgent (Devil's Adv)  │
│  GeneralWorkerAgent                      │   │  ArtisticIntegrityAgent       │
└──────────────────────────────────────────┘   └───────────────────────────────┘
  • Worker Agents: Propose concrete code refactors, dependency updates, and branch integrations (qa_agent.py, build_agent.py, art_agent.py).
  • Critic Agent: Detects logical flaws, anti-patterns, and strategic dishonesty (agents hiding bugs to pass CI).
  • Opponent Agent: Dialectical devil's advocate challenging every proposal with worst-case scenario testing.
  • Artistic Integrity Agent: Enforces visual and creative fidelity in creative and gaming software projects, ensuring AI optimizations do not strip human aesthetic soul.
  • Budget Guard Agent: Monitors API token consumption and token-per-watt efficiency to prevent runaway expenses.

💰 Economic Justification: CRR Economics

A central tenet of the PWM framework is economic discipline. AI agents must never cost more than the human rework they prevent. PWM continuously computes the Compute-to-Rework Ratio (CRR):

$$\text{CRR} = \frac{\text{Total AI Inference Cost (€)} + \text{Infrastructure & GPU Cost (€)}}{\text{Estimated Human Developer Rework Saved (€)}}$$

  • $\text{CRR} < 0.10$: Exceptional efficiency (AI is 10x+ cheaper than manual firefighting).
  • $\text{CRR} \le 0.30$: Target operating budget envelope.
  • $\text{CRR} > 0.30$: Layer 4 Retain Firewall veto triggered (FAILED_CRR_BUDGET).
  • $\text{CRR} \ge 1.00$: Jevons Paradox Alert — autonomous execution halted; requires explicit human executive override.

⚡ Model Serving & Hybrid Cloud Architecture

PWM uses a cost-optimized Hybrid Serverless + On-Demand GPU topology:

┌────────────────────────────────────────┐       ┌───────────────────────────────────────┐
│          Google Cloud Run              │       │       Google Compute Engine (GCE)     │
│       (Serverless Orchestration)       │       │            (On-Demand GPU VM)         │
│                                        │       │                                       │
│  • Web Dashboard & 3D DTO Garden       │ HTTP  │  • GraphJEPA Server (:8001)           │
│  • Layers 1, 3, 4, 5 Execution         ├──────►│  • JEPA World Model Server (:8000)    │
│  • Vertex AI Gemini 3 Gateway          │       │  • PointJEPA 3D Server (:8002)        │
│  • Scale-to-Zero (--min-instances=0)   │       │  • NVIDIA NemoClaw Sandbox (:8008)    │
└────────────────────────────────────────┘       └──────────────────┬────────────────────┘
                                                                    │
                                                 Automated Auto-Shutdown on Idle
  • Cloud Run Scale-to-Zero: Containerized orchestration scale-to-zero (--min-instances=0) when no active users are connected, avoiding idle hosting charges.
  • On-Demand GPU Lifecycle: run_gpu_pipeline.py starts the GPU VM via GCP API, waits for health checks, processes batched embeddings, and guarantees shutdown in a finally block.
  • Semantic Vertex AI Fallbacks: If the GPU VM is offline, PWM seamlessly falls back to Gemini Pro/Flash semantic simulation with zero downtime.

💻 Quick Start & Local Execution

1. Prerequisites & Installation

# Clone the repository
git clone https://github.com/petripaananen/Project-World-Model.git
cd Project-World-Model

# Setup Python virtual environment
python -m venv .venv
source .venv/Scripts/activate  # Windows: .venv\Scripts\activate

# Install dependencies
pip install -r requirements.txt

2. Environment Configuration

Create a .env file in the project root:

GOOGLE_API_KEY=your_gemini_api_key
GCP_PROJECT_ID=your-gcp-project-id
GCP_LOCATION=us-central1
NEMOCLAW_ENDPOINT_URL=http://localhost:8008/audit
JEPA_WM_ENDPOINT_URL=http://localhost:8000

3. Execution Commands

  • Run Interactive 3D DTO Web Dashboard (Recommended):

    python -m pwm.main --web --port 8765
    

    Open http://localhost:8765 to view the live dashboard and Babylon.js 3D Garden.

  • Run CLI Demo Mode (Fully deterministic, no API keys required):

    python -m pwm.main --mode demo
    
  • Run Live Gemini 3 Agent Analysis:

    python -m pwm.main --mode analyze
    
  • Run Continuous 24h Autonomous Loop:

    python -m pwm.main --loop --interval 300
    
  • Simulate Specific Pre-Built Scenarios:

    • Scenario 1 (Causal Counterfactual Simulation): python -m pwm.main --scenario 1
    • Scenario 2 (NemoClaw Sandbox Veto): python -m pwm.main --scenario 2
    • Scenario 3 (CRR Budget Alert & Jevons Defense): python -m pwm.main --scenario 3
  • Start the Standalone JEPA Model Serving Cluster:

    python -m pwm.serving.runner --all
    

🧪 Automated Test Suite

PWM enforces a strict pre-deployment testing rule: all release commits must pass 100% of local unit and integration tests.

pytest tests/

Test Coverage (81 Passed / 0 Failures):

  • test_rsi_integration.py: Validates Layer 3 Predict-Before-Evaluate selection, Layer 4 Retain Gate veto conditions (dishonesty, sandbox, energy, CRR), and closed-loop trajectory recording.
  • test_jepa_core.py: Asserts GraphJEPA topological embeddings, LeJEPA SIGReg regularization, and OPF Gram matrix orthonormality.
  • test_calibration.py: Asserts self-supervised calibration factor updates, factorized grounding errors, and trajectory persistence.
  • test_new_agents.py: Validates Worker, Critic, Opponent, and specialized agent consensus workflows.
  • test_security_adversarial.py: Validates SAIF security posture, prompt injection resistance, and NemoClaw isolation.
  • test_budget_and_loop.py: Validates CRR calculations, token budget enforcement, and debate loops.
  • test_agile_integration.py: Tests deterministic Agile metrics (velocity, lead time, RACI, DoD compliance).
  • test_model_serving.py: Tests FastAPI JEPA microservice endpoints (/simulate, /encode-graph, /audit-geometry).
  • test_gcp_config.py: Verifies GCP configuration loading, GCE lifecycle management, and semantic fallbacks.
  • test_jira_ingest.py & test_linear_ingest.py: Tests real-world issue tracker adapters.
  • test_ftue_parsers.py: Verifies MS Project XML and Slack export parsers.

📚 Academic Citation & References

If you use or build upon the Project World Model framework in your academic research or enterprise engineering, please cite:

@mastersthesis{paananen2026pwm,
  author       = {Petri Paananen},
  title        = {Itseohjautuvat työnkulut videopeliteollisuudessa: tekoälyn maailmanmallit tuotannon johtamisen viitekehyksenä},
  school       = {Jyväskylä University of Applied Sciences (JAMK)},
  year         = {2026},
  type         = {Master's Thesis},
  url          = {https://urn.fi/URN:NBN:fi:amk-2026052919003}
}

Key Literature & Architecture References:

  1. RSI-Anything: Gen-Verse (2026). RSI-Anything: Learning to Self-Improve World Models and Policies through Gated Retention. arXiv:2610.13912.
  2. JEPA-Anything: Gen-Verse (2026). JEPA-Anything: Learning Predictive Models across Different Worlds. arXiv:2609.20800.
  3. LeJEPA: Balestriero, R., & LeCun, Y. (2025). LeJEPA: Provable and Scalable Self-Supervised Learning Without Heuristics. Meta AI Research.
  4. Google SAIF: Secure AI Framework: Standards for Agentic Risk Mitigation. Google Cloud Security.

📄 License

This project is licensed under the Apache License, Version 2.0. See the LICENSE file for details.

↑↓ navigate openesc close