Psi Tether
The Psi Tether is a paired-operator Psi-Tech module that binds two HelmKit Mk1+ units into a low-bandwidth coherence-sharing link for the duration of a defined session. Engineering-honestly, it is a synchronized HRV-coherence biofeedback channel between two operators, mediated by the Psi Mesh; doctrinally, it is the technological reflection of the Tho'ra Clan's pair-bond practice — two operators with their gear coupled staying in coordinated state through a high-stress evolution.
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
A Tether session, in protocol:
- Two operators consent and pair their HelmKits via short-range NFC + Resonant-Card co-signature.
- The Tether bonds their Psi Stabilizer coherence channels; each operator's anchor signal is informed by both biosignals.
- Tether-active is visibly indicated to both operators (HUD ring color, audible tone).
- Either operator can break the Tether instantly; the lanyard breaks both ends simultaneously.
Tether use cases: Resonant Pipeline paired contact, high-stress operator rotation, mentor–trainee field exercises, joint analysis seats at StarCom.
Theoretical Basis
- 2e7d32;"
Epistemic status: [[
|
HRV-coherence biofeedback works in single-operator mode (the Psi Stabilizer base layer). Sharing biosignals between consenting people improves joint regulation in clinical co-regulation studies.
- 1565c0;"
Epistemic status: [[
|
Two operators using a Tether maintain joint coherence longer under stress than two operators with independent Stabilizers. Pre-registered, falsifiable.
- c62828;"
Epistemic status: [[
|
The Tether also couples operator Psi Field states beyond what biosignal-sharing alone accounts for. This is the Tho'ra-doctrinal layer; engineering utility does not depend on it.
Subsystems and BOM
Mk0 (target ≤ \$10 / pair)
Operators sit shoulder-to-shoulder with synchronized Psi Stabilizer Mk0 anchor practice — verbal pacing, shared breath count. No hardware coupling. Demonstrates the practice; obviously limited.
Mk1 (per HelmKit, adds ≤ \$80)
- Tether software stack — included with HelmKit Mk1 firmware
- nRF52840 short-range secure pairing — already in HelmKit Mk1
- Psi Mesh frame format for Tether traffic — software
- Per-operator key co-signing logic — software
- HUD ring color change for tether-active — firmware
- Bone-conduction tether-tone — already in HelmKit Mk1
- Per-session cryptographic key (Diffie-Hellman over Resonant Cards) — software
The Mk1 is mostly software riding on HelmKit Mk1 hardware. Per-pair hardware adds ≈\$0.
Mk2 / Mk3
Mk2: 3+ operator tether ("Tether Mesh"); shared marker channel on Focus Lens; safety-supervised joint emission caps. Mk3: integration with Resonant Pipeline and Star Seer live records; documented tether topology preserved in session records.
Build Notes
- Per-session keys. Each Tether session uses an ephemeral keypair derived at pair time; no long-lived shared secrets.
- Both consent or no Tether. Pairing requires NFC contact from both Resonant Cards within a 5-second window.
- Joint emission cap. MCU-B enforces that the joint Stabilizer envelope cannot exceed single-operator caps for either side.
- Visibility. Tether-active state must be visible to both operators at all times. No covert tether.
Safety and Ethics
- No tether without mutual consent at session start.
- Either operator's lanyard kills both ends.
- The Tether shares coherence digests, not raw biosignals. The Psi Recorder keeps raw signals local.
- No tether between non-equal parties (e.g. handler–subject). Tho'ra doctrine: tether is between peers.
- No tether to non-consenting third parties under any circumstance.
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
- One operator destabilizes the pair. → Stabilizer interlock per side; auto-disengage if either operator's baseline drifts.
- Lost pairing key. → Ephemeral keys; new pair = new key.
- Covert tether attempt. → State always visible; covert mode physically disabled.
- Non-peer tether. → Doctrinal prohibition; mentor–trainee tether explicitly documented as time-bounded training use.
- Tether-fatigue. → Default session ≤ 60 minutes; mandatory cool-down.
- Operator coercion in pair-bond. → Mutual-consent gating at session start; either side can break instantly.