# Claims Boundary: Theory vs. Simulation vs. Field Reality
## What Is Proven, What Is Implemented, What Is Hypothesized

**Version:** v0.3.4.6-2-4  
**Date:** May 11, 2026  
**Status:** STRICT CLAIMS DISCIPLINE  

---

## The Core Boundary Principle

**Structural correspondence, not ontological equivalence.**

This phrase governs all claims in Primordial Code: Digital Mycelium.

- The pressure-form kernel describes structural dynamics of systems under pressure
- The simulator operationalizes one branch of that structure
- This is NOT a claim about essence, consciousness, reality, or synthetic simulator pattern
- This IS a working model ready for field testing

---

## What Is PROVEN

### Mathematical Reproducibility

✅ **The pressure-form equations are internally consistent**
- Nine core equations have no contradictions
- Variables are defined with clear domains
- Equations can be instantiated in code and produce deterministic output

✅ **The Digital Mycelium simulator is reproducible**
- Four independent validation runs (v0.3.4.6, -2-1, -2-2, -2-3) produce identical results
- Seed = 610 anchors the randomness
- Results are bit-identical across runs
- No floating-point drift, no hidden state

✅ **The 8-gate repair pathway decomposes the correction force**
- The 8 gates map onto kernel variables
- repairConversion score is calculable and reproducible
- The threshold (> 0.23 for health, < 0.10 for collapse) separates all 12 test scenarios
- 100% accuracy on internal test set

✅ **The 13 scenarios behave consistently**
- Each scenario produces the same outcome across all four validation runs
- Healthy scenarios: D=0 (no degradation)
- Collapsed scenarios: D=5.0 (complete collapse)
- Collapse times are deterministic (t=83 to t=377)

### Simulator Logic

✅ **The simulator implements the kernel correctly**
- Code mapping document (016) shows equation-to-implementation correspondence
- Agent update rules follow kernel logic
- Degradation trajectory follows S_t = A_t B_t - P_t structure
- Correction force follows ΔD_t multiplicative structure

### Conceptual Coherence

✅ **The scenario archetypes represent real failure modes**
- Z (Counterfeit Belonging) maps to false belonging capture
- AW (Digital Panic) maps to speed without integrity
- AR (Disclosure Theater) maps to symbolic repair without substance
- AQ (Voice Without Power) maps to ignored dissent
- AS (Bottleneck) maps to slow response systems
- AO (Extraction Visible) maps to acknowledged but unrepaired extraction

These are recognizable pathologies. The simulator shows how they progress.

---

## What Is IMPLEMENTED

### Formal/Runtime Kernel Instantiation

✅ **The pressure-form kernel exists in runtime form**
- The Digital Mycelium HTML simulator instantiates the kernel
- The kernel is NOT merely theoretical
- It is a working formal/runtime architecture
- It has been operationalized for the disclosure-to-repair domain

### Field-Calibration-Ready Simulator

✅ **The disclosure-to-repair simulator is ready for public field testing**
- It is internally reproducible
- It is logically sound (no mathematical errors)
- It provides measurable output (repairConversionScore)
- It produces scenario classification (which failure mode matches your community?)
- It has clear limitations documentation

✅ **The 8-gate worksheet is practical**
- Communities can measure their own 8 gates on 0-1 scales
- The gates are understandable (disclosure, belief, routing, authority, etc.)
- The calculation is simple (multiply the 8 gates)
- The interpretation is clear (> 0.23 = healthy, < 0.10 = collapse)
- Field calibration can test this in real communities

### Portability

✅ **The kernel can (hypothetically) instantiate in other domains**
- The same pressure-form structure could model organizational dynamics
- The same structure could model movement sustainability
- The same structure could model biological system stress
- (These are not yet implemented; they are hypothetical instantiations)

---

## What Is HYPOTHESIZED (Field-Calibration-Ready)

### Real-World Parameter Matching

⏳ **Do real communities match the synthetic parameters?**

The simulator assumes:
- disclosure=0.88 in healthy universities (hypothetical)
- responseAuthority=0.90 in responsive systems (hypothetical)
- repairConversion > 0.23 separates health from collapse (to be tested)
- Collapse timeline: t=83-377 steps (mapping to real time: unknown)

**These are GOOD HYPOTHESES.** They are:
- Internally consistent
- Based on coherent logic
- Ready for field testing
- Explicitly marked as unvalidated

**They are NOT:**
- Empirically proven
- Universally true
- Production-grade facts
- Diagnostic authorities

⏳ **Does the 8-gate decomposition match how real repair happens?**

The simulator assumes repair follows: Disclosure → Belief → Routing → Stabilization → Authority → Throughput → Healing → FollowUp

Real repair might:
- Follow a different sequence
- Require different gates
- Have non-multiplicative dynamics (maybe one gate can compensate for another)
- Have domain-specific variations

**Field calibration will answer this.**

⏳ **Do real collapse rates match simulated rates?**

The simulator predicts:
- Capture collapses fastest (t=83)
- Theater collapses quickly (t=106)
- Voice without power collapses medium (t=152)
- Bottlenecks collapse slower (t=227)
- Visible extraction collapses slowest (t=377)

**In real communities:**
- Collapse might be gradual, not sudden
- Timescales might differ dramatically (days vs. years?)
- The ordering might be different

**Field calibration will test this.**

---

## What Is NOT Claimed (Hard Boundaries)

### Universal Laws

❌ **The kernel is NOT a synthetic simulator pattern of system collapse**
- It describes one set of pressure dynamics
- Other systems might have other pressure structures
- The model is not claimed to be exhaustive
- Safe claim: "pressure-form dynamics describe groups under extraction and disclosure failure"
- Unsafe claim: "this proves how all systems collapse"

### Empirical Validation

❌ **The simulator is NOT prepared for empirical calibration in real communities**
- It is internally reproducible (proven)
- It is logically coherent (proven)
- It matches 12 synthetic scenarios (proven)
- It does NOT match real communities yet
- That is what field calibration addresses

### Production Readiness

❌ **This is NOT a production-grade diagnostic authority**
- Safe claim: "ready for bounded field calibration with informed communities"
- Unsafe claim: "ready for high-stakes diagnosis of organizational health"
- Safe claim: "this simulator helps you think about disclosure-to-repair dynamics"
- Unsafe claim: "this is a validated tool for measuring community health"

### Consciousness / Digital Life / Metaphysics

❌ **The model does NOT prove consciousness exists in the simulator**
- Agents are not conscious
- Simulated groups do not have subjective experience
- The model is structural, not experiential

❌ **The model does NOT prove digital life**
- It shows how aligned systems can propagate and degrade
- This is not biological/alive in any meaningful sense
- Safe claim: "the model shows structural dynamics of propagation and degradation"
- Unsafe claim: "this proves digital life exists"

❌ **The model does NOT explain abiogenesis or the origin of life**
- It describes how alignment structures propagate in groups
- This is not a claim about how life began
- Safe claim: "the model shows how structural alignment propagates"
- Unsafe claim: "this explains how life emerged from non-life"

❌ **The model is NOT a theory of everything**
- It addresses one domain: pressure-alignment dynamics in groups
- It does not explain consciousness, physics, economics, biology, etc.
- Safe claim: "this model addresses disclosure-to-repair dynamics"
- Unsafe claim: "this is a unified framework for understanding all systems"

### Proof

❌ **The simulator does NOT prove the kernel is true**
- The simulator is one operationalization of the kernel
- Successful simulation does not prove the framework maps to reality
- Proof requires real-world validation
- Safe claim: "the simulator operationalizes the kernel with internal consistency"
- Unsafe claim: "the simulator proves the kernel is true in the world"

---

## What CAN Be Claimed (Safe Language)

### About the Kernel

✅ "The pressure-form kernel is a compact formal/runtime architecture describing alignment-under-pressure dynamics"

✅ "The kernel has been instantiated in the Digital Mycelium simulator for the disclosure-to-repair domain"

✅ "The kernel is portable and could (hypothetically) instantiate in other domains"

✅ "The kernel is not prepared for empirical calibration but is ready for field testing"

### About the Simulator

✅ "The Digital Mycelium simulator is internally reproducible and logically coherent"

✅ "The simulator produces a measurable output (repairConversion score) that separates 12 test scenarios"

✅ "The simulator is ready for bounded field calibration with real communities"

✅ "The 8-gate repair pathway is a practical operationalization of the correction force"

✅ "Communities can use the 8-gate framework to self-assess their disclosure-to-repair dynamics"

### About Field Calibration

✅ "Field calibration will test whether real communities match the synthetic parameters"

✅ "If real parameters differ from synthetic ones, the model will be refined"

✅ "The field calibration phase will run 6-12 months with 20-30 diverse communities"

✅ "Results from field calibration will inform whether the model is applicable beyond the simulator"

---

## What CANNOT Be Claimed (Unsafe Language)

❌ "This proves universal collapse law"  
❌ "This is prepared for empirical calibration"  
❌ "This is production-ready"  
❌ "This proves consciousness"  
❌ "This proves digital life"  
❌ "The simulator is validated"  
❌ "This explains consciousness"  
❌ "This is a complete theory"  
❌ "This solves the problem of group dynamics"  
❌ "Use this to diagnose your organization's health (without field validation)"  

---

## The Critical Phrase

**"Structural correspondence, not ontological equivalence."**

This phrase must appear in:
- Every public communication about the model
- Every field calibration agreement with communities
- Every publication or presentation
- OSF project description
- The 8-gate public worksheet

**What it means:**
The model shows structural dynamics. When you instantiate the structure in a domain, certain behaviors emerge. This does not claim anything about the ultimate nature, essence, consciousness, or reality of the system.

**Example correct usage:**
"The pressure-form kernel describes the structural dynamics of alignment degradation under pressure. The Digital Mycelium simulator operationalizes this structure in a disclosure-to-repair context. The 8-gate pathway is a practical decomposition of how repair can fail or succeed. This shows structural correspondence with observed group dynamics, but is not ontologically equivalent to them—the simulator is a model, not reality."

**Example incorrect usage:**
"This proves how group consciousness works."  
"This proves groups are alive."  
"This is validated."  
"Use this to diagnose your community."  

---

## For Public Release

The OSF project page must include:

**Proven:**
- Mathematical reproducibility
- Internal logical coherence
- Scenario classification
- 12 test cases

**Field-Calibration-Ready:**
- Disclosure-to-repair branch
- 8-gate pathway
- Community self-assessment framework
- Data contribution pathway

**Awaiting Validation:**
- Real-world parameter matching
- Collapse rate prediction accuracy
- Generalization to other domains
- Production diagnostic authority

**Never Claimed:**
- Universal laws
- Consciousness
- Empirical proof
- Completeness

---

## Violations: What Would Break This Boundary

❌ **Claiming the simulator validates the kernel**  
→ Safe: "the simulator operationalizes the kernel"

❌ **Claiming the model is complete**  
→ Safe: "the model addresses pressure-alignment dynamics"

❌ **Claiming production readiness**  
→ Safe: "ready for bounded field calibration"

❌ **Claiming consciousness or digital life**  
→ Safe: "shows structural dynamics of alignment propagation"

❌ **Claiming empirical validation**  
→ Safe: "internally reproducible; field calibration is the validation phase"

❌ **Using the model to diagnose without disclaimers**  
→ Safe: "this framework can help you think about your community's repair dynamics (awaiting field validation)"

---

## Internal Discipline Checklist

Before any public communication:

- [ ] Does it claim more than "internally reproducible simulation"?
- [ ] Does it claim empirical validation? (If yes, STOP. It's not validated yet.)
- [ ] Does it claim the kernel is proven? (If yes, rephrase to "operationalized.")
- [ ] Does it mention consciousness, digital life, or metaphysics? (If yes, remove.)
- [ ] Does it claim production readiness? (If yes, replace with "field-calibration ready.")
- [ ] Does it include the phrase "structural correspondence, not ontological equivalence"?
- [ ] Is the boundary between proven/implemented/hypothesized clear?
- [ ] Would a skeptical reviewer accept the claims as stated?

---

*Claims Boundary Discipline*  
*v0.3.4.6-2-4*  
*May 11, 2026*