Psi Mesh

From FusionGirl Wiki
Revision as of 20:47, 11 May 2026 by JonoThora (talk | contribs) (Phase G: stamp page as defensive publication)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

The Psi Mesh is the Tho'ra Clan's peer-to-peer encrypted radio mesh for HelmKit-equipped operators and Field Recorder units in the field. It carries Psi-Tech telemetry, threat-signature exchange, and operator state-sharing across a small team without depending on cellular or internet infrastructure. The Psi Mesh is the field substrate that the PsiNet and the Earth Intelligence Network connect into when uplink is available, and stands alone when it is not.

Defensive publication notice. This page is published as a defensive publication. Its publication date and content are intended to constitute prior art under 35 U.S.C. § 102 and equivalent international patent law, for the purpose of preventing the patenting of the disclosed subject matter and its obvious extensions by third parties. Reuse is governed by Project:Licensing (CC BY-SA 4.0) for written content; hardware designs disclosed herein are additionally licensed under CERN-OHL-S v2; reference software is GPL-3.0-or-later.

Overview

The Psi Mesh is, architecturally:

  • Layer 1: radio — 433/868/915 MHz LoRa or 2.4 GHz BLE-mesh, operator-jurisdiction-appropriate.
  • Layer 2: routing — Reticulum or B.A.T.M.A.N.-adv, store-and-forward, single-hop and multi-hop transparent.
  • Layer 3: identity — keys from the operator's Resonant Card (or in-helm Mk1 keypair).
  • Layer 4: content — signed Psi-Tech telemetry frames, Psi Defender threat signatures, Psi Recorder session digests, terse text.

Bandwidth is small (kbit/s, not Mbit/s). The mesh is for coordination, not media.

Theoretical Basis

  1. 2e7d32;"
Epistemic status: [[
Category:Provisional Psi Claims|PROVISIONAL]]

LoRa and Reticulum are mature off-grid mesh substrates with documented field deployments.

  1. 2e7d32;"
Epistemic status: [[
Category:Provisional Psi Claims|PROVISIONAL]]

BLE-mesh / Reticulum identity binding through commodity secure-elements is a solved problem.

  1. 1565c0;"
Epistemic status: [[
Category:Testable Psi Claims|TESTABLE]]
Theory anchors: Psionic Threat Model

Real-time team-share of Psi Defender threat signatures materially improves group situational awareness in hostile-EM environments. This is the Mk2 evaluation question.

Subsystems and BOM

Mk0 (target ≤ \$0 per operator)

Group text thread + group voice channel + paper map. Documented as a baseline; the Mk1+ Psi Mesh must outperform this.

Mk1 (per node, target ≤ \$120)

  • nRF52840 + LoRa SX1262 module (RAK4630 or similar) — \$30
  • PCB or wire antenna for chosen band — \$5
  • USB-C battery harness — \$10
  • HelmKit pairing connector (JST-GH) — \$5
  • Enclosure (3D print) — \$10
  • Per-node provisioning amortized

Mk2 / Mk3

Mk2: meshed LoRa + BLE-mesh hybrid, gateway nodes that bridge to EIN when uplink is available. Mk3: integration with the Resonant Pipeline and the Star Seer Observatory feeds.

Build Notes

  • Band per jurisdiction. Operators must use license-exempt bands legal in their region. The mesh stack is band-agnostic.
  • Identity = Resonant Card. Mesh nodes pair to the operator's Resonant Card on first boot; identity is portable across hardware.
  • Frame budget. Default per-operator: 1 telemetry frame / 30 s, 1 threat-signature on detect, text on demand. Higher rates require coordinator approval.
  • No raw biosignal. Biosignals stay on the Psi Recorder; the mesh carries digests and markers only.

Safety and Ethics

  • Encrypted by default. End-to-end via per-operator keypair.
  • Local-first. The mesh does not phone home unless a gateway node is present and consented.
  • Direction-finding hardening. Default duty cycle low; LoRa spreading factor chosen to balance range vs DF-vulnerability.
  • No remote-command of one operator's HelmKit by another. The mesh exchanges information; it does not exchange control.

Maturity

Maturity (Mk0 → Mk3)

See Tho'ra Tech Maturity Levels for the convention.

Mark Phase Status Confidence Evidence Base Next Validation Gate
Mk0 Cosplay-type Complete 100% (symbolic) Ritual + build practice User satisfaction
Mk1 Prototype Active
Mk2 Test-type Planned
Mk3 Production Projected

Failure Modes and Mitigations

  • Duty-cycle violation in regulated band. → Firmware enforces regional duty-cycle caps; operator cannot exceed without re-flash.
  • Lost node = lost key. → Revocation propagated via Resonant Card revocation log.
  • Mesh partition. → Store-and-forward; nodes hold frames for next reachable hop.
  • Direction-finding by adversary. → Low duty cycle; jurisdiction-appropriate spreading factor; emission cap.
  • Sybil attack. → Operator identities bound to issued Resonant Cards; sybils require physical issuance.
  • Operator burdened by mesh. → HelmKit surfaces only actionable mesh events; raw frames stay in the Psi Recorder log.

See Also