Research-Stack/airtable_import_guide.md
Brandon Schneider e5fb0a5f4d chore: commit accumulated working tree changes
Lean: update Semantics modules, add new numerics/physics data files
Hardware: update FPGA bitstreams (tangnano9k_uart_loopback)
Infra: k3s-flake tests, netcup-vps configuration, VCN compute substrate
Docs: ARCHITECTURE, specs, citation updates
2026-05-30 00:10:02 -05:00

149 lines
No EOL
5.8 KiB
Markdown

# Airtable Import Guide for Compute Substrate Research Database
## Overview
This database encodes all the compute substrate research we discussed, from $10 embedded morphic field computers to EPYC fabric configurations, with comprehensive performance metrics and scaling analysis.
## Files Generated
### 1. Schema Definition
**File:** `airtable_compute_substrate_schema.json`
- Complete Airtable schema with 7 tables
- Field definitions with types and options
- Ready for Airtable API import
### 2. Hardware Substrates Table
**File:** `airtable_hardware_substrates.csv`
- 7 compute substrates with full specifications
- Categories: Physical Entropy, Harvested Cycles, Display Interface, Empirical Discovery, Coordination, Overkill
- Cost/bandwidth/complexity metrics
- Lean and Python implementation references
### 3. Math Workloads Table
**File:** `airtable_math_workloads.csv`
- 7 mathematical workloads with optimal substrate mapping
- Categories: Fractal Geometry, Cellular Automata, Game Theory, Soliton Fields, Sidon Sets, Topology
- Complexity and parallelizability analysis
- Physical grounding and display requirements
### 4. Performance Metrics Table
**File:** `airtable_performance_metrics.csv`
- Detailed performance for each substrate-workload combination
- Operations/sec, bytes/sec, ops/$ ratios
- Power, latency, scalability, efficiency ratings
- Performance notes and considerations
### 5. Scaling Analysis Table
**File:** `airtable_scaling_analysis.csv`
- Hardware class evolution from 6502 to EPYC SP5
- Cost/performance scaling analysis
- Sweet spot identification (ARM1, Core 2, Pi 2W)
- Value ratio calculations (performance gain per cost increase)
### 6. Integration Patterns Table
**File:** `airtable_integration_patterns.csv`
- 6 integration patterns combining multiple substrates
- Cost/performance for combined configurations
- Use case targeting (Embedded, Desktop, Server, Data Center, Research)
- Complexity and scalability analysis
### 7. Optimal Configurations Table
**File:** `airtable_optimal_configurations.csv`
- 7 recommended hardware configurations
- Target use cases (Ultra-Low-Cost, Research, Production, High-Performance)
- Hardware, entropy source, harvested substrates, display interface
- Expected performance and value ratios
## Import Instructions
### Option 1: Manual Airtable Import
1. Create a new Airtable base named "Compute Substrate Research"
2. For each CSV file:
- Create a table matching the file name
- Import the CSV data
- Set field types according to the schema
3. For the schema JSON:
- Use Airtable's API or manual table creation
- Configure field types and options
### Option 2: Airtable API Import
Use the Airtable API to programmatically create the base and tables:
```bash
# Example using Airtable API (requires API key)
curl -X POST https://api.airtable.com/v0/bases \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d @airtable_compute_substrate_schema.json
```
## Key Insights Encoded
### 1. Infinite Ops/$ Substrates
- **TOSLINK Entropy**: Physical optical imperfections as deterministic stochastic channel
- **USB-C to SFP**: Modern optical entropy with hot-swappable SFP modules
- **PCIe Idle Cycles**: Link state machine idle cycles as free compute
- **HDMI TMDS Abuse**: Display cable as N-dimensional soliton field transport
- **DisplayPort Texel**: 8K60 texel transport with NVENC acceleration
### 2. Optimal Cost-Performance Sweet Spot
- **$10-200 range**: ARM to mid-range CPU class
- **Pi 2W winner**: 1.3M ops/$ (modern ARM efficiency)
- **Performance gains exceed costs** up to ~$200
- **Beyond $200**: Costs exceed performance gains (EPYC is overkill for simple math)
### 3. Spatiotemporal RAM Innovation
- **1km+ fiber spool**: Light propagation delay = memory addressing
- **5μs propagation**: 5,000 temporal memory slots
- **1,000 spatial slots**: Physical fiber length addressing
- **5M total spatiotemporal locations**: 4D compute substrate
- **Zero power storage**: Fiber stores data in light propagation
### 4. Simple Math Advantage
- **Menger sponge QR**: XOR, bit shifts, addition (perfect for cheap hardware)
- **No complex operations**: No floating point, no transcendental functions
- **Cache-friendly**: L1/L2 cache sufficient for N=64 lattice
- **Embarrassingly parallel**: Linear scaling across cores
### 5. Network Effects
- **Distributed quine**: s_next(Node_i) = e(Node_j) across network
- **Communication costs**: Λ_net = Λ_local + λ·d_torus
- **TOSLINK latency**: Actually matters for networked evolution
- **Fiber delay line**: NetworkRAM addressing via DriftTensor
## Usage Examples
### Query: "What's the best substrate for Menger sponge QR?"
```sql
SELECT * FROM "Math Workloads"
WHERE "Workload Name" = "Menger Sponge QR"
```
→ Returns: MCU + USB-C SFP (simple math + physical entropy)
### Query: "What substrates have infinite ops/$?"
```sql
SELECT * FROM "Hardware Substrates"
WHERE "Ops/$" = "Infinite"
```
→ Returns: TOSLINK, USB-C to SFP, PCIe Idle, HDMI TMDS, DisplayPort
### Query: "What's the sweet spot in hardware scaling?"
```sql
SELECT * FROM "Scaling Analysis"
WHERE "Sweet Spot" = TRUE
```
→ Returns: ARM1, Core 2, Pi 2W (optimal cost-performance range)
### Query: "What's the optimal $10 configuration?"
```sql
SELECT * FROM "Optimal Configurations"
WHERE "Total Cost" = 10
```
→ Returns: $10 Morphic Field Computer with spatiotemporal RAM
## Notes
- All performance metrics are estimates based on the research discussed
- "Infinite" ops/$ means the substrate is already paid for (harvested cycles)
- Performance ratios assume simple math operations (XOR, shifts, addition)
- Complex math workloads may favor different substrates
- Spatiotemporal RAM capacity depends on fiber length and optical quality
- Network latency effects are not included in base performance metrics