io.github.farssaadeldin7-ux/haptic-feedback-mapper

Open the Stripe billing portal to change plan, update the card, or cancel the Haptic Feedback Mapper subscription.

Append one mapped event to the local event log, atomically, validated against the exported profile: the line carries the event id, class, the pattern's amplitude/duration/repeat tuple, priority and cooldown, as NDJSON at ${XDG_CONFIG_HOME:-$HOME/.config}/plugin-suite/haptic-feedback-mapper-events.log — the bridge any watching haptic driver turns into the actual vibration. Structured errors for unmapped events (unmapped_event), events a profile maps to silence (silent_event), and a missing profile (no_profile). This server appends the line; it drives no hardware. Requires a paid plan.

The four event classes — act_now, done, ambient, noise — each with its criterion, its channel, and examples, plus the one rule, the no-decision rule and the distribution note. Reference data only; mapping_audit is what checks a recorded mapping against it. Omit class for all four.

Compile a designed mapping and vocabulary into ready-to-use artefacts in a caller-supplied directory: a canonical JSON profile (event id, class, priority, cooldown, and the pattern as an amplitude/duration/repeat tuple derived from the vocabulary axes) plus a POSIX-sh "notify" hook that appends a timestamped NDJSON line per mapped event to the local event log — the documented contract any haptic driver, Stream Deck plugin or automation tool can watch. The mapping is checked against the mapping_audit and vocabulary_check rules first, and an export that fails its own audit is refused with the failures named. The plugin designs and exports the mapping and emits events; the hardware driver on the user's machine does the vibrating — no haptic hardware is driven directly. Requires a paid plan.

Store and activate a Haptic Feedback Mapper licence key on this machine. Use when the user pastes a licence key, or after a purchase completes.

Check the Haptic Feedback Mapper licence on this machine: plan, included capabilities, remaining quota and seat usage. Call this when a paid tool reports a licence problem, or when the user asks what their plan includes.

List the available Haptic Feedback Mapper plans, prices and what each one includes.

The load arithmetic: checks/day x refocus minutes x working days, at the conservative floor and the literature figure (and a caller-supplied figure if given), as minutes/day, hours/week and hours/year — priced at the buyer's hourly rate when one is passed. Every assumption is echoed back for showing next to the numbers. Arithmetic only: it does not measure anything, and the result is labelled a projection, not a gain. Requires a paid plan.

Record one working session's counts in the local measurement log: phase (baseline before the mapping ships, after once it has), duration, screen checks, and — after only — haptics delivered and acted on, which feed the trust metric. Requires a paid plan. Nothing leaves this machine.

A recorded event->class mapping checked mechanically against the stated rules, with the entries quoted: ambient or noise events carrying a haptic, act_now/done events without one, events feeding no decision, the act_now ceiling, and the class distribution with its quiet share. Facts only — it never decides which class an event belongs in. Requires a paid plan.

The refocus-cost figures the load arithmetic runs at: the conservative glance-level floor and the interruption-recovery literature range, each with its basis and its limits stated, plus the rule that every shown number names its figure. Reference data only — the figures are borrowed from office task-switching research, not measured in studios, which is why the method computes with both bounds.

The measurement log with its computed position: per-phase checks-per-hour averages with small-sample notes, the baseline-to-after drop share, the trust metric (share of delivered haptics acted on) with the crying-wolf flag, and the stated usual causes when checks did not drop. Counting and division only; whether the sessions were comparable is the user's claim to defend. Requires a paid plan.

Begin a Haptic Feedback Mapper purchase. Returns a Stripe Checkout link. Call list_plans first if the user has not chosen a plan.

A proposed pattern set checked mechanically against the vocabulary rules, with the evidence quoted: the 3-5 limit, duplicate meanings, collisions on the count/intensity/rhythm axes, pairs that differ only in intensity, and the failure-distinctiveness rule. Facts only — whether the patterns feel different on real hardware is what the blind test decides. Requires a paid plan.

The vocabulary design constraints: 3-5 patterns, one meaning each, the three axes untrained users can actually distinguish (count, intensity, rhythm), the failure-distinctiveness rule, the fallback requirement, and the blind test. Reference data only; vocabulary_check is what measures a proposed set against it.