This is an offline single-HTML app. No data goes to or from the internet after this page loads. Your log entries live in your browser's sessionStorage — on this device, in this browser, and nowhere else.
Your data is YOUR responsibility.
Clearing browser data, switching browsers, using private/incognito mode, or losing this device erases everything. Use the Export (⤒) button in the topbar to save a .pumapack backup somewhere safe — ideally after every session.
Press ? any time for help and keyboard shortcuts. A few demo entries are pre-loaded so you can see the shape.
An append-only timestamped log — the "captain's log" of the PumaWorx family. Each workspace tab is its own dataset with its own chip palette and its own display timezone. Quick-capture a one-line headline, then optionally add a longer description in the detail popup. Works offline as a single HTML file; installable as a PWA.
¶ badge when a description is attached); the description is optional, rendered with the §26 live-preview markdown editor in the detail popup.trace · debug · info · warn · error · fatalquestion · hypothesis · procedure · observation · measurement · anomaly · result · reference. Separates prediction (Hypothesis) from captured data (Measurement) from outcome (Result); Anomaly flags unexpected events without invoking severity.information · observation · evidence/artifact · hypothesis · assessment · decision · action · communication. Separates analyst observations from formally preserved evidence, calls out the working assessment of scope/severity as its own phase, and gives outward-facing communication its own chip.#word — subject tag, filterable below@word — stakeholder tag, separate filter row!chip — one-shot chip override for this entry only#/@; palette order for !).
chip:warn — chip id match#prod or tag:prod — tag match@alice or stakeholder:alice — stakeholder matchbefore:2h, before:2026-05-21 — temporal upper bound (relative s/m/h/d/w or ISO date)after:DATE-OR-DURATION — temporal lower boundhas:description / has:tags / has:stakeholders — presence checksCreated + last Edited timestamps. Edits to the timestamp colorize: teal ↶ for backdated entries (ts < created_at), gold for forward-shifted ones..pumapack — cross-app envelope (⌘S).csv — id, ISO timestamp, chip, tags, stakeholders, title, description; reimportable.md — markdown document with each entry's description as a section.rtf — Word-friendly file; data columns monospace, titles proportional.pumapack or .csv and always creates a new workspace named after the source file — never silently merges.
sessionStorage under the pumalogger.* prefix. Nothing leaves your machine.See the Keyboard tab for every shortcut.
PumaLogger stores everything in your browser's sessionStorage under the pumalogger.* prefix — on this device, in this browser, and nowhere else. There is no server, no account, and no entry ever leaves your machine.
sessionStorage is tied to this specific browser on this specific device.
Use Export in the topbar (or ⌘S) to write a .pumapack file containing every workspace and its prefs — the PumaWorx cross-app envelope. Re-importable here and structured so other PumaWorx apps can consume data.entries[].
Each tab's right-click menu also exports just that workspace, in your choice of format: .pumapack, .csv, .md, or .rtf. Copy timeline as Markdown / RTF writes the same content to the clipboard for paste into Word, Pages, Notes, or any markdown editor.
⌘O (or drag-and-drop) opens the file picker for import. Imports always create a new workspace named after the source file — they never silently merge into your active dataset, so reimporting a backup leaves your live workspaces untouched.
⚠ Permanent. This erases every PumaLogger entry, tag, and preference stored in this browser. Export a backup first — there is no undo.
Still sure? Type DELETE EVERYTHING to finalize.
.pumapack.pumapack fileOn Windows/Linux, use Ctrl wherever ⌘ is shown.
PumaLogger was designed as part of PumaWorx to assist in recreating timelines sourced from multiple local timezones. It is built on ancient theories of bound-book incident response.
PumaWorx is a suite of offline, single-HTML productivity apps that run entirely in your local browser. The entire suite is a personal, open source vibecoding project.
Every workspace owns its own chip palette — the set of chips behind the composer pip. Rename or recolor any chip, add new ones, reorder them, change which chip is the default. Pick a starting preset when you create a new workspace (the + button in the tab strip); after that, edit freely. Each workspace is independent — editing one tab's chips never touches another's.
One demo tab ships on first run:
A second, CIRT-flavored example log lives at demo/north-pole-cirt.json alongside the app — drag it onto the window or use Import (⌘O) to load. It runs through a deliberately absurd North-Pole incident-response narrative on the Investigation preset: observation → hypothesis → evidence → assessment → decision → action → communication, with executive, legal, and PR engagement layered on top.
A sandboxed click-around version of the app — same UI, example data pre-loaded, persistence stripped — is also deployed at pumalogger.greykit.com/demo.html.
Click the button below to add a fresh Welcome tab at any time. Existing tabs are not touched; the new one is suffixed if there's a name conflict.