Incident process studio · 2026 · Solo — popularity-led research, immutable graph architecture, test-first persistence hardening, accessibility, editorial interaction design, production verification

Handrail

A local-first incident process studio for placing, joining, moving, undoing, and safely sharing an operational response map.

The problem

Incident leads often hold a changing sequence of checks, repairs, and communications in their heads while the team needs one visible operating path. Handrail lets a person place real response steps across See it, Move it, and Say it lanes, join them into a directed rail, reposition them, undo edits, and copy a bounded URL snapshot. Boards persist in the browser; the app has no account, backend, analytics, credential input, or board-upload path. A view-only share does not overwrite the viewer's saved board, while an explicit edit adopts the imported board locally. Production deployment dpl_AbLQwsBEfqKCW68JzQQaivnPNzYG is READY from exact GitHub SHA 2e2acb3b8f73f2bc138152aab38c846fd9626cab. The concept came from secure 2026-08-13 Star Radar run 20260813T214606-0700-github-star-radar-b27b1229 (JSON SHA-256 4af52e56cef56b973e6643fb91176ed31273930b7148773b2b0e7d8be431da93): daily rank #1 cathrynlavery/diagram-design gained 4,475 stars that day and had 15,200 total stars. Handrail translates demand for deliberate diagrams into an original incident-operations workflow without copying the source repository's skill, code, templates, brand, or assets.

Architecture

Key decisions

01

Keep the operating plan local

Board content stays in the browser unless the person explicitly copies a share URL. Removing third-party font requests made the no-upload claim exact for the shipped page, and a view-only import remains transient until an edit adopts it.

02

Make persistence and sharing one tested contract

The same graph limits govern mutations, storage, and URL decoding. Test-first review fixes closed mismatched edge and payload caps, oversized identifiers, blank labels, duplicate joins, coordinate escape, sticky share fragments, and silent local-board replacement.

03

Use direct manipulation without hiding semantics

The canvas is built from labeled buttons and explicit controls rather than pointer-only drag state. The add-step dialog traps focus, restores it on close, inerts background landmarks, and reduced-motion and JavaScript-disabled paths remain usable and honest.

04

Bind production evidence to the pushed source

The private default branch advanced to 2e2acb3b8f73f2bc138152aab38c846fd9626cab, and the connected Vercel project produced READY deployment dpl_AbLQwsBEfqKCW68JzQQaivnPNzYG from that exact SHA before this case study was drafted.

Metrics

12
unit contracts passing
8
browser paths passing
0
high-severity dependency vulnerabilities
4475
stars gained that day by the upstream source