Side-effect log

In your browser's localStorage under key vialfile-sideeffects-v1. Nothing is sent to a server in v1. When we add sync (opt-in), your existing entries will migrate over cleanly.

1 = noticed but not limiting. 2 = mild, resolves on its own. 3 = moderate, prompts you to check the protocol. 4 = significant, considering dose reduction. 5 = severe, halting dose and re-evaluating. The scale is your own — consistency across entries matters more than absolute calibration.

Peptide-induced effects typically take 1–3 weeks to stabilize at a dose; shorter-window views show noise that flattens out by week two. The grid hides daily chop on purpose.

Log what you'd want to remember in four weeks. Over-logging dilutes the pattern — a stack that has three severity-1 headaches and one severity-4 water-retention shift reads very differently from the grid if you log all of them versus just the real shift.

Export + import are coming in the next release. For now you can inspect the raw JSON in browser devtools (localStorage.getItem('vialfile-sideeffects-v1')) and copy it elsewhere as a backup.

Two quick context lines for the peptide you just selected: From library lists commonly-reported effects for the peptide (sourced from r/Peptides and PubMed references — up to four, null when not yet catalogued), and Your history rolls up your own logged entries for that peptide into count, mean severity, and last date. Library hints are informational — they're not a list of effects you should expect or panic about; they're a naming prompt so entries cluster cleanly in the pattern grid. The same panel renders on the calculator so you see what to expect and what you've experienced side-by-side before you dose.

When a peptide in your active stack has logged ≥ 2 severity-3+ side effects in the last 14 days and its bloodwork protocol is already overdue, vialfile surfaces a paired alert at the top of the page. Both signals together — a high-severity side-effect cluster and a missed draw window — are a stronger prompt to check in with your provider than either one alone. The banner clears automatically once bloodwork is logged and the status updates to on-track, or if the side-effect pattern drops below the threshold.

Each logged side-effect entry now shows how long after your most-recent injection of the same peptide the effect was logged — e.g. "2h after injection". Time is measured from the injection timestamp in your injection log that immediately preceded the effect, at or before its timestamp. Format scales automatically: under a minute shows "< 1m", under an hour shows minutes, under a day shows hours, and multi-day lags show days (each rounded to the nearest unit). The line is hidden when no prior injection of that peptide exists in your log — brand-new users or entries logged before the injection tracker was used will see nothing. This is purely a read from the injection log — no new data is stored, and the line updates automatically as you add or delete log entries on the log page. Use it to distinguish injection-day reactions (< 1h) from delayed responses (hours) and lagged systemic effects (days) — a key temporal pattern for identifying which peptide is responsible.