Skip to the beginning of the images gallery

55-aerophi-fractal-qbeam

$4,911,937.50

In stock

SKU

2086

AeroPhi Fractal QBeam: the same QBeam relay node at six scales; one packet trickles down from the planetary tier to the chip tier and back up, animated picture

Asset valuation: $11,000,000,000. Project 55 · cri-one.com portfolio · Author: Christopher Gabriel Brown AeroPhi turns every cell tower, satellite, edge node, and endpoint chip into a QBeam relay in a single fractal mesh. The same quantum-data packet trickles down from planet-scale broadcast into a

For the curious

Think of a packet the way you think of rain. It falls from the sky onto a rooftop and ends up in a glass on your desk, the same water the whole way down. AeroPhi is a cloud built that way. Every satellite, cell tower, rooftop node, rack and endpoint chip becomes a QBeam relay in one fractal mesh, and the same quantum-data packet trickles down from planet-scale broadcast to a chip in your hand, and back up again, intact at every tier. A chip and a satellite are the same node type at different scales. No gateway, no protocol boundary.

The mesh has six tiers, from satellites and submarine backbones down to cell towers, buildings, racks and single dies. Each tier is self-healing: take out a tower and the city's data reflows through its neighbors. A tower becomes a compute and flash-storage node, so data lives close to whoever uses it. Every QBeam packet is 4,736 bits: a header, an AES-256-GCM payload and a two-layer error-correction tail, with post-quantum key exchange available per sovereign policy. A country can own its top three tiers end to end.

This is for carriers, satellite operators, sovereign cloud builders and datacenter operators. AeroPhi is designed, not yet foundry-ready: the six-tier architecture, the propagation protocol, twenty silicon configurations, reference hardware at every tier, firmware, SDKs, test harnesses and a sovereign-deployment playbook are on file, built on the filed ExitPhi patent application. The inventor retains the IP. The buyer walks away with that design set and the playbook to deploy it.

Details

Description

AeroPhi — QBeam Fractal Aerial Cloud (SKU 2086)

Patent-pending. Built upon U.S. Non-Provisional Utility Patent Application No. 19/722,805, Confirmation No. 4017, Patent Center No. 77974071, filed 2026-06-27 via USPTO Patent Center under 35 U.S.C. § 111(a). Title: Integrated Wireless Datacenter Fabric with Phased-Array Cooling Antenna, Order-Preserving Antenna Series, and Quantum-Teleportation Protocol atop a Shared Classical Channel . 30 claims (6 independent, 24 dependent). Related patent application: U.S. Application No. 19/717,706 (UniPhi Retroactive Wireless Adapter). Inventor: Christopher Gabriel Brown, pro se, sole inventor, no assignment of record at filing. IP fully retained. AeroPhi is the mesh-scale deployment of the ExitPhi patented integrated system (CoolBeam + PipeBeam + QBeam). Invention record anchors trace to the master IP catalog entries 989–995 and 1744–1751 (aerial flash-server cluster, © 2017–2018). Current status: Designed — concept, six-tier architecture, QBeam propagation protocol, 20 silicon configurations, reference hardware at every tier, firmware, SDKs, test harnesses, and sovereign-deployment playbook are on file. Not yet foundry-ready. Sibling domains: Communications, Space & Defense.

Overview

AeroPhi turns every cell tower, satellite, edge node, and endpoint chip into a QBeam relay in a single fractal mesh — so the same quantum-data packet trickles down from planet-scale broadcast into a chip on your desk, and trickles up from that chip back out to the whole mesh, with quantum-level integrity preserved at every tier.

Every conventional cloud today is one-directional and scale-locked: your device queries a datacenter, the datacenter answers. AeroPhi collapses that hierarchy. QBeam carries the data. Every node in the mesh — from a chip’s on-die transceiver up to a geostationary satellite — speaks the same QBeam protocol . Data trickles both directions through the mesh in a fractal pattern. Same packet. Every scale. Both directions. Coherent.

The mesh has no protocol boundary between tiers . A T6 chip and a T1 satellite are not merely interoperable; they are the same node type at different scales. This is the fractal property. No translation gateway, no protocol boundary, no format shift. The same packet you broadcast at T1 arrives intact at T6, and the same packet a T6 chip emits reaches T1 without transcoding.

Why AeroPhi Beats the Current Cloud

No more datacenter monopoly. Compute and storage live distributed across the mesh, weighted toward wherever the data is being used. Data lives closest to its consumer, not in a distant datacenter.
No aerial single point of failure. Every tier is a self-healing mesh. Take out a T3 tower and the metro’s data reflows through neighbouring T3 towers or up to T2 and back down.
Cell towers become cloud nodes. A tower is not a dumb radio — it is a compute + flash-storage node in the aerial cloud. Encrypted packet tickets live in the tower hardware (aerial flash-server), not in a distant AWS region.
Sovereign by construction. A country can own its T1–T3 tiers end-to-end without depending on Amazon, Google, or Microsoft. AeroPhi is the sovereign cloud primitive.

The Six Scale Tiers

Tier Scale Physical Nodes Data Role Storage Layer Latency Budget Throughput Target

T1 · Planetary Global GEO/LEO satellites, submarine backbones, ground stations Broadcast + planetary aggregation Cold archive 240 ms round-trip 40 Gb/s per beam

T2 · Continental Country-scale National backbone routers, sovereign anchor sites Regional routing, sovereign anchors Warm archive 30 ms 100 Gb/s per link

T3 · Metropolitan City-scale Cell towers, municipal edge nodes (aerial flash-server) Low-latency city cloud, aerial flash-server storage Hot flash cache 5 ms 40 Gb/s per tower

T4 · Facility Building-scale Rooftop nodes, in-building repeaters, PoPs Service mesh, private aerial cloud RAM cache 1 ms 25 Gb/s per building

T5 · Rack / Cluster Chassis-scale Rack-mounted QBeam transceivers, IoT swarms Cluster-local coherence, device pool Cluster-local cache 250 µs 12 Gb/s per rack

T6 · Chip / Endpoint Silicon-scale Single die, single handset, single wearable Emission, reception, on-die QBeam relay On-die register 50 µs 3 Gb/s per endpoint

All targets are design targets derived from the engineering record; not measured guarantees.

QBeam Protocol Specification

QBeam is the patented quantum-data carrier from ExitPhi (USPTO App No. 19/722,805). AeroPhi deploys QBeam at mesh scale. Every QBeam packet is exactly 4,736 bits (592 bytes) :

Field Size (bits) Description

Header 128 Addressing, sequencing, sovereign domain, quantum-integrity nonce

Payload 4,096 User data or protocol data, AES-256-GCM encrypted (3,968 bits plaintext + 128-bit GCM tag)

FEC Tail 512 Two-layer forward error correction (Reed-Solomon outer + LDPC inner)

Header Fields (128 bits)

Field Bits Description

Version 4 Protocol version (current: 0x1)

Source Tier 3 1–6 (T1–T6)

Destination Tier Mask 6 Bit mask over T1–T6 (e.g., 0b111111 = broadcast to all tiers)

Sovereign Domain 16 Identifies the sovereign whose policy governs this packet

Packet Type 5 DATA, ACK, NAK, BEACON, ROUTE_ANNOUNCE, ROUTE_WITHDRAW, STORE_COMMIT, STORE_QUERY, STORE_ANSWER, LEDGER_HASH, KEY_EXCHANGE, POLICY_UPDATE

Reserved 3 Zero on emission

Sequence Number 48 Monotonic per (source, sovereign domain); 48 bits at 40 Gb/s ≈ 10 5 years

Quantum-Integrity Nonce 43 Random per packet; binds to the QBeam symbol stream at the receiving PHY

Packet Types (12 Defined)

Value Name Semantics

0x00 DATA Standard payload

0x01 ACK Acknowledgment of a previous DATA packet

0x02 NAK Negative acknowledgment; retransmit request

0x03 BEACON Tier heartbeat + sovereign-domain advertisement

0x04 ROUTE_ANNOUNCE Fractal-router table update

0x05 ROUTE_WITHDRAW Router table withdrawal

0x06 STORE_COMMIT Instruction to a T3 aerial flash-server to persist payload

0x07 STORE_QUERY Query an aerial flash-server for a packet by sequence number

0x08 STORE_ANSWER Response to STORE_QUERY

0x09 LEDGER_HASH American Dollar Blockchain hash of this packet

0x0A KEY_EXCHANGE ML-KEM (post-quantum) key encapsulation

0x0B POLICY_UPDATE Sovereign-policy change; must be signed by sovereign authority

Error Correction

Layer Code Detail

Outer Reed-Solomon (255, 223) over GF(2 8 ) 32 parity bytes = 256 bits

Inner LDPC (2048, 1712) 256 bits used for the FEC tail

Combined — Correct up to 12 symbol errors per packet at design SNR

Encryption

Scheme Role Standard

AES-256-GCM Default payload encryption; key derived per sovereign domain from root FIPS PUB 197

ML-KEM Post-quantum key encapsulation; optional per sovereign policy NIST SP 800-208

Ed25519 Sovereign-authority ROUTE_ANNOUNCE signature verification —

Shamir’s Secret Sharing Sovereign root key ceremony: 3-of-5 threshold —

Trickle-Down Mechanism

Downward Flow (T1 → T6)

A T1 satellite emits a QBeam broadcast addressed to a sovereign-domain mask covering the target region.
National T2 anchors receive the broadcast and split it into per-metro sub-beams, addressed to the metropolitan sovereign-domain sub-masks.
Each T3 tower receives its metro’s sub-beam and caches it in the aerial flash-server. Tower simultaneously fans the beam out into T4 via WFA silicon.
T4 facility nodes receive the beam, cache it in RAM, and fan out to T5 racks and cluster hosts.
T5 racks fan out to T6 endpoints via SPI/I2C or WiFi 7.
The T6 endpoint sees the same packet the T1 satellite emitted. No transcoding at any hop.

Upward Flow (T6 → T1)

A T6 endpoint emits a QBeam packet addressed to a sovereign-domain mask higher up the tree.
The T6 packet is picked up by its T5 rack, aggregated with peer T6 emissions, and forwarded to T4.
T4 facility node aggregates T5 emissions and forwards to T3.
T3 tower aggregates T4 emissions and stores in the aerial flash-server. Forwards to T2.
T2 anchor aggregates T3 emissions from across the metro and forwards to T1.
T1 satellite receives the aggregated planetary emission.

Coherence Guarantees

CoolBeam clocks every repeater — thermal drift on any node is bounded such that the QBeam packet’s quantum state does not decohere within the tier’s latency budget.
PipeBeam aligns every backhaul — temporal drift between adjacent tiers is bounded to less than one QBeam symbol period.
The fractal-router state machine at every node commits a receipt to the aerial flash-server before ACK’ing upstream, enabling full-path retroactive audit.

AERO_TX_ASIC — Universal QBeam Transceiver SoC

The universal endpoint silicon. Every tier uses the same synthesisable core with different peripherals and packaging.

Sub-Blocks (7 Modules)

Block RTL File Purpose Feature-Flagged?

aerophi_top rtl/aerophi_top.v Top-level integration No

aerophi_qbeam_tx rtl/aerophi_qbeam_tx.v Packet framer, FEC encode, hand to PHY No

aerophi_qbeam_rx rtl/aerophi_qbeam_rx.v PHY receive, FEC decode, header parse No

aerophi_mesh_router rtl/aerophi_mesh_router.v Fractal-router state machine + table No

aerophi_afs rtl/aerophi_afs.v Aerial flash-server controller (T3 storage) Yes (PROP_AFS)

aerophi_crypto rtl/aerophi_crypto.v AES-256-GCM + optional ML-KEM ML-KEM: PROP_KEM

aerophi_scale_invariant rtl/aerophi_scale_invariant.v Tier mask decoder, replay-window check No

Feature Flags (9 Proprietary Blocks)

Flag Block Default (Min Config) Present In

PROP_QRF QBeam Radio Frontend 0 T3+

PROP_FMR Fractal Mesh Router 0 T5+

PROP_AFS Aerial Flash-Server 0 T3

PROP_SDE Sovereign Domain Enforcement 0 T4+

PROP_KEM Post-Quantum KEM 0 T3+

PROP_LDPC Advanced LDPC 0 T4+

PROP_CBI CoolBeam Interface 0 T4+

PROP_PBI PipeBeam Interface 0 T4+

PROP_QSI Quantum Symbol Integration 0 T3 apex

Process Nodes & Package Families

Process Node Package Families NRE Estimate

22 nm QFN (edge/consumer) $50k–$260k

16/12 nm BGA (mid) $400k–$1.4M

7 nm FCBGA (server/flagship) $4M–$9M

5 nm FCBGA (apex) $8M–$18M

5 nm rad-hard BGA (space-grade) $12M–$22M

3 nm FCBGA (continental apex) $25M–$55M

Silicon Configurations (20 Total)

Use Case Recommended Config Process Package

Consumer handset endpoint CFG-01 22 nm QFN-56

Consumer wearable / sensor CFG-02 22 nm QFN-56 + PNP

Smart-home hub CFG-03 22 nm QFN-72

Residential / SMB router CFG-04 22 nm QFN-88, 4×4 MU-MIMO

Enterprise edge CFG-06 16/12 nm BGA-144

Enterprise hub CFG-07 16/12 nm BGA-225

Municipal cell tower CFG-10 7 nm FCBGA-225

Metropolitan flagship tower CFG-13 5 nm FCBGA-196

Rad-hard defence edge / satellite payload CFG-16 5 nm rad-hard BGA-196

Hyperscale datacenter / continental anchor CFG-17 3 nm FCBGA-300

All 20 configurations are generated by hardware/gen_configs.py , each with its own FOUNDRY_HANDOFF.md . Tape-out through the AutoPhi Day-One production stack (portfolio Project 21), targeting TSMC, Samsung, Intel, SkyWater, and GlobalFoundries.

ASIC Pinout (AEROPHI-CFG-13, 5 nm FCBGA-196)

Pin Group Count Purpose

QBeam TX Serial 16 (8 diff pairs) QBeam symbol stream to PHY

QBeam RX Serial 16 (8 diff pairs) QBeam symbol stream from PHY

RF Control 8 single-ended RF frontend calibration/control

PCIe Gen4 × 4 24 Host bus

DDR5 66 External DRAM

Config / Debug 12 JTAG, SPI config, reset, IRQ

Power 44 Core, IO, PHY analog, DDR

Ground 26 —

Total 196 —

Clocking

Domain Source Rate

QBeam symbol clock Off-chip QBeam PHY (Silicon Labs Si5518) 20 GHz for T3+

Fabric clock On-chip PLL 1–2 GHz (process dependent)

AFS clock Derived from fabric clock Asynchronous FIFO between AFS and host bus

CoolBeam-locked domain QBeam PHY handoff When PROP_CBI = 1

PipeBeam-aligned domain Backhaul framing When PROP_PBI = 1

Fractal Mesh Routing Algorithm

Every node, from a T6 chip to a T1 satellite, runs the same fractal-router state machine with identical logic, identical wire format, differing only in routing-table size and per-hop latency budget. The routing decision at every tier reduces to two questions: (1) Is this packet’s destination tier mask compatible with my tier? (2) Does this packet’s sovereign domain match my sovereign policy?

Seven-State Pipeline

State Actions

IDLE Wait for packet arrival

RECEIVE Pull QBeam symbols; verify PipeBeam alignment; verify CoolBeam thermal window

DECODE LDPC inner code; Reed-Solomon outer code; header parse

POLICY Sovereign domain check; tier mask check; replay window check

STORE Commit receipt to aerial flash-server; optional STORE_COMMIT (T3 only)

ROUTE Look up (sov_dom, tier_mask) in fractal-router table; compute next hop(s); enqueue for TRANSMIT

TRANSMIT AES-256-GCM re-encrypt (fresh nonce); LDPC + RS re-encode; hand to QBeam PHY

Each state transition is bounded to the tier’s per-hop latency budget divided by the state count. For T3 (5 ms budget), each state has 700 µs. For T6 (50 µs budget), each state has 7 µs.

Fractal-Router Table Sizing

Tier Typical Table Size Update Rate

T1 10–100 entries 1 per hour

T2 100–1,000 entries 1 per minute

T3 1,000–10,000 entries 1 per second

T4 100–1,000 entries 1 per second

T5 10–100 entries 1 per 5 seconds

T6 1–10 entries 1 per minute

Convergence

Route convergence is guaranteed within one BEACON period per tier: 5 ms metropolitan, 30 ms continental, 240 ms planetary. Worst-case full-mesh convergence (T6 → T1 → T6 through the whole mesh): 6 hops × 240 ms = ~1.5 s. Best case (metropolitan): T3 → T3 = 5 ms. At the practical scale of a national mesh (~10,000 T3 nodes + 24 T2 anchors + 2 T1 satellites), convergence completes in T3 Tower Node — Cell Tower Retrofit Board

The physical package that turns any existing cell tower into a T3 AeroPhi node. 61 components, 563 pins, 517 named nets. Full KiCad-10 schematic included.

Property Value

Board Name aerophi_t3_tower

Form Factor 250 × 200 × 12 mm

PCB Stack-up 10 layers (Sig/Gnd/Sig/Pwr/Sig/Sig/Pwr/Sig/Gnd/Sig), 1.6 mm, FR-4 high-Tg (≥ 170 °C)

Operating Temp −40 °C to +75 °C

Power Input 48 V PoE++ or 24 V DC, 200 W peak

Power Draw ~40 W idle; 180 W peak (all QBeam ports active + SSD sustained write)

Cooling Passive convection with fin heatsink over ASIC and NVMe cage

Silicon 1× AERO_TX_ASIC (AEROPHI-CFG-13, 5 nm FCBGA-196)

Flash Storage 4× Samsung PM9A3 1 TB M.2 22110 NVMe SSDs, RAID-10, 2 TB usable

Memory 1× Micron DDR5-6400 32 GB UDIMM

RF Frontend 8× TI LMH2828 wideband amps + 8× Skyworks SKY73305 diplexers; 8× SMA-F edge coupler ports

Backhaul 25 GbE SFP28 fibre (primary) + optional SFP+ slot; 1 GbE RJ45 management

PCIe Switch Broadcom PEX88096 96-lane PCIe Gen4

PHY Marvell 88E1547 5-port 1G/10G/25G PHY

BMC Aspeed AST2600 baseboard management controller

Power Conversion Vicor DCM48x 48→12 V isolated 400 W; TI TPS543C20 bucks (3.3 V, 1.8 V); TI TPS62933 bucks (1.0 V core, 0.85 V core)

Boot Flash Micron MT25QL256 256 Mbit NOR SPI

Clocks Abracon 100 MHz reference; Silicon Labs Si5518 20 GHz QBeam PHY clock

Debug JTAG 20-pin ARM; UART 6-pin; 8× status LEDs; recovery pushbutton

Enclosure Interface 4× M4 mounting bosses per T3_TOWER_ENCLOSURE model

T3 Tower Enclosure — IP66 Weatherproof Housing

Property Value

Material 6061-T6 aluminium, machined from stock

Coating Type III hard-anodize (MIL-SPEC)

Enclosure External ~275 × 225 × 55 mm (assembled: 347 × 224 × 149.2 mm with mast clamp)

Weight (bare) ~4.2 kg

Weight (populated) ~5.5 kg

Ingress Protection IP66 per IEC 60529

Operating Temp −40 °C to +75 °C

Storage Temp −55 °C to +85 °C

Vibration IEC 60068-2-6 (sine sweep 10–500 Hz, 0.5 g)

Shock IEC 60068-2-27 (30 g, 11 ms half-sine)

Salt Spray ASTM B117, 500 hours

UV Resistance Type III anodize; expected 15+ years outdoor

Mast Clamp Two C-shape brackets for 60–114 mm diameter tower legs; 40 mm band width, 8 mm plates

Cable Glands 3× IP68 M20 (6–12 mm cable diameter) for power + fibre + spare

Vent Membrane M12 Gore-Tex vapour-permeable membrane

Gasket 3 mm diameter silicone O-cord, high-temp RTV adhesive

Fasteners Stainless steel: 4× M5 lid screws, 2× M8 mast-clamp bolts, 4× M4 board standoffs

CAD Source OpenSCAD parametric model (enclosure.scad)

T2 Continental Anchor — National-Routing Rack Card

The national-routing tier between T1 satellites and T3 towers. Aggregates traffic from thousands of T3 towers within a national footprint. Deploys as a 4U carrier-grade rack card .

Property Value

Form Factor 400 × 340 × 3.2 mm (4U rack card)

PCB Stack-up 16 layers, 2.4 mm, FR-4 high-Tg

Operating Temp 0 °C to +55 °C (ETSI EN 300 019 class 3.2)

Silicon 4× AEROPHI-CFG-17 (3 nm apex) in parallel

Host CPU Intel Xeon-D 2712 (12-core, 24-thread, 90 W TDP)

Memory 4× 32 GB DDR5-6400 UDIMM = 128 GB total

Flash Storage 8× Samsung PM9A3 4 TB M.2 22110 NVMe = 32 TB usable (RAID-10, 4-way stripe × 2-way mirror)

Backhaul 2× 400 GbE QSFP-DD (800 Gbit/s aggregate bidirectional) + 25 GbE SFP28 + 1 GbE RJ45

RF Frontend 16 channels (4 per ASIC × 4 ASICs); 16× LMH2828 + 16× SKY73305 + 16× SMA edge

Power 2× 48 V DC redundant, hot-swap; 1,200 W peak per input; ~120 W idle, 1,150 W peak

Timing IEEE 1588 PTP grandmaster (Microchip ZL30734) + u-blox ZED-F9T GNSS (GPS L1/L5 + Galileo E1/E5a + BeiDou) + Rakon RX-4340M OCXO 100 MHz holdover (±0.05 ppm, 24-hour ±1 µs budget)

Redundancy 2× BMC (AST2600), 4 ASICs in parallel, 2× 400 GbE independently routed via MUX pair, GNSS + OCXO holdover

Backplane VITA-46 96-pin edge

Front Panel 4-digit LED display + 3 buttons + buzzer + 8 status LEDs

T5 Rack Node — Carrier-Grade Data-Centre Card

The carrier-grade central-office / data-centre form of the AeroPhi mesh. 62 components, 704 pins.

Property Value

Form Factor 300 × 260 × 3.2 mm (2U rack card)

PCB Stack-up 12 layers, 2.4 mm, FR-4 high-Tg

Operating Temp 0 °C to +55 °C (ETSI EN 300 019 class 3.2)

Silicon 2× AEROPHI-CFG-08 (16/12 nm BGA-256) in cold-redundant primary/secondary

Flash Storage 4× Samsung PM9A3 2 TB M.2 22110 NVMe, RAID-10, 4 TB usable

Memory 1× Micron DDR5-6400 32 GB UDIMM

Backhaul 2× 25 GbE SFP28 + 1 GbE RJ45 management

RF Frontend 8× LMH2828 + 8× SKY73305 + 8× SMA edge

PCIe Switch Broadcom PEX88096 96-lane

Redundancy MUX TI TS3DV642 2:1 12-lane differential MUX

BMC Aspeed AST2600

Power 2× 48 V DC redundant, hot-swap (TI LM74700 ORing); 2× Vicor DCM4823 (800 W total); ~80 W idle, 380 W peak

Cooling Front-to-back forced air, 4× 40 mm chassis fans

Backplane VITA-46 96-pin edge, 24 conductive fingers, keyed A

Front Panel 4-digit LED (HT16K33) + 3 buttons + piezo buzzer + 8 status LEDs (PCA9634 driven)

T4 Facility Cluster — Campus-Scale Aggregator

Property Value

Form Factor 220 × 180 × 2.0 mm (compact 1U-half board)

PCB Stack-up 10 layers, 1.6 mm, FR-4 high-Tg

Operating Temp −5 °C to +60 °C

Silicon 2× AEROPHI-CFG-11 (7 nm FCBGA-256) with redundancy MUX

Flash Storage 2× Samsung PM9A3 2 TB M.2 22110, RAID-1, 2 TB usable

Backhaul 2× 40 GbE QSFP+ (80 Gbit/s aggregate) + 25 GbE SFP28 + 1 GbE RJ45

Power 48 V PoE++ or 24 V DC, 250 W peak; ~55 W idle, 240 W peak

Timing PTP subordinate (locks to upstream T2 grandmaster via QSFP+); TCXO 100 MHz; 30-minute ±10 µs holdover

T6 Endpoint Reference — Module for Handsets, Wearables, IoT

The smallest form-factor AeroPhi node. 13 components, 149 pins.

Property Value

Form Factor 45 × 30 × 1.6 mm

PCB Stack-up 6 layers, 1.0 mm, FR-4

Operating Temp −20 °C to +70 °C

Silicon 1× AEROPHI-CFG-01 (22 nm QFN-56, 8 × 8 mm)

RF Frontend Single-channel: 1× TI LMH2828 amp + 1× Skyworks SKY73305 diplexer; SMA-F edge (U.FL alternate footprint)

Host Interface 20-pin 2 mm connector: SPI (≤ 20 MHz) + I2C (400 kHz fast mode) + IRQ + nRESET + UART + CLK_25M + 2× GPIO

Power 3.3 V from host; 200 mW idle (~60 mA), 800 mW peak (~250 mA)

Boot Flash Micron MT25QL256 256 Mbit NOR SPI

Boot Modes Standalone (BOOT_MODE=0, boots from on-board NOR) or Host-loaded (BOOT_MODE=1, firmware via SPI within 200 ms)

Debug 10-pin ARM SWD header (bench-only); 2× status LEDs (alive, link)

T1 Satellite Payload — Space-Flight-Qualified Node

On-orbit node that closes the long-baseline coherence loop. Co-manifest payload for the NCS-19 satellite bus (portfolio Project 19). 42 components, 632 pins.

Property Value

Form Factor 233.35 × 160 mm (6U CompactPCI-serial Space)

PCB Stack-up 14 layers, 2.4 mm, polyimide-based rad-tolerant substrate

Operating Temp −40 °C to +85 °C qualified; −55 °C to +105 °C survival

Vibration 25 g rms random (Falcon 9, launch)

Radiation 100 krad TID + SEE-immune to LET 60 MeV·cm²/mg

Silicon 4× AEROPHI-CFG-16 (5 nm rad-hard BGA-196) in cold-redundant quad: Primary (hot) + Hot-Spare (armed, receive-only) + Cold-A (unpowered) + Cold-B (terminal backup)

Power Dual 28 V spacecraft bus (A/B); 8× Cobham RHFL4913 rad-hard DC-DC converters; 40 W avg, 90 W peak

Host Connectivity 2× SpaceWire (Cobham UT200SpWPHY01) @ 200 Mbit/s per ECSS-E-ST-50-12C

Data Interface 4× TI DS90LV018 LVDS/RS-422 @ 800 Mbit/s each (3.2 Gbit/s aggregate)

RF Frontend 4 channels: 4× LMH2828 space-grade (MIL-STD-883 screened) + 4× SKY73305 space-grade; SMA-F edge connectors for ground-test coupon only

Housekeeping TI ADS1258 16-ch 24-bit ADC (JAN-Q rad-tolerant); 4× RTDs, 8× rail voltages, 4× current shunts

Boot Flash Cobham UT8QNF1M8 1M × 8 NOR flash (100 krad TID); dual-image A/B failover

Deployables 2× redundant pyro channels for antenna deployment + 1× survival heater output; Cobham RH1553Pyro driver with double-latch safety

Clocks Q-Tech rad-hard TCXOs: 100 MHz reference, 20 GHz QBeam PHY, 10 MHz payload sync, 100 MHz backup

Primary Connectors MIL-DTL-38999/26 15-pin (power) + Glenair MDM-9 SpaceWire (2 ports) + Glenair Micro-D 51-pin (mission data)

Lifetime Extension Cold-side ASICs (U3, U4) reduce TID accumulation by ≥ 80%; estimated 3–4× lifetime vs. hot-hot pair

Firmware & Protocol Stack

C QBeam Protocol Stack (firmware/protocol/)

Property Value

Language C99, portable

Files aerophi_protocol.h (~150 lines public API) + aerophi_protocol.c (~280 lines reference implementation)

Portability Bare-metal (ARM Cortex-M4+, RISC-V rv32/rv64), POSIX (Linux, BSD, macOS), Windows (MSVC or clang)

Implements Packet framer/unframer, LDPC codec, RS codec, AES-256-GCM, ML-KEM, fractal-router state machine, aerial flash-server controller, sovereign-domain policy engine

API Functions aerophi_frame(), aerophi_unframe(), aerophi_policy_check(), aerophi_make_beacon(), aerophi_make_route_announce()

Error Codes AEROPHI_OK, ERR_TOO_SHORT, ERR_VERSION, ERR_FEC, ERR_DECRYPT, ERR_POLICY, ERR_SOVEREIGN, ERR_TIER_MASK, ERR_INTERNAL

Rust Fractal-Mesh Routing Daemon (firmware/mesh/)

Property Value

Language Rust (stable toolchain)

Target Any T2–T4 node

Binary aerophid (reference daemon)

Modules lib.rs (public types), state_machine.rs (7-state pipeline), policy.rs (sovereign-domain enforcement), announce.rs (ROUTE_ANNOUNCE / ROUTE_WITHDRAW handlers), store.rs (aerial flash-server backend trait + in-memory impl)

Handles Mesh discovery, convergence, sovereign-domain routing, aerial flash-server load balancing, live QBeam telemetry

Endpoint SDKs

SDK Language Interface Target Tiers Detail

C SDK C99 aerophi_sdk.h (header-only reference) T5–T6 Socket-like API: aerophi_open(), aerophi_close(), aerophi_send(), aerophi_recv(); wraps the C protocol stack

Python SDK Python 3.10+ pip-installable package: from aerophi import Connection, Tier T5–T6 Context-manager pattern; Tier, PacketType, Header, Connection classes; 496-byte max payload per packet

Rust Crate Rust (stable) aerophi crate, no_std friendly T5–T6 Tier, PacketType, Header, Connection, Error types; zero-alloc no_std support for bare-metal T6 endpoints

Sovereign Deployment

Onboarding Checklist

Sovereign domain allocated (16-bit identifier assigned by the inventor).
Sovereign root key ceremony: 4096-bit RSA or 384-bit ECDSA root key, split into 5 shares via Shamir’s Secret Sharing (3-of-5 threshold).
Sovereign authority public key distributed to every AeroPhi node.
Sovereign policy YAML defines allowed tier masks, cross-sovereign peers, retention windows, audit-log destinations.
Sovereign audit trail destination: sovereign-owned SIEM, the American Dollar Blockchain (portfolio Project 6), or both.

Deployment Phases

Phase Scope Success Criteria

Pilot (3 towers) 3-tower metropolitan triangle bring-up Round-trip P99 ≤ 15 ms intra-metro, ≤ 40 ms cross-national; flash hit rate ≥ 80%; zero sovereign-domain leakage

Metropolitan (60 towers) Single-metro AeroPhi mesh for carrier, municipal utility, or campus Flash hit rate ≥ 85%; zero policy violations per day

Sovereign National (1,200 towers) Full national coverage with T1–T6 tiers End-to-end mesh operation across all six tiers; sovereign audit trail operational

T2 Anchor Site Requirements

1× T5 rack chassis (2U) with 2× AEROPHI-CFG-10 (7 nm) for redundancy
2× 100 GbE fibre uplinks to peer T2 anchors
4× 25 GbE fibre downlinks to T3 towers
8× NVMe flash arrays, 8 TB each, RAID-10
HSM (hardware security module) for sovereign root key material
Tier III+ datacenter under sovereign operational control; 5 kW rack power minimum; N+1 redundant cooling

Integration with cri-one.com Portfolio

Sibling Project Relationship

ExitPhi (App# 19/722,805) Provides CoolBeam (thermal integrity) + PipeBeam (temporal alignment) + QBeam (quantum-data carrier). AeroPhi is the mesh-scale deployment of ExitPhi.

NCS-19 Communications Satellite (Project 19) T1 flagship node — the geostationary QBeam beacon. AeroPhi’s T1 payload flies as a co-manifest passenger.

WFA Silicon (Project 54) Terminates QBeam into WiFi 7 at T3–T4 tiers.

UniPhi Retroactive Wireless Adapter (Project 53, App# 19/717,706) T5–T6 layer that adapts any legacy PC/device into a QBeam endpoint.

Super Dome + American Dollar Blockchain (Project 6) Encryption + ledger layer that rides on top of the mesh at every tier.

AutoPhi Future (Project 18) Underlying voxel-as-cell silicon architecture used in every AEROPHI-CFG.

Day-One Fabrication (Project 21) Tape-out production stack for every AEROPHI-CFG.

AutoPhi 1Z Accelerator (Project 23) Can be hosted at T2 or T3 for high-density inference/compute workloads.

Invention Record Anchors

Cluster Entry Numbers AeroPhi Tier

Aerial Flash-Server (cell tower cloud storage) 989, 990, 991, 992, 993, 994, 995 T2–T3

1-Light-Trigger / cold-light microchip / digital optics 1 T6 on-die QBeam origin

QBeam / photon-carrier (cubit function languages) 926, 927, 928 QBeam protocol root

Fractal encryption / routing 110, 324, 347, 348 Scale-invariance crypto + routing

Directive cloud / travel cloud 1051, 1424, 1425, 1426 T2–T5 routing + sovereignty

Micro-cloud / one-server 972, 973 T5–T6 minimum cell

Cell tower broadcast property 948, 49, 102 T1–T3 governance + licensing

Inter-satellite 104; NCS-19 (Project 19) T1 satellite support

Test Harnesses

Test Suite Purpose Verifies

Coherence Test (tests/coherence/) End-to-end QBeam round-trip: T6 → T1 → T6 across 12 hops Byte-for-byte payload identity; per-tier latency budgets met; aerial flash-server receipts committed at each T3 hop; sovereign-domain enforcement passed at each hop; zero FEC failures

Convergence Test (tests/convergence/) Fractal-mesh routing algorithm convergence N routes converge across all nodes within one BEACON period; no routing loops; ROUTE_WITHDRAW drops route from every peer within one BEACON period; sovereign-authority signature rejects unsigned/wrongly-signed ROUTE_ANNOUNCE

Normative References

Reference Subject

USPTO App 19/722,805 ExitPhi, 30 claims, CoolBeam + PipeBeam + QBeam integrated system

USPTO App 19/717,706 UniPhi Retroactive Wireless Adapter, T5–T6 endpoint adapter reference

FIPS PUB 197 Advanced Encryption Standard (AES)

NIST SP 800-208 Stateful hash-based signature schemes

3GPP TS 38.104 NR base station radio transmission and reception (T3 tower interoperability)

IEC 60529 Degrees of protection provided by enclosures (IP code)

MIL-STD-461F EMI requirements (CE102/CE106 for satellite payload)

MIL-STD-883 Test method standards for microcircuits (space-grade screening)

ECSS-E-ST-50-12C SpaceWire standard

IEEE 1588 Precision Time Protocol (PTP)

IPC-2221 Generic standard on printed board design (Class 2 industrial; Class 3 defence/space recommended)

Maturity Report

Subsystem Status Detail

Concept + architecture + protocol spec Production-quality documents Complete six-tier architecture, QBeam propagation protocol, sovereign-deployment playbook

T3 Tower Node schematic Genuine 61-component reference Not yet PCB-laid out; no Gerbers

T3 Enclosure Genuine parametric OpenSCAD model Fabrication-ready; no IP66 certification test report yet

T2 Continental Anchor schematic Full 4U rack-card schematic Complete with PTP grandmaster + GNSS + OCXO

T5 Rack Node schematic Genuine 62-component reference Cold-redundant primary/secondary with full front-panel design

T6 Endpoint Ref schematic Genuine 13-component reference Module-level integration reference

T1 Satellite Payload schematic Genuine 42-component reference Cold-redundant quad with full rad-hard power tree; SpaceWire + LVDS + pyro

20 Silicon Configurations FOUNDRY_HANDOFF.md each Vendor-realistic anchors; no GDSII/LEF/DEF yet

AERO_TX_ASIC RTL Genuine module structure + interfaces 7-module scaffolding; placeholder crypto

Firmware (C + Rust) Genuine skeletons matching C99 protocol spec Placeholder crypto backend (production build should link certified core)

SDKs (C / Python / Rust) Reference implementations C header-only; Python pip-installable; Rust no_std friendly

Test Harnesses Both PASS Synthetic hop simulation, not real network

What is NOT yet in hand (buyer / acquirer / licensee scope): silicon tape-out of any AEROPHI-CFG (gated by AutoPhi / foundry partner); PCB layout files and Gerbers for all tiers; field-deployment tests on real cell-tower hardware; long-baseline coherence measurements over intercontinental spans; FCC / ETSI radio-emissions compliance filings; FIPS 140-3 crypto module certification; ESA / NASA parts approval for T1 payload.

What Is in the Package

Category Item Count / Detail

Documentation AEROPHI_CONCEPT.md Concept + architecture note with one-sentence pitch and six-tier definition

SPEC.md Top-level technical specification (11 sections, rev 0.1)

HANDOFF.md Session handoff notes and honest maturity report

AEROPHI_IP_REFERENCES.md IP catalog anchors: 40+ invention entry cross-references

RENDER_SPECIFICATION.md Photorealistic render specification for T3 enclosure

docs/ARCHITECTURE.md Six-tier fractal mesh architecture in detail (10 sections)

docs/QBEAM_PROTOCOL.md Bit-exact QBeam packet format specification (12 sections)

docs/FRACTAL_MESH_ROUTING.md Fractal mesh routing algorithm with 7-state pipeline and convergence proof sketch (11 sections)

Deployment Guides docs/SOVEREIGN_DEPLOYMENT.md Sovereign deployment operational guide (8 sections): onboarding, silicon procurement, T3 fleet, T2 anchor, T1 payload, endpoint fleet, operations, incident response

examples/*.yaml (3 files) sovereign_deployment.example.yaml, metropolitan_metro.example.yaml, pilot.example.yaml

Hardware — Schematics T3_TOWER_NODE/aerophi_t3_tower.kicad_sch 61 components, 563 pins, 517 named nets (KiCad-10)

T2_CONTINENTAL_ANCHOR/aerophi_t2_continental.kicad_sch 4U rack card with 4× ASIC + Xeon-D + PTP grandmaster + GNSS

T5_RACK_NODE/aerophi_t5_rack.kicad_sch 62 components, 704 pins, dual PSU, cold-redundant ASIC pair

T4_FACILITY_CLUSTER/aerophi_t4_facility.kicad_sch Campus-scale aggregator, 2× ASIC, 2× 40 GbE QSFP+

T6_ENDPOINT_REF/aerophi_t6_endpoint.kicad_sch 13 components, 149 pins, module-level integration

T1_SATELLITE_PAYLOAD/aerophi_t1_sat.kicad_sch 42 components, 632 pins, cold-redundant quad, rad-hard

hardware/gen_schematic.py Generator script for all six tier board schematics

Hardware — Board Specs SPEC.md per tier (6 files) T1, T2, T3, T4, T5, T6 board specifications

BOM.csv per tier (6 files) Bills of materials with vendor part numbers

LAYOUT_HINT.md per tier (6 files) PCB layout guidance for the CM

T3_TOWER_ENCLOSURE/enclosure.scad OpenSCAD parametric weatherproof enclosure model (IP66)

T3_TOWER_ENCLOSURE/README.md Enclosure fabrication, rendering, and customisation guide

AERO_TX_ASIC/SPEC.md ASIC silicon specification (8 sections): blocks, feature flags, clocking, pinout, verification

Silicon Configs FOUNDRY_HANDOFF.md × 20 CFG-01 through CFG-20 (22 nm to 3 nm); generated by hardware/gen_configs.py

RTL (Verilog) rtl/aerophi_top.v Top-level integration

rtl/aerophi_qbeam_tx.v Packet framer, FEC encode, PHY handoff

rtl/aerophi_qbeam_rx.v PHY receive, FEC decode, header parse

rtl/aerophi_mesh_router.v Fractal-router state machine + route table

rtl/aerophi_afs.v Aerial flash-server controller

rtl/aerophi_crypto.v AES-256-GCM + optional ML-KEM

rtl/aerophi_scale_invariant.v Tier mask decoder, replay-window check

Firmware firmware/protocol/ (C99) aerophi_protocol.h (~150 lines) + aerophi_protocol.c (~280 lines): QBeam protocol stack

firmware/mesh/ (Rust) 5 source modules + aerophid binary: fractal-mesh routing daemon

SDKs sdk/c/aerophi_sdk.h C endpoint SDK (header-only reference)

sdk/python/aerophi/__init__.py Python pip-installable endpoint SDK

sdk/rust/src/lib.rs Rust no_std friendly endpoint crate

Test Harnesses tests/coherence/coherence_test.py 12-hop end-to-end coherence test (T6 → T1 → T6)

tests/convergence/convergence_test.py Routing-table convergence test (configurable node/route count)

Figures & Diagrams figures/fig01–fig05.svg 5 architecture SVGs: six-tier mesh, trickle-down, tower retrofit, QBeam packet, sovereign mesh

figures/aerophi_symbol.svg + store display SVGs + PNGs Symbol, store display, and icon graphics in multiple resolutions (512, 256, 200, 64 px)

Machine-Readable MANIFEST.json Project manifest: SKUs, product line, relationships, file index

How This Is Delivered

This package ships on a single Blu-ray disc, posted to the delivery address on your order. The archive on the disc is AES-256 encrypted; the passphrase is sent separately, by email, once the disc is despatched — so the disc alone is of no use to anyone who intercepts it.

Discs are despatched by tracked, signed-for post. Allow 5 business days for mastering and verification before despatch.

Footnotes

Product number 8505.
Family: qbeam.
Purchase: When you buy, you buy the use of that blueprint only.

Reviews

Write Your Own Review