Back to corpus
architecturetechnical paper candidatescore 28

Stage 0: RESEARCH — AutoMesh Self-Healing Architecture

``` [ROOT] AutoMesh Self-Healing ├── [D1] Code-Level Healing (self-healing-code/) │ ├── healer.py (1580 lines, Gen 6-7) │ │ ├── Wound/Antibody/ImmuneMemory (SQLite, reactive) │ │ ├── HealingStrategies (5: null_coalesce, type_coerce, key_fuzzy, index_bounds, retry_backoff) │ │ ├── CellularRegeneration (Gen 6, AST scan, 6 vuln patterns, fortify) │ │ └── WatchMode (Gen 7, file polling, VitalityTimeline, auto-fortify) │ └── KEY: Local-only. No cross-machine propagation. │ ├── [D1] Mesh Coordination (mesh-node-agent/) │

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

### 1. Two Immune Systems, Not Connected - **EW immune.py**: 4-tier quarantine for evolution techniques (G/R/D), sliding window, exploration burst - **Healer ImmuneMemory**: wound/antibody pattern matching for Python runtime errors - **Gap**: These operate independently. EW immune handles evolution process health; healer handles code execution health. Neither covers infrastructure fault tolerance. ### 2. EW4 Invariants Already CALC-Aware - `check_min_entropy_production` accepts `calc_results` param, boosts novelty from cross-agent discoveries - `check_bounded_divergence` accepts `calc_pending_count`, factors pending dispatches into divergence pressure - This means the invariant framework is designed for multi-agent coordination already ### 3. Feedback Metabolism = Heartbeat Speed Control - `feedback.py` computes metabolism (0.0-1.0) from signal freshness/diversity/volume - High metabolism → fast heartbeat → aggressive exploration - Low metabolism → slow heartbeat → conservative refinement - This is directly portable to mesh: machine metabolism from task success rate / pane utilization / failure diversity ### 4. Cross-Layer Forcing Has Dream Storm Hook - `forcing.py::handle_dream_storm()` already handles external event injection - This is the pattern for injecting mesh events: rate limit hits, cascading failures, machine dropouts ### 5. Missing Layer: Mesh-Level Immune System The EW immune system (4-tier quarantine) operates on evolution techniques. Need an equivalent operating on: - Machines (quarantine a flaky machine) - Panes (quarantine a crashing pane) - Task types (quarantine prompts that consistently fail) - Accounts (quarantine rate-limited Claude accounts)

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.