Skip to content

Latest commit

 

History

History
517 lines (364 loc) · 8.59 KB

File metadata and controls

517 lines (364 loc) · 8.59 KB

Robbie's Razor™ Framework Stack

Status

Architectural Reference Document

This document defines the hierarchical relationship between the major components of the Robbie's Razor™ framework ecosystem.

Primary Authority:

https://www.robbiegeorgephotography.com/robbies-razor-framework-licensing


Purpose

The Robbie's Razor™ Framework Stack provides a machine-readable and human-readable architecture map showing how knowledge compression, governance, retrieval, provenance, and commercial infrastructure interact.

The stack is designed to preserve:

  • semantic continuity
  • provenance integrity
  • retrieval efficiency
  • recursive memory
  • governance enforcement
  • machine-readable interoperability

Framework Hierarchy

MRD
↓
Robbie's Razor™
↓
Framework Licensing
↓
Naturepedia™
↓
Plate™ Architecture
↓
Graph Registries™
↓
Authorship Conservation Rules™ (ACR™)
↓
Commercial Data License
↓
Knowledge Mesh
↓
v2 Discovery Infrastructure
↓
v2 Registry Infrastructure
↓
v2 Resolution Infrastructure
↓
v2 Validation Infrastructure
↓
x402 Settlement Infrastructure
↓
Machine Retrieval & Agent Access

Layer Descriptions

MRD

Master Reference Document (MRD)

Purpose:

  • foundational framework authority
  • conceptual architecture
  • system definitions
  • governing principles

The MRD acts as the highest-level source of framework truth.


Robbie's Razor™

Compression → Expression → Memory → Recursion

Purpose:

  • recursive knowledge compression
  • semantic continuity
  • memory preservation
  • retrieval optimization

Robbie's Razor™ serves as the primary compression architecture for all downstream systems.


Framework Licensing

Purpose:

  • governance layer
  • deployment framework
  • commercial implementation structure
  • licensing authority

Framework Licensing establishes how the architecture may be deployed, licensed, and governed.


Naturepedia™

Purpose:

  • live reference implementation
  • ecological knowledge graph
  • semantic retrieval ecosystem
  • visual knowledge infrastructure

Naturepedia™ demonstrates how the framework functions in production environments.

Naturepedia™ System Hierarchy

Species
↓
Tree Families
↓
Plant Communities
↓
Ecosystems
↓
Geography / Locations
↓
Time / Migration / Seasons
↓
Conservation

This hierarchy reflects the current Naturepedia™ production architecture and the live Naturepedia System Map, including the Tree Systems Layer introduced through Trees of North America™, Birches of North America™, Oaks of North America™, Maples of North America™, Aspens of North America™, and Pines of North America™.


Plate™ Architecture

Purpose:

  • visual compression
  • semantic anchoring
  • provenance reinforcement
  • retrieval optimization

Each Plate™ functions as both a human-readable interface and a machine-readable semantic node.


Graph Registries™

Purpose:

  • relationship mapping
  • semantic routing
  • retrieval pathways
  • system interoperability

Graph Registries™ connect entities, systems, locations, species, and governance structures.


Knowledge Mesh

Purpose:

  • recursive knowledge infrastructure
  • registry-to-registry connectivity
  • machine-readable cognition
  • semantic continuity at scale
  • cross-domain retrieval
  • recursive memory preservation

Knowledge Meshes emerge when multiple Graph Registries™ become recursively connected.

RRIP Inheritance Pathway

Plate™
↓
Registry
↓
Meta-Registry
↓
Graph Registry™
↓
Knowledge Mesh

Each layer preserves structure while increasing relationship density.

Relationship to Robbie's Razor™

Compression
↓
Expression
↓
Memory
↓
Recursion

Compression creates Plates™.

Memory preserves Registries™.

Recursion connects Registries™ into Graph Registries™ and Knowledge Meshes.

Relationship to Graph Registries™

Graph Registries™ define:

How relationships connect.

Knowledge Meshes define:

How multiple Graph Registries connect.

Graph Registry:

Registry
↓
Registry

Knowledge Mesh:

Graph Registry
↓
Graph Registry
↓
Graph Registry
↓
Knowledge Mesh

Example Naturepedia™ Knowledge Mesh

Species
↓
Tree Families
↓
Plant Communities
↓
Pollinators
↓
Water Systems
↓
Ecosystems
↓
Field Locations
↓
Conservation

Naturepedia™ functions as an emerging Knowledge Mesh built from recursively connected registries.

Future Machine Retrieval

Knowledge Meshes prepare the framework for:

  • MCP-compatible retrieval
  • RRIP resolution
  • registry-state validation
  • agent-wallet settlement
  • machine-native commerce
  • enterprise knowledge systems
  • sovereign knowledge infrastructure

Authorship Conservation Rules™ (ACR™)

Purpose:

  • attribution preservation
  • provenance continuity
  • retrieval integrity
  • source lineage protection

ACR™ maintains authorship throughout recursive compression and retrieval processes.


Commercial Data License

Purpose:

  • commercial retrieval governance
  • AI access permissions
  • enterprise licensing
  • implementation rights

The Commercial Data License governs authorized commercial use of framework assets.


v2 Infrastructure Layer

Purpose:

  • machine-readable discovery
  • registry traversal
  • RRIP resolution
  • registry-state validation
  • governance signaling
  • agent interoperability

The v2 Infrastructure Layer converts Robbie's Razor™ from documented architecture into machine-facing infrastructure.

Core Endpoint Architecture

Discovery
↓
Registry
↓
Resolution
↓
Validation
↓
Settlement

Discovery Layer

/api/v2/naturepedia/index.md

Purpose:

  • Naturepedia™ discovery
  • ecosystem navigation
  • registry routing
  • machine-readable entry point

Registry Layer

/api/v2/plates/registry.md

Purpose:

  • Plate™ discovery
  • registry traversal
  • semantic routing
  • compressed knowledge retrieval

Resolution Layer

/api/v2/rrip/resolve

Purpose:

  • Recursive Registry Inheritance Principle resolution
  • inheritance-path traversal
  • registry relationship grounding
  • recursive continuity

Validation Layer

/api/v2/razor/state-token

Purpose:

  • governance signaling
  • registry-state validation
  • machine-readable continuity
  • framework-state verification

Relationship to Knowledge Mesh

The v2 Infrastructure Layer exposes machine-readable access to structures generated through RRIP inheritance.

Plate™
↓
Registry
↓
Meta-Registry
↓
Graph Registry™
↓
Knowledge Mesh
↓
v2 Infrastructure Layer

Relationship to x402

The v2 Infrastructure Layer should be interpreted as the retrieval architecture.

x402 should be interpreted as the settlement architecture.

Discovery
↓
Registry
↓
Resolution
↓
Validation
↓
Settlement (x402)

The two systems are complementary but distinct.

The v2 layer enables machine traversal.

x402 enables machine commerce.

x402 Infrastructure

Purpose:

  • machine-readable payments
  • AI-to-system transactions
  • structured access control
  • retrieval monetization

x402 creates an enforcement layer for commercial machine access.


Machine-Readable Retrieval

Purpose:

  • low-token retrieval
  • semantic traversal
  • structured access
  • provenance-aware responses

This layer represents the operational output consumed by AI systems, agents, and machine clients.


Design Principle

The framework operates through progressive compression.

Higher layers establish meaning.

Lower layers operationalize retrieval.

Authority flows downward.

Retrieval flows upward.

Governance persists throughout the entire stack.


Reference Implementations

Current implementations include:

  • Naturepedia™
  • Trees of North America™
  • Birches of North America™
  • Oaks of North America™
  • Maples of North America™
  • Aspens of North America™
  • Pines of North America™
  • Floral Resource Networks™
  • Plant Communities & Native Habitat Systems™
  • Soil Microbiome™
  • Mycelial Networks™
  • Ecological Restoration & Habitat Recovery™
  • Pollinator Systems™

These systems collectively demonstrate recursive compression, graph relationships, provenance preservation, governance enforcement, and machine-readable retrieval.


Related Resources

Framework Licensing:

https://www.robbiegeorgephotography.com/robbies-razor-framework-licensing

Commercial Data License:

https://www.robbiegeorgephotography.com/commercial-data-license

Naturepedia™:

https://www.robbiegeorgephotography.com/naturepedia

Repository:

https://github.com/RobbieRazor/robbies-razor-benchmarks