vialfile

Current stack

Define what you're running today — 2 to 4 peptides with start dates and doses. Mark one stack active and the calculator, injection log, and bloodwork pages will auto-default from it. The four log pages keep their own data; the stack is just a metadata layer pointing at "this is what's current."

Peptides in this stack (2–4)

No stacks yet. Define your first stack above and mark it active.

What "active" does

  1. Calculator — when you select a peptide that's in your active stack, a "in your current stack — started date, nd ago" line appears above the source links. Confirms you're still on the protocol you set.
  2. Injection log — the peptide dropdown defaults to your active stack's first item (instead of the empty placeholder). Saves a click on every entry.
  3. Bloodwork cadence — the "logged injections without bloodwork protocols" suggestion list also includes peptides from your active stack you haven't started a protocol on yet. Catches the gap between "I'm running this" and "I have a draw schedule for it."

All three integrations are read-only. None of them write back to vialfile-stack-v1. If your active stack is malformed or empty, the three pages fall back to their existing behavior — no breakage.

Stack FAQ

Why a separate "stack" instead of just tagging entries?

Tagging makes every log entry carry stack metadata, which couples your historical log to a current concept that changes every cycle. Keeping stacks separate means the four logs stay clean (one schema each) and you can switch active stacks without rewriting history. The stack layer is auto-prunable; your logs are forever.

How many stacks can I save?

Up to five. When you save a sixth, the oldest by created-at is auto-pruned. The cap exists so the localStorage footprint stays small — typically <2 KB even at the cap. If you need more history, export from the settings page first.

What happens to the active flag when I delete the active stack?

You'll have no active stack until you mark another one. The four cross-surface integrations fall back to their pre-stack defaults — empty dropdown placeholder on the log page, no context line on the calculator, only injection-log-derived suggestions on bloodwork.

Why isn't the stack in the backup file?

The backup file is currently vialfile-backup-v1 with three sections (injections / sideeffects / bloodwork). Stack is metadata, not user data — losing your "current stack" is recoverable in 30 seconds, losing six months of injection logs is not. A future backup version may include stacks; for now, the cross-surface fallbacks make stack data low-stakes.

Where is my stack data stored?

In your browser's localStorage under key vialfile-stack-v1. Clearing site data, switching browsers, or using private mode will erase it. Same privacy model as the other four logs — nothing is sent to a server.