The original designs. The dated record. The history before the company.
I created the original Pulse concept and designs before R.A.I.N Technologies LLC was formed. Pulse was later renamed HAIL.
I dispute Rain Technology Solutions’ subsequent origin account, including Stone Hazlett’s published account, because it omits my earlier work. This archive presents the dated designs and documents behind that dispute.
An independent historical record published by the original designer. This is not the official Rain Technology Solutions product or support website.
THE PRODUCT CONNECTION
Pulse was the original name. HAIL is the renamed capability.
My April 2019 sketches name Pulse as a plugin within ATAK, part of the Team Awareness Kit (TAK) ecosystem. Those designs combine wearable vital signs, individual and team patient views, and information sharing from the point of injury through evacuation to the hospital.
HAIL stands for Health Awareness Intelligence Logistics. Rain Technology Solutions currently describes it as an ATAK-native medical capability connecting wearable vital signs and the care team. The public ATAK Plugin: HAIL listing still uses the application identifier com.atakmap.android.plugin.rain.pulse.
Pulse and HAIL are the same capability under different names. In my assessment as the original designer, the foundational designs changed very little. The archive below makes my original architecture and interface choices available for direct inspection.
Current product reference: Rain Technology Solutions’ HAIL page. The drawings document the original designs; they are not screenshots of a completed Pulse implementation or a record of every later HAIL feature.
AT A GLANCE
The documented timeline
Original concept
A shared medical picture linking patient, medic, command, MEDEVAC, and hospital. View the architecture.
Pulse workflows and ATAK interface designs
Evacuation workflows, wearable integration, patient views, and device controls. Explore the dated designs.
R.A.I.N Technologies LLC formed
The Wyoming filing follows the original concept and April interface designs. Read the company record.
My departure
The effective date stated in my resignation letter. Read the letter.
Published origin account
An interview with Stone Hazlett describes the origins of HAIL and Rain Technology Solutions. Read the attribution context.
01 / THE DESIGN ARCHIVE
Before HAIL, these were my designs.
Eight original design records, arranged chronologically. The dates below are those displayed in the photo information within each source screenshot. The captions explain the design content; each image links to the complete source at its original URL.
DESIGN 01 ·
The original medical communications architecture
My handwritten concept connects the point of injury, command, a MEDEVAC platform, and the receiving hospital. It describes shared patient status and continuous vital signs across that care pathway.
This workflow maps the delays and repeated verbal relays between a medic, command, and evacuation teams. The proposed Pulse application shares patient status as treatment and evacuation proceed.
The design calls for evacuation crews to see vital signs, medications, and reactions while en route, with information continuing onward to the receiving hospital.
This architecture links a Bluetooth watch to an end-user device running ATAK and Pulse, then distributes patient information over radios to command, evacuation, and hospital nodes.
My interface notes explicitly name the Pulse plugin. They cover starting ATAK, connecting a watch over Bluetooth, ownship and team tabs, connection status, and settings. The phone in the photo provides an ATAK interface reference.
The individual view brings together callsign, coordinates, altitude, range and bearing, medical fields, heart rate, oxygen saturation, and update timestamps.
These are specific connections between the early records and the capability described on the current HAIL product page. They explain why the original designs matter to the product’s history.
Capability
My original record
Current HAIL description
Shared medical picture
2017 architecture links point of injury, command, evacuation, and hospital.
April 2019 workflow shares information before pickup and onward to hospital.
Patient information supporting the evacuation and care pathway.
02 / COMPANY RECORDS
Formation, governance, and departure
The design record precedes the LLC’s formation. These documents provide the subsequent company chronology and the text relevant to my departure.
JUNE 5, 2019
Articles of Organization
The Wyoming filing records the formation of R.A.I.N Technologies LLC on June 5, 2019, filing ID 2019-000859709. That is the legal name shown in this historical document; Rain Technology Solutions is the current product-facing name used above.
The posted agreement names me among the initial managing members. It contains no express invention-assignment or work-for-hire clause, and no intellectual property is itemized as a contribution in Schedule D. The contribution and valuation fields in that schedule are unfilled.
The copy includes organizational-meeting language dated June 5, 2019. Its adoption and member signature lines are unfilled in the posted copy. These observations describe this document; they do not by themselves settle all ownership or membership questions.
Relevant locations: initial managers and manager resignation, page 6; member withdrawal, page 22; Schedule D, page 35.
EFFECTIVE AUGUST 1, 2019
Resignation letter
My letter states an effective resignation date of August 1, 2019 and cites Section 6.2.3 of the Operating Agreement. It contains no express assignment or license of intellectual property and no express release of rights. The second page contains receipt and acceptance wording.
Section 6.2.3 addresses resignation as a manager; the agreement separately addresses member withdrawal. The letter and agreement are provided together so readers can inspect their actual wording.
On December 22, 2025, The Last Mile published Alex Goin’s interview with Stone Hazlett about Rain Technology Solutions and HAIL. Asked where HAIL’s concept came from, Hazlett said it comes from my own background.
I dispute that origin account because it omits my earlier work: the 2017 concept and the April 2019 Pulse architecture, workflows, and interface designs shown here. Pulse was subsequently renamed HAIL. This archive presents the dated material behind my account.
The interview also describes team development using “we.” My disagreement concerns attribution of the original concept and designs; the interview does not expressly say that Hazlett personally created every later component.
The archived PDF is a 14-page browser capture dated January 1, 2026. That capture date is separate from the article’s December 22, 2025 publication date.
In private correspondence, RAIN leadership asserted that the company owned the intellectual property since inception and that I relinquished ownership upon departure. I dispute those assertions. The correspondence is not published here; this public record focuses on the designs and documents readers can inspect directly. The underlying ownership and attribution issues remain unresolved.
COMMON QUESTIONS
HAIL, Pulse, and this archive
Is Pulse the same thing as HAIL?
Yes. Pulse was the original name of the capability I designed; it was later renamed HAIL. My April 2019 design notes explicitly name the Pulse plugin. The current HAIL Google Play listing also retains rain.pulse in its application identifier.
How does HAIL relate to ATAK and TAK?
HAIL is marketed as an ATAK-native medical capability. ATAK belongs to the TAK ecosystem. My original Pulse designs show an ATAK plugin connecting wearable patient data and the wider care team.
Who is publishing this timeline?
I am the original designer of the capability first called Pulse. I created the original concepts and designs presented here and publish this archive to document their provenance.
Where can I find current HAIL product information?