Usage instructions

What this is?

A structural reading tool. Not a belief system. Not a predictive oracle. Not a replacement for disciplinary expertise.

Use it accordingly.

Quick Hack 

Import the framework page and the Foundations essays into a new AI chat and ask questions about whatever you're trying to understand. The framework gives the AI a shared vocabulary that makes cross-domain reasoning more precise. Use scepticism throughout — poke holes, question assumptions, don't accept the first answer.

Start With the Board

Before asking why something evolved, exists, or failed — ask what the board looked like first.

• What are the constraints?

• What is limited?

• What is abundant?

• What gradients exist?

• What is the time scale?

• What is the disturbance frequency?

Do not start with outcome. Start with pressure.

If you cannot identify constraints, you are guessing.

Follow the ledger

Every structure represents a cost. Something was invested in. Something was abandoned. Something was traded off.

Ask: 

• what strengthened? 

• What weakened? 

• What was abandoned? 

• What is being paid for continuously and what only runs on reserves?

Living systems operate on open ledgers.

Non-living systems operate on threshold physics.

• What can only be afforded seasonally?

• What shuts down when payment fails?

• What runs on stored reserves?

If nothing was abandoned, you are not looking closely enough. If you cannot locate the cost, you have not understood the structure.

Separate Constraints From Editors

Constraints limit what is possible. Editors determine what persists.

Gravity is a constraint. Predation is an editor.

Temperature range is a constraint. Freeze–thaw cycling is an editor.

Confusing these collapses clarity immediately.

Read Absence as Carefully as Presence

What is missing often tells you more than what is visible.

• Why no vision upgrade?

• Why no migration?

• Why no gigantism?

• Why no diversification?

• Why no armour?

Absence is structural information. Ask why the board stopped paying for something.

Watch for Lock-In

Specialization improves performance and removes escape routes simultaneously. Extreme optimization for one board condition increases collapse risk when the board shifts.

Extreme specialization often means:

• Reduced elasticity

• Reduced negotiation capacity

• Increased collapse risk under board shift

Ask:

• Is this feature elastic?

• Or is it rigid and dependent on stable conditions?

Do Not Anthropomorphize

Boards do not decide.

Editors do not intend.

Evolution does not plan.

Remove intention unless it is actually present in the system being analyzed. Intent only applies where intent actually exists (e.g., human systems).

Do Not Overgeneralize

The framework reveals patterns. It does not guarantee universality.

If an example does not fit:

• Stress test it.

• Refine definitions.

• Adjust hinge placement.

Do not force-fit reality into the framework.

This Is a Reading Tool, Not a Crystal Ball

Memory Prism does not predict specific outcomes.

It:

• Narrows outcome space.

• Reveals pressure directions.

• Highlights trade-offs.

Experts within disciplines do predictive modeling. This framework provides structural orientation.

Stress Test Everything

The framework was built adversarially.

Use it adversarially.

Ask:

• Where does this break?

• What assumption is hidden?

• What budget was ignored?

• What scale mismatch exists?

If it survives stress testing, keep it.

If it fails, refine it.

Cross Scales Carefully

Boards are nested.

A system can:

• Succeed locally

• Fail at higher scale

Do not evaluate survival at only one scale. Short-term stability is not long-term viability.

Stable for now is the operating principle.

Do Not Treat It as Sacred

The framework will change.

• Because boards change.

• Because new data emerges.

• Because refinements are inevitable.

If you treat it as doctrine, you have misunderstood it.

What This Framework Is For

It is for:

• Reducing disciplinary friction

• Identifying structural similarities across fields

• Asking sharper questions

• Seeing trade-offs faster

• Lowering cognitive load when entering new domains

It is not for:

• Winning arguments

• Replacing textbooks

• Predicting the future

• Explaining everything

Final Reminder

Every structure is a receipt. Every receipt reflects pressure.

Read the pressure.

Author's note : using the framework with AI requires scepticism. You can't take data provided at face value, you need to poke it, jab it from various angles, what assumptions is AI making, are they true, does AI understand the geometry of said assumptions (this has been my biggest problem while understanding a topic, AI makes basic assumptions, does not understand the implications of assumed origins). Even though I have spent a lot of time with AI making the framework, understanding a lot of things using the framework, AI for me is still a delegation tool which process raw data into an easy readable conversational mode, I am still asking the questions, poking and jabbing holes in flows and assumptions provided.