naturepedia
MCP serverSearchYour AI can search and resolve canonical resources from Naturepedia, Robbie's Razor, and GC-MRD-v2.0 once this integration is added. It can look up entries across all three collections and return the canonical version of a resource.
Use naturepedia in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add naturepedia and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the about naturepedia tool from naturepedia
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
Details
Available today. Use it from your connected AI after setup.
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
Add the integration, then ask your AI to search for or resolve a resource from Naturepedia, Robbie's Razor, or GC-MRD-v2.0.
What your AI can do with it
- Search Naturepedia resources
- Look up Robbie's Razor entries
- Find GC-MRD-v2.0 resources
- Resolve a resource to its canonical version
- Search all three collections from one place
Install naturepedia
The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user naturepedia 'https://mcp.robbiegeorgephotography.com/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://mcp.robbiegeorgephotography.com/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=naturepedia&config=eyJ1cmwiOiJodHRwczovL21jcC5yb2JiaWVnZW9yZ2VwaG90b2dyYXBoeS5jb20vbWNwIn0=Open the link and Cursor adds the server at that address.
ChatGPT
https://mcp.robbiegeorgephotography.com/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add naturepedia --url 'https://mcp.robbiegeorgephotography.com/mcp'Run it once, then sign in with codex mcp login naturepedia if the server asks for an account.
From the project's README
As published by robbierazor/robbies-razor-benchmarks in README.md.
Run a Razor Audit
Evaluate any AI system using Robbie George’s Grand Compression Cosmology:
Reference implementation and benchmarking framework for evaluating Robbie’s Razor compliance, recursive stability, and compression efficiency in reasoning systems operating under constrained compute, memory, and governance bandwidth.
System Architecture Overview
This repository supports Robbie’s Razor™, Naturepedia™, and Plate™ systems as part of a recursive ecological knowledge architecture combining:
- semantic compression
- machine-readable provenance
- recursive relationship mapping
- ecological intelligence architecture
- structured retrieval systems
- low-token semantic traversal
Core reasoning sequence:
compression → expression → memory → recursion
Key concepts: Robbie’s Razor · Grand Compression Cosmology · Recursive Stability · Compression Efficiency · Reasoning Benchmarks
Grand Compression Law of Intelligence
Within the Grand Compression Cosmology, intelligence is modeled through the reuse of preserved compressed structure across recursive cycles under finite resource and stabilization constraints.
The framework proposition can be summarized as:
preserved structure
→ expression
→ memory
→ recursive reuse
→ prediction / adaptation
The core Robbie’s Razor™ sequence is:
compression → expression → memory → recursion
This sequence is a framework architecture.
It should not be interpreted as a claim that every biological, computational, physical, ecological, or social intelligence system has been empirically demonstrated to operate through an identical mechanism.
Accordingly:
Grand Compression framework proposition
≠
universally established law of intelligence
and:
recursive reuse
≠
automatic intelligence
A system must still be evaluated according to its declared task, preserved structure, prediction quality, correctness, resource constraints, and failure conditions.
Recursive Constraint Model
Within the framework, recursive performance may be analyzed using two conceptual constraint classes:
- Energetic Recursion Ceiling — the available energetic budget relative to the cost of coherent transitions;
- Governance Recursion Ceiling — the available stabilization or correction capacity relative to correction demand.
A conceptual energetic ceiling may be written as:
R ≤ E / JCT
A conceptual governance ceiling may be written as:
R × C ≤ S
Combining the two produces the framework-level Safe Recursion Envelope:
R ≤ min(E / JCT, S / C)
Where:
- R = recursion rate;
- E = available energy within the declared system boundary;
- JCT = Joules per Coherent Transition;
- S = available stabilization or governance bandwidth;
- C = correction demand per transition.
These expressions are architectural research relations.
Quantitative application requires operational definitions for every variable, compatible units, measurement procedures, system boundaries, baselines, uncertainty, and falsification conditions.
Without those declarations:
R ≤ E / JCT
R × C ≤ S
and:
R ≤ min(E / JCT, S / C)
must not be represented as universally validated physical laws.
Intelligence Interpretation Boundary
The framework motivates the hypothesis that useful intelligence may depend not only on computation, but on the ability to preserve and recursively reuse structure that remains valid for later tasks.
Possible relevant properties include:
- compression efficiency;
- retained identity;
- preserved relationships;
- provenance;
- memory;
- retrieval fidelity;
- prediction;
- correction;
- adaptation;
- resource cost.
The presence of these properties in an implementation does not independently establish a universal theory of intelligence.
Likewise:
compression
≠
understanding
memory
≠
truth
prediction
≠
causal explanation
recursive stability
≠
factual correctness
Current Governance
Current interpretation is governed by:
The Grand Compression Cosmology — Master Reference Document, MRD v2.0
Canonical identifier:
GC-MRD-v2.0
Repository implementations and benchmark results remain subject to:
- RC-21 — Reference Implementation Distinction
- RC-22 — Domain Transfer Constraint
The repository may test bounded consequences of the Grand Compression Law of Intelligence, but implementation or benchmark success must not be represented as universal empirical confirmation of the law.
Constraint-Bounded Recursive Intelligence
Constraint-Bounded Recursive Intelligence was introduced during the MRD v1.9 development cycle and remains part of the current MRD v2.0 framework.
It models recursive intelligence as an implemented process operating within finite substrate and governance constraints rather than as an unconstrained abstraction.
Relevant constraints may include:
- energy;
- compute;
- memory;
- bandwidth;
- thermal capacity;
- cooling;
- material infrastructure;
- fabrication;
- networking;
- coordination;
- correction capacity;
- governance bandwidth.
The framework expresses a candidate substrate-alignment condition as:
Gᵣ ≤ Eₛ
Where:
- Gᵣ = recursive gain per iteration;
- Eₛ = substrate expansion capacity.
This relation should be interpreted as a framework-level architectural condition.
It is not automatically a dimensionally complete or universally validated physical law.
A quantitative application must define:
- what constitutes recursive gain;
- what constitutes substrate expansion capacity;
- the units used for both quantities;
- the relevant time interval;
- system boundaries;
- normalization;
- baseline;
- uncertainty;
- measurement procedure;
- competing explanations;
- and failure conditions.
Without those declarations:
Gᵣ ≤ Eₛ
should remain a conceptual substrate-alignment relation.
Efficiency vs Expansion
Constraint-Bounded Recursive Intelligence motivates an important architectural distinction:
capability growth through improved efficiency
≠
capability growth through substrate expansion
A recursive system may potentially increase useful work through:
- better compression;
- preserved reusable structure;
- memory reuse;
- reduced recomputation;
- improved retrieval;
- lower correction burden;
- better algorithms;
- better utilization;
- improved hardware.
Physical infrastructure expansion may also increase available capacity.
The framework therefore does not require the claim that compression efficiency is always the primary driver of long-term capability growth.
A safer relation is:
useful recursive capability
may increase through
internal efficiency improvements
and/or
external substrate expansion
The relative contribution of each must be measured for the system being evaluated.
Constraint Response
If recursive demand exceeds an active substrate constraint, possible outcomes may include:
constraint activation
→ adaptation
→ efficiency improvement
→ substrate expansion
→ plateau
→ degradation
→ failure
Different systems may follow different paths.
Therefore:
Gᵣ > Eₛ
≠
automatic collapse
and:
Gᵣ ≤ Eₛ
≠
guaranteed stability
The relation identifies a framework concern about alignment between recursive growth and supporting capacity.
It does not, by itself, determine every system outcome.
Relationship to the Physical Substrate Constraint Field
The repository contains a dedicated engineering orientation for this concept:
docs/physical-substrate-constraint-field.md
That document should be interpreted alongside the current MRD v2.0 architecture.
The relevant distinction is:
internal recursive organization
+
external substrate capacity
→
bounded operating regime
This is a conceptual relationship, not a complete physical equation.
Current Authority
Current governing authority:
The Grand Compression Cosmology — Master Reference Document, MRD v2.0
The historical v1.9 introduction remains part of the development record.
Current interpretation is governed by MRD v2.0.
Canonical authority for the broader recursive engineering architecture spans the current MRD sections governing:
- recursive stability and physical substrate constraints;
- structural intelligence engineering;
- preserved reusable structure;
- predictive evaluation;
- reference implementation;
- and domain transfer.
Repository implementations remain subject to:
- RC-21 — Reference Implementation Distinction
- RC-22 — Domain Transfer Constraint
Accordingly:
framework constraint relation
≠
empirical physical law
and:
reference implementation
≠
universal confirmation
Robbie’s Razor Architecture
Within the Grand Compression Cosmology, Robbie’s Razor™ provides a reference architecture for organizing recursive information processing around:
compression → expression → memory → recursion
A broader implementation-oriented loop may be represented as:
Environment
│
▼
Observation
│
▼
Compression
│
▼
Expression
│
▼
Memory
│
▼
Recursion
│
▼
Prediction
│
▼
Action
│
▼
Feedback
│
▼
Memory Update
│
▼
Recompression
└──────────────→ renewed observation / processing
This is a Grand Compression reference architecture.
It should not be interpreted as a claim that every intelligent, biological, computational, ecological, or physical system has been empirically demonstrated to implement this exact loop.
The architecture instead provides a structured way to ask whether a system:
- compresses information or operating burden;
- expresses that compressed structure in a usable form;
- preserves sufficient state for later reuse;
- recursively reuses prior structure;
- produces predictions, decisions, or actions;
- receives feedback;
- and updates its preserved state.
Different implementations may realize these functions through different mechanisms.
Accordingly:
shared functional sequence
≠
identical implementation
and:
architectural correspondence
≠
shared physical mechanism
Closed-Loop Interpretation
A Robbie’s Razor implementation may be described as closed-loop when outputs, feedback, or evaluated consequences can influence preserved state and subsequent recursive processing.
Conceptually:
state
→ transformation
→ output
→ feedback
→ state update
→ renewed transformation
Closure in this repository is an engineering concept concerning governed re-entry and state reuse.
It must not automatically be equated with specialized mathematical meanings of closure in topology, algebra, dynamical systems, category theory, or physics.
Cross-domain transfer remains governed by RC-22.
Recursive Stability
Within the framework, recursive stability is not produced merely by repeating the cycle.
A stable implementation may require sufficient preservation of:
- identity;
- relationships;
- provenance;
- constraints;
- version state;
- retrieval accessibility;
- correction state;
- task-relevant information.
The relevant engineering question is:
Does repeated reuse preserve enough required structure for the system to continue operating within its declared correctness and resource boundaries?
This makes stability an evaluable property rather than an automatic consequence of recursion.
Accordingly:
recursion
≠
stability
memory
≠
correct memory
and:
stable internal state
≠
factual truth
Safe Recursion Envelope
The framework defines a conceptual Safe Recursion Envelope using energetic and stabilization constraints.
An energetic ceiling may be represented as:
R ≤ E / JCT
A stabilization or governance ceiling may be represented as:
R × C ≤ S
Their combined framework relation is:
R ≤ min(E / JCT, S / C)
Where:
- R = recursion rate within the declared system;
- E = available energy within the declared system boundary;
- JCT = Joules per Coherent Transition;
- S = available stabilization or governance bandwidth;
- C = correction demand per transition.
The Safe Recursion Envelope should be interpreted as a framework-level constraint model.
It does not mean that satisfying the inequality automatically guarantees stability.
Likewise, violating an estimated boundary does not by itself establish the cause of an observed failure.
Therefore:
inside modeled envelope
≠
guaranteed stability
and:
outside modeled envelope
≠
proven failure mechanism
Quantitative Boundary
A quantitative application of the Safe Recursion Envelope must define:
- the system being evaluated;
- recursion rate;
- energy boundary;
- coherent transition;
- JCT measurement method;
- stabilization bandwidth;
- correction demand;
- units;
- normalization;
- time interval;
- baseline;
- uncertainty;
- expected relationship;
- alternative explanations;
- and failure conditions.
Without these declarations:
R ≤ min(E / JCT, S / C)
remains an architectural research relation rather than a universally validated physical law.
Reference-Implementation Boundary
Repository code and Naturepedia™ implementations may demonstrate operational forms of:
compression
→ expression
→ memory
→ recursion
Successful implementation demonstrates that a declared architecture can operate.
It does not independently establish that:
- the architecture is universal;
- the Safe Recursion Envelope is a universally validated law;
- stable operation proves factual correctness;
- or the complete Grand Compression Cosmology has been empirically confirmed.
This distinction is governed by:
- RC-21 — Reference Implementation Distinction
- RC-22 — Domain Transfer Constraint
Current governing authority remains:
The Grand Compression Cosmology — Master Reference Document, MRD v2.0
The historical MRD v1.9 development cycle introduced the Recursive Stability Attractor and Unified Recursion Efficiency Relation.
These concepts remain part of the current MRD v2.0 framework, but their repository interpretation must distinguish between:
- canonical framework definition;
- conceptual mathematical model;
- implementation;
- benchmark observation;
- and empirical confirmation.
Historical development note:
docs/empirical/v1.9-recursive-stability-attractor-update.md
That file preserves the v1.9 development context and should not be interpreted as overriding the current MRD v2.0 authority.
Recursive Stability Attractor — Current Interpretation
The Recursive Stability Attractor is a Grand Compression framework model describing a candidate tendency for some constrained recursive systems to move toward more sustainable compression regimes as inefficient recursive behavior encounters internal or external limits.
A conceptual sequence may be represented as:
expansion
→ constraint accumulation
→ compression or architectural adaptation
→ possible stability restoration
This sequence is an architectural model.
It does not establish that every recursive system must follow this trajectory.
Possible outcomes under constraint may instead include:
- stabilization;
- architectural adaptation;
- oscillation;
- plateau;
- degraded performance;
- failure;
- external substrate expansion;
- or termination.
Accordingly:
constraint
≠
guaranteed convergence
and:
repeated recursion
≠
automatic approach to a stability minimum
The Stability Minimum remains a framework concept governed by the current MRD v2.0 architecture.
Any claim that a particular system converges toward such a minimum requires a declared operational definition, baseline, measurement procedure, uncertainty, and failure conditions.
Unified Recursion Efficiency Relation
The historical v1.9 development material introduced the candidate recursion-efficiency quantity:
S_r = I / JCT
Where:
- S_r = recursion efficiency;
- I = preserved functional information;
- JCT = Joules per Coherent Transition.
It also motivates the relation:
R ≤ (E · S_r) / I
These expressions should be treated as framework-level conceptual relations unless a specific evaluation supplies operational definitions and compatible units.
In particular, a quantitative use must define:
- what counts as preserved functional information;
- how
Iis measured; - what constitutes a coherent transition;
- how JCT is measured;
- the definition of recursion rate
R; - the energy boundary
E; - normalization;
- uncertainty;
- baseline;
- and falsification conditions.
Without those declarations:
S_r = I / JCT
and:
R ≤ (E · S_r) / I
remain architectural research expressions rather than universally established physical laws.
Compression Efficiency and Capability Growth
The framework motivates the hypothesis that some capability growth may be achieved through improved compression efficiency, preserved reusable structure, better memory, and reduced redundant recomputation rather than through proportional physical-resource expansion alone.
The bounded relationship is:
better compression / reuse
→ potentially more useful work per declared resource budget
not:
compression efficiency
→ guaranteed long-term capability growth
Infrastructure expansion, algorithmic improvement, model architecture, hardware, data, workload demand, and other factors may also affect capability.
Any comparative claim should identify the relevant variables and baseline.
Current Authority Boundary
The historical v1.9 material remains useful for documenting the development of these concepts.
Current interpretation is governed by:
The Grand Compression Cosmology — Master Reference Document, MRD v2.0
Canonical identifier:
GC-MRD-v2.0
The repository should preserve the distinction:
historical introduction
≠
current governing authority
and:
canonical framework model
≠
empirical confirmation
Reference implementations and benchmark results remain subject to:
- RC-21 — Reference Implementation Distinction
- RC-22 — Domain Transfer Constraint
Robbie’s Razor therefore retains the architectural sequence:
compression → expression → memory → recursion
without treating the sequence itself as proof that every recursive system converges to the same stability regime.
Repository Map
Quick research summary: docs/RESEARCH_OVERVIEW.md
Knowledge Architecture
The applied knowledge architecture of this repository is governed by MRD v2.0, including:
- Section 12 — Structural Intelligence Engineering
- Section 13 — Predictive Compression, Evaluation, and Reference Implementation
Section 12 establishes the engineering principles governing:
- Recursive Knowledge Compression Architecture (RKCA);
- Recursive Compression Interfaces (RCIs);
- Plates™ as applied cognitive infrastructure;
- Recursive Registry Inheritance Principle (RRIP);
- Comparative Compression Geometry™;
- retrieval-dominant knowledge systems;
- machine-readable intelligence; and
- recursive deployment under energy, memory, governance, and substrate constraints.
Section 13 establishes the evaluation and evidence requirements governing:
- Predictive Compression Theory;
- Preserved Reusable Structure;
- Compression Fitness;
- falsifiability and declared failure conditions;
- evidence-state classification;
- benchmark architecture;
- reference-implementation boundaries;
- domain-transfer constraints; and
- AI-agent interpretation and evidence discipline.
Within this repository:
compression → expression → memory → recursion
is implemented as an engineering architecture rather than merely a conceptual sequence.
Recursive Knowledge Compression Architecture defines how complex knowledge systems are compressed into reusable human-readable and machine-readable cognitive structures.
RKCA extends Robbie’s Razor™ into applied knowledge systems through:
- Recursive Compression Interfaces;
- Plates™;
- Registries;
- Meta-Registries;
- System Maps;
- Graph Registries™;
- Knowledge Meshes;
- provenance records; and
- machine-readable retrieval.
These components collectively form a retrieval-dominant architecture.
Rather than repeatedly reconstructing knowledge from raw information, validated compressed structures may be preserved as reusable cognitive infrastructure.
Under RC-18, preservation requires maintaining sufficient identity, relationships, provenance, constraints, version state, and retrieval pathways for valid future reuse.
Under RC-17, validated compressed registries may become substrates for later compression cycles through recursive registry inheritance.
The applied progression is:
Plate™ → Registry → Meta-Registry → System Map → Graph Registry™ → Knowledge Mesh
This architecture is intended to reduce unnecessary recomputation while preserving provenance, semantic relationships, version continuity, and recursive usability.
Canonical references:
- Recursive Knowledge Compression Architecture — MRD v2.0 §12.7
- Recursive Registry Inheritance Principle — MRD v2.0 §12.8 and RC-17
- Comparative Compression Geometry™ — MRD v2.0 §12.9
- Predictive Compression Theory — MRD v2.0 §13.2
- Preserved Reusable Structure Principle — MRD v2.0 §13.3 and RC-18
- Compression Fitness Principle — MRD v2.0 §13.4 and RC-20
- Reference Implementation — MRD v2.0 §13.7 and RC-21
- Domain Transfer Constraint — RC-22
- Provisional mathematical formalization — Appendix Q
RKCA, Naturepedia™, and all repository implementations remain applied engineering or reference-implementation layers.
Canonical definitions remain governed by The Grand Compression Cosmology — Master Reference Document, MRD v2.0.
Implementation does not equal empirical confirmation.
Naturepedia™ operation does not independently establish universal validation of the complete framework.
Earth Systems Expansion (Naturepedia™)
Naturepedia™ now includes a dedicated Earth Systems architecture layer connecting geological, hydrological, biological, microbial, and ecosystem-scale knowledge systems.
Primary Earth Systems Hub:
https://www.robbiegeorgephotography.com/earth-systems
Current Earth Systems registries:
- Earth Systems™
- Soil Systems™
- Carbon Cycle™
- Ecosystem Feedbacks™
- Weather™
- Water Systems™
- Microbial Life Systems™
- Volcanic Landscapes™
- Geothermal Ecosystems™
- Yellowstone Thermal Features™
- Hydrothermal Ecosystems™
Connected Intelligence Systems:
- Bioelectric Systems™
- Quantum Agriculture™
- Plant Intelligence™
- Plant Communication™
- Plant Electrophysiology™
- Mycorrhizal Networks™
- Electrical Ecology™
- Geometry of Nature™
- Hopf Fibration — established mathematical comparison class
- E8 Lattice™ — bounded mathematical reference
- Fractals™
- Fibonacci™
- Information Systems in Nature™
Naturepedia™ Systems Expansion (June 2026)
Major systems now include:
Shortened here. Read the whole README on GitHub.
Tools it offers (3)
What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.
about_naturepediasearch_naturepediaresolve_naturepedia_resource
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- naturepedia MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
com-robbiegeorgephotography-naturepedia- Source
- github.com/robbierazor/robbies-razor-benchmarks
- Hosted endpoint
https://mcp.robbiegeorgephotography.com/mcp
github.com/robbierazor/robbies-razor-benchmarks