Documentation

P31 Labs Documentation

Complete technical documentation for P31 NodeZero, P31 Buffer, P31 Spectrum, and the P31 Compass architecture.

v0.2.1 · Latest release Last updated:
📦 P31 NodeZero Firmware 🧪 P31 Buffer 🔭 P31 Spectrum 🧭 P31 Compass 💚 L.O.V.E. Economy
HARDWARE

P31 NodeZero

ESP32‑S3 firmware, LoRa mesh networking, haptic feedback, and hardware specifications.

View Docs →
No matching documentation found. Try different keywords.

Code Example

Initializing the P31 NodeZero mesh network:

import { NodeOne } from '@p31/node-one';

const node = new NodeOne({
  frequency: 915, // MHz
  meshId: 'p31-delta',
  haptics: true
});

node.on('message', (msg) => {
  console.log('Received:', msg);
});

await node.start();

Detailed Topics

Mesh Routing Protocol (P31 Compass)

The P31 Compass uses a modified AODV (Ad‑hoc On‑Demand Distance Vector) protocol with topology‑aware metric. Each node maintains a routing table with signal strength and path reliability. For full specification, see Routing Protocol.

Haptic Feedback Patterns

P31 NodeZero supports 123 distinct haptic patterns defined in the DRV2605L library. Patterns are grouped into categories: alerts, confirmations, navigation, and data encoding. Refer to the Haptics Reference for waveform tables.

Documentation Philosophy

Why We Document Everything

Documentation is not optional — it's essential. The mesh grows through knowledge, not through code alone.

Transparency: All code is documented. All APIs are documented. All architectures are documented. We don't hide anything. The mesh grows through transparency, not through obscurity.

Accessibility: All documentation is accessible. Clear language. Code examples. Diagrams. The mesh holds for everyone, or it doesn't hold at all.

Completeness: Every function documented. Every parameter explained. Every design decision justified. The mesh grows through understanding, not through mystery.

The Beauty: Just as quantum states exist in superposition until measured, code exists in potential until documented. Documentation is the measurement that collapses the wave function into knowledge. The geometry protects the signal — and documentation makes it accessible.

Documentation Tools

How We Write Docs

Markdown for prose. Code comments for inline documentation. Diagrams for architecture. The mesh grows through multiple formats.

Markdown: All documentation is written in Markdown. Easy to read. Easy to write. Easy to maintain. The mesh grows through simplicity, not through complexity.

Code Comments: Inline documentation in code. Every function documented. Every complex algorithm explained. The mesh grows through clarity, not through mystery.

Diagrams: Architecture diagrams. Data flow diagrams. System topology diagrams. The mesh grows through visualization, not through text alone.

The Beauty: Just as information theory describes signal transmission, documentation describes knowledge transmission. Good documentation maximizes channel capacity by providing clear information (high S/N) and multiple formats (high B). The geometry protects the message.