Psionic User Interface

The Psionic User Interface (PUI) is the Tho'ra Clan's design discipline for interfaces between operators and Psi-Tech systems. It is not a single product — it is the rules-of-engagement for how a HelmKit Mk1, a Star Seer HUD, a Psi Stabilizer anchor button, or a Resonant Finder tile feed presents information to and accepts intent from a human under conditions where the operator is also the sensor. A psionic interface is one where the user's biology, attention, and intent are first-class inputs and outputs, not just incidental peripherals.

Overview

The PUI doctrine commits to four principles:

• The operator is always in the loop. No Psi-Tech action engages without operator affirmation. There is no "auto" mode that does not start as a deliberate operator gesture.
• Surface signal, hold meaning. The interface presents signal (a bearing, a coherence delta, an anomaly class) and reserves meaning to the operator. It does not pre-interpret.
• Honest uncertainty. Confidence is always shown. The interface refuses to display a class above its actual confidence.
• Disengage by default. All active modes have an obvious disengage; the lanyard kill works regardless of UI state.

The PUI is also the rule for how astrologically- and psi-derived inputs (chart hash, transit state, Psi Defender threat classification) appear: never as imperatives, always as offers.

Theoretical Basis

1. 2e7d32;"

Epistemic status: [[ Category:Provisional Psi Claims|PROVISIONAL]]

Modern human-factors literature on closed-loop biofeedback and operator-in-the-loop systems supports each PUI principle individually.

1. 1565c0;"

Epistemic status: [[ Category:Testable Psi Claims|TESTABLE]] Theory anchors: Resonant Neurobiology

An interface built on the four PUI principles produces measurably better operator outcomes (fewer over-reliance failures, faster correct decisions, faster disengage) than one without. Falsifiable through A/B field trials.

1. c62828;"

Epistemic status: [[ Category:Speculative Psi Claims|SPECULATIVE]] Theory anchors: Psi Field, Astrological Frequency Harmonics

The PUI is the substrate over which the operator's psi-field state itself becomes a UI input (intent-derived gestures, coherence-gated commands). This is the PsiSys-side ambition; it is not required for the Mk1 utility claim.

Subsystems and BOM

The PUI is implemented across hardware + firmware + ritual:

Hardware affordances

• Hard kill lanyard — operator-grippable, breakaway, severs upstream power. Mandatory on every HelmKit Mk1+.
• Anchor button — single physical button on the Psi Stabilizer module; engages an operator-triggered anchor window. No software replacement.
• Status ring — visible-spectrum LED ring on every active module showing standby / armed / emit / fault.
• Bone-conduction discreet channel — audio cues delivered without occluding ambient hearing.

Firmware contracts

• Confidence-first display. Every numeric or class output carries a confidence figure; UI refuses to render above-actual confidence.
• Engage gating. Every engagement-mode transition is logged in the Psi Recorder with operator affirmation timestamp.
• Telemetry visibility. The operator can read every active emit cycle's parameters at any time; nothing is hidden.

Ritual layer

• Pre-session check. Standardized 60-second pre-session checklist (battery, calibration date, chart hash, baseline HRV). Documented in operator briefing.
• Post-session debrief. Structured marker prompt: what was felt, what was logged, what to revisit.

Build Notes

• No silent failure. Every fault state has a visible and audible signal. The interface never just "stops".
• No silent emission. Every emit cycle lights the status ring and registers a Recorder event.
• No silent calibration. Calibration changes require operator affirmation and are logged.
• Latency floor for safety paths. Kill-to-power-off latency ≤ 100 ms. UI latency targets ≥ 16 fps for moving overlays.

Safety and Ethics

• No operator override of safety interlocks except via documented procedure (e.g. recovery-from-fault), which the Psi Recorder captures fully.
• No third-party UI control. Mesh-shared information may inform; it never commands.
• Accessibility: the PUI supports operators with reduced vision/hearing through redundant channels.
• The interface is documented openly so operators (and outside auditors) can understand what their gear is doing.

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

• Over-reliance on interface. → Default dwell windows; mandatory off-cycles; debrief prompts highlight reliance patterns.
• Confidence inflation. → UI refuses to render above-actual classifier confidence; below-threshold displays "unknown".
• Notification fatigue. → Per-class severity; only safety-critical events use audible channel.
• Hidden emission. → No emit without visible status; firmware contract enforced at MCU-B.
• Operator gesture conflated with intent. → Affirm-then-act gating on every engagement.
• Accessibility gap. → Redundant channels (visible + audible + haptic) mandatory.

See Also

• Psi-Tech
• HelmKit
• HelmKit Architecture
• Psi Stabilizer
• Psi Harmonizer
• Psi Defender
• Psi Recorder
• PsiSys
• Tho'ra Mission Doctrine
• Tho'ra Tech Maturity Levels