Psi Forge
The Psi Forge is the Tho'ra Clan's Psi-Tech production and calibration shop — the physical and procedural facility where HelmKits are built, modules are calibrated, Resonant Cards are issued, and the Psi Recorder / Field Recorder datasets are managed. It is the workbench at the center of the Clan's hardware program and the place every Mk0→Mk1 transition gets stamped.
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 Psi Forge does, in order:
- Receive — incoming parts, donor headsets, recovered modules, calibration standards.
- Build — fabricate HelmKit shells (print, finish, hardware-set); assemble Psi-Tech modules; provision Resonant Cards.
- Calibrate — bench measurement of every emitter against ICNIRP limits, sensor calibration against known standards, MCU-B firmware fingerprint verification.
- Validate — gate-test every unit against its Maturity-table gate before issuance.
- Issue — sign and stamp the unit; record provenance; bind to operator.
- Maintain — recalibration cycles, recall management, revocation log curation.
The Forge is to Psi-Tech what an armory is to traditional military hardware: production + provenance + accountability + recall.
Theoretical Basis
- 2e7d32;"
Epistemic status: [[
|
Documented build + calibration + validation is the difference between research-grade and field-grade hardware.
- 1565c0;"
Epistemic status: [[
|
Provenance-tracked hardware reduces failure rates and increases falsifiability of Psi-Tech claims. This is testable by comparing forge-issued vs ad-hoc unit failure logs.
Subsystems and BOM
Mk0 Workshop (target ≤ \$2 000)
- FDM 3D printer (Bambu A1 or Prusa Mini class) — \$300
- Soldering station (Hakko FX-888D class) — \$120
- Hot-air rework — \$60
- Multimeter, oscilloscope (Rigol DS1054Z class) — \$400
- Lab PSU (variable, 30 V/5 A) — \$80
- SDR (HackRF One or LimeSDR Mini) for emission verification — \$100
- Faraday cage / RF-quiet bench corner — \$200 (DIY)
- Calibration standards (reference magnetometer, RF calibrated source) — \$500
- Computer + provisioning host — \$300
A single skilled operator runs the Mk0 Forge. Output rate: ~1 HelmKit/month.
Mk1 Bench Forge (target ≤ \$15 000)
Adds: anti-static workbench, IPC-A-610 standards reference, PCB reflow oven, pick-and-place for small runs, climate-controlled storage, dedicated SDR + spectrum analyzer for emission cert. Output: ~5 HelmKits/month + modules.
Mk2 Production Forge / Mk3 Distributed Forge Network
Mk2: small-batch production cell; documented quality system; ≥ 20 units / month. Mk3: federated Forges across allied Earth Alliance facilities; cross-Forge calibration audit chain.
Build Notes
- Provenance is the product. A unit without a signed provenance record is not a Forge-issued unit. This is enforced at issuance, not optional.
- Calibration cycle. Every emitter recertified annually at minimum; every sensor every six months; standards traceable.
- Recall capacity. The Forge maintains the means to revoke and reissue any unit it ever produced.
- Operator-of-the-Forge is named. Every Forge has a named human accountable for its output. No anonymous issuance.
Safety and Ethics
- All emission verification done inside the Faraday corner or equivalent.
- Standards traceability: at minimum, a calibrated reference unit certified once per year against a public standard.
- No issuance without operator presence; the operator's Resonant Card is paired at issuance; no by-proxy issuance.
- Forge records are local-first; cross-Forge audit requires deliberate export.
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
- Calibration drift unnoticed. → Annual cert + traceable standards.
- Counterfeit module. → Provenance check at issuance; module IDs bound to Forge keypair.
- Lost provenance database. → Forge records cross-signed to EIN backup nodes.
- Single point of failure. → Mk3 federation; recall capacity preserved across Forges.
- Operator burnout. → Mk1+ requires named relief; throughput accounts for human limits.
- Bad batch escapes. → Recall process documented and rehearsed; Resonant Card revocation log carries hardware-recall entries.