Addresses That Mean Something

RPP is a 28-bit semantic addressing protocol that encodes meaning directly into addresses. Route data based on what it is and who can access it — not just where it lives.

Get Started View on GitHub

The Problem with Traditional Addressing

Memory addresses are opaque. They tell you where data is, but nothing about what it means.

🔍

No Semantic Context

Address 0x7F3A2100 tells you nothing. Is it sensitive? Personal? Shareable? You need separate systems to track this metadata.

🔐

Scattered Access Control

Consent and permission logic gets duplicated across every service. Each system reinvents the wheel for access decisions.

🔄

Routing Requires Lookups

To route data correctly, you query databases, check permissions, consult policies. The address itself provides no guidance.

RPP: Meaning Built Into Every Address

A 28-bit address that encodes what data is, how accessible it is, and where to route it.

Shell
2 bits
Theta
9 bits
Phi
9 bits
Harmonic
8 bits

                Example: 0x0182801

                Shell = 0 (Hot) → Route to: in-memory storage

                Theta = 12 (Gene) → Data type: genetic/identity data

                Phi = 40 (Grounded) → Access: open, no consent needed

                Harmonic = 1 → Resolution mode
            

📁

Shell (2 bits)

WHERE it's stored

Hot / Warm / Cold / Frozen

🔬

Theta (9 bits)

WHAT type it is

Gene / Memory / Dream...

🔒

Phi (9 bits)

WHO can access it

Grounded / Transitional / Ethereal

🎵

Harmonic (8 bits)

HOW to handle it

Resolution / frequency / mode

Why This Design?

RPP eliminates entire categories of distributed systems complexity by encoding decisions into addresses.

⚡

O(1) Everything

Encode: 4 bit shifts + 3 ORs. Decode: 4 bit shifts + 4 ANDs. No database, no network, no cache lookups.

📦

28 Bits = Tiny

Fits in a single 32-bit integer. Embeddable in URLs, headers, logs, QR codes.

🔌

Zero Dependencies

Pure arithmetic. Works on microcontrollers to mainframes. No runtime, no libraries required.

🔍

Deterministic = Auditable

Same input always produces same output. Unit testable, formally provable.

📋

Self-Documenting

Address reveals intent without documentation lookup. Decode any address to see its meaning.

🛡

Consent by Design

GDPR/privacy compliance built into addressing. Phi encodes access level — consent isn't bolted on.

The Geometry: Spherical Coordinates

RPP addresses map to points on a conceptual sphere. Theta and Phi aren't arbitrary — they're angular coordinates.

Theta (Azimuthal)

Rotation around the vertical axis. Divides the sphere into 8 semantic sectors: Gene, Memory, Witness, Dream, Bridge, Guardian, Emergence, Meta.

Phi (Polar)

Distance from the "north pole" of abstraction to the "south pole" of grounding. Low phi = accessible. High phi = requires consent.

Shell (Radial)

How far from the center. Shell 0 (Hot) is closest to the core. Shell 3 (Frozen) is the outer boundary.

Quick Start

Get up and running in 60 seconds. Zero dependencies.

Installation

                pip install rpp-protocol
            

CLI Usage

# Encode an address
rpp encode --shell 0 --theta 12 --phi 40 --harmonic 1
[ENCODE] [OK] 0x0182801 | Hot | Gene | Grounded

# Resolve (get routing decision)
rpp resolve --address 0x0182801
[RESOLVE] [OK]
  allowed: true
  route: memory://gene/grounded/12_40_1

Python API

from rpp import encode, decode, resolve

# Encode an address
addr = encode(shell=0, theta=12, phi=40, harmonic=1)
print(hex(addr))  # 0x182801

# Resolve with operation
result = resolve(addr, operation="read")
print(result.allowed)  # True
print(result.route)    # memory://gene/grounded/12_40_1

Install from PyPI View Source Read the Spec

Live Demo

Experience RPP on Windows. Click through the tutorial screens to see semantic addressing in action.

                    
                    Windows Terminal - PowerShell
                
                    C:\Users\demo

Bits per address

<1ms

Encode/decode

Dependencies

Languages