Seven Files

The Constraint Architecture

The Mycelial Mind is structured as 7-file constraint system.

Each document performs a distinct role.
No single file contains the full system.

Together, they form a closed, testable architecture.

How to Use This Page

• Download individually
• Evaluate sequentially (see Start Here)
• Interpret under constraint

The system is designed to be independently testable.

You are not required to trust the author.

The Seven Files

1 - Manuscript

Conceptual integration and provenance

This document integrates the system once its structural components are understood.

It provides:

• origin of the framework under contradiction
• conceptual synthesis across files
• interpretation of the full architecture

It does not introduce new technical claims.

Role: Integration layer
Best read: Last

2 - Impossible ASI

Structural ceiling on guarantees

This file establishes a hard boundary:

Under partial observability, certain guarantees cannot be made for any deployed system.

It defines:

• indistinguishability limits
• constraint boundaries on verification
• conditions under which guarantees fail

This is not a prediction.

It is a limit on what is structurally possible.

Role: Boundary layer
Function: Fixes the constraint space

3 - Technical Supplement

Audit layer - definitions, certificates, observables

This is the enforcement spine of the system.

It introduces:

• certificate-grounded refusal (“Healthy No”)
• CTQ observables (stability under contradiction)
• artifact-based evaluation (logs, traces, failure cases)

All claims must reduce to checkable artifacts, not interpretation.

Failures are recorded, not hidden.

4 - Toy Proof of Concept

Minimal executable system

This file provides the smallest working system in which the framework becomes observable.

It demonstrates:

• deterministic contradiction handling
• CTQ-based regime separation
• full audit pipeline: input → logs → metrics → classification

All outputs are:

• explicit
• reproducible
• falsifiable

Key property

You can run this yourself and observe:

• whether regimes separate
• whether CTQ behaves as claimed
• whether the system fails under controlled conditions

If it fails, the hypothesis is falsified.

Role: Minimal evidence layer
Barrier to entry: Low
Purpose: Immediate empirical testing

5 - Supplementary Analyses

Stress-testing and compression discipline

This file tests whether the system survives:

• domain translation
• abstraction pressure
• vocabulary shifts

It applies the same structural grammar across domains without expanding scope.

Key property

If the structure breaks under translation, it is not stable.

This file ensures:

• no hidden assumptions
• no ontology drift
• no narrative inflation

Role: Robustness layer
Function: Pressure-testing the system

6 - Power Under Constraint

Capability under structural limits

This file redefines power:

Not as output, but as reachable capability under constraint.

It shows:

• how constraint shapes capability
• why “more optimisation” is not sufficient
• how fragility emerges under pressure

No new primitives are introduced.

Role: Geometry / consequence layer
Function: Re-frame capability under limits

7 - Trajectories

Long-horizon behavioural classification

This file closes the system across time.

It classifies:

• long-run system behaviours
• regime transitions
• failure modes under constraint

It does not predict.

It classifies what remains possible under the established constraints.

Role: Temporal closure layer
Function: Explain behaviour over time

System Properties

Across all seven files:

• No claim depends on author authority
• No component requires belief
• All critical elements are either:
  • provable, or
  • testable, or
  • falsifiable

The system is designed so that:

validation can occur without contacting the creator

Where to Start

• Start Here - evaluation protocol
• Technical Supplement + Toy PoC - fastest path to testing
• Seven Files (full set) - complete architecture
• About - origin and posture

Final Note

This is not a collection of papers.

It is a constraint system.

Each file removes a failure mode that another file could not eliminate alone.

The system should be evaluated the same way it was built:

under constraint, under pressure, and without assumption.

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