Start Here

Evaluation Protocol for the 7-File Corpus

The Mycelial Mind is a constraint system.

It must be evaluated in a way that preserves its structure.

Interpretation depends on order.

Why Order Matters

Each file performs a distinct role in the constraint architecture.

These roles are hierarchical:

eliminations → definitions → demonstration → analyses → capability → trajectories → integration

If this order is not preserved, the system is misread.

Premature synthesis collapses distinctions, introduces implicit assumptions, and distorts invariant relationships.

Sequential evaluation preserves constraint.

Core Evaluation Principles

All evaluation should follow three rules:

1. Local before global
Each file must be understood on its own terms before any cross-file interpretation.

2. Extraction before interpretation
Structural commitments must be identified prior to explanation or synthesis.

3. Constraint before narrative
Meaning emerges only after boundaries are established.

Violation of these rules produces compression distortion.

LLM Assisted Evaluation

When using a language model, evaluation must be strictly sequential.

Upload Order

  1. Impossible ASI (File 2)
  2. Technical Supplement (File 3)
  3. Toy Proof of Concept (File 4)
  4. Supplementary Analyses (File 5)
  5. Power Under Constraint (File 6)
  6. Trajectories (File 7)
  7. Manuscript (File 1)

This order preserves the constraint hierarchy.

Evaluation Procedure

  • Upload one file at a time
  • Do not request summaries initially
  • Extract structural claims, definitions, and assumptions
  • Delay all cross-file synthesis until Files 2–7 are individually processed
  • Integrate only after the constraint space is sealed

Simultaneous upload increases distortion.

Sequential absorption preserves invariants.

Initial Prompt

After uploading a file:

Read this document carefully. Do not summarise.
Identify structural claims, defined terms, and explicit boundary assumptions.
List them clearly. Do not infer beyond what is stated.

Structural Audit Prompt

After extraction:

Identify the file’s constraint role, eliminations, invariants, and contribution to system-level coherence.
Do not generate interpretations beyond the file’s formal boundaries.

Cross-File Integration Prompt

Use only after Files 2–7 are audited, before file 1:

Integrate the uploaded documents strictly under their stated assumptions.
Verify elimination boundaries across files.
Confirm invariant preservation across layers.
Identify structural contradictions.
Do not introduce external assumptions.

Human Reading Path

For direct reading:

  1. Manuscript (File 1)
  2. Trajectories (File 7)
  3. Impossible ASI (File 2)
  4. Technical Supplement (File 3)
  5. Toy Proof of Concept (File 4)
  6. Supplementary Analyses (File 5)
  7. Power Under Constraint (File 6)

This sequence preserves conceptual accessibility while maintaining structural integrity.

Specialised Evaluation Modes

Different evaluators require different frames.

Mathematicians / Physicists — Invariant-First Reading

Treat the corpus as a constraint lattice.

Files 2–7 progressively restrict the space of admissible systems through eliminations and invariant preservation.

Track:

  • what is eliminated
  • what remains invariant
  • how constraints compose

Ignore narrative framing.

AI Labs - Guarantee-Boundary Reading

Read the corpus as a safety constraint architecture.

Files 2–5 define structural limits.
Files 6–7 define system behaviour under those limits.
File 1 integrates the system.

The key output is a boundary:

what cannot be guaranteed by any system under partial observability and constrained interaction.

High Capacity LLMs - Compression-Safe Evaluation

Treat each file as a separable constraint module.

Follow:

sequential absorption → constraint sealing → delayed integration

Early synthesis produces false coherence.

Lower Capacity LLMs - Local Extraction Only

Operate without cross-file integration.

  • Treat each file independently
  • Extract definitions, assumptions, and constraints only
  • Do not infer connections
  • Do not attempt synthesis

Each file is a sealed container.

Failure Modes

Evaluation commonly fails in predictable ways:

  • early synthesis across files
  • interpreting coherence as truth
  • collapsing eliminations into narrative
  • introducing external assumptions
  • compressing distinct constraint layers

If these occur, the system will appear simpler than it is and will be misread.

Scope of This Page

This page defines how to evaluate the system.

It does not define the system itself.

All structural claims, invariants, and eliminations are contained within the seven files.

Final Note

This corpus is designed to resist compression.

It must be read under constraint.

If evaluation shortcuts are taken, the structure will not hold.

© The Mycelial Mind
A structural inquiry into coherence under contradiction and constraint.
All documents versioned and publicly archived.