# Facet

Facet (originally called Task List) is a task list that also records progress over time. See `PLAN.md` for the design decisions and `info.md` for the short write-up shown on the site at `/facet/info`.

## About

Facet is a planner that remembers. You keep batches of categorized tasks with a start and an end time, and every change is recorded as a small snapshot, so later you can see when work really happened. On top of that sit seven progress charts, a finish-date forecast, a Shape view where each category is a corner of a rotating shape (turn it to choose what to work on next) and a Shape Progress time-lapse where that shape grows and changes like an evolving organism as you add, finish and drop categories.

### Features at a glance

- Batches with start and end times in a chosen time zone, colours, and plain-text import and export (`# Category`, `[] task`, `[x]`, `[3/10]`, `[~]`, `- [] subtask`), with markdown converting live as you type.
- Drag-and-drop or Alt+↑/↓ reordering of tasks (with sub-tasks) and whole categories.
- Automatic and manual snapshots, editable history, and backup and restore.
- Seven progress charts with a time zoom (30 minutes to the whole batch, plus Start → now), including build-up views, and a forecast that accounts for tasks being added or removed.
- Shape view: rotate the shape, isolate a category, four geometry modes, effects, wide layout and an editor panel.
- Shape Progress: a looping or stop-at-the-end time-lapse at four speeds, with a scrubber, trail and effects.
- Light, dark or match-device theme, a shortcuts panel and an info panel.

See `LEARNINGS.md` for the bugs, fixes and design lessons, and `ANIMATION-PLAN.md` for the explainer and logo animations (watch them at `/facet/showcase/`).

## What it is

One self-contained `index.html` (vanilla JavaScript, inline SVG charts, no libraries, no build step) served at `/facet`. All data lives in this browser's `localStorage` under the key `tbx.facet.v1`.

## Using it

- Start on **Overview**: create a batch (a name, a start time, an end time, and optionally a colour), import one from text, or add the sample batch to look around.
- **Tasks** shows the open batch. Click a checkbox to toggle done, type to edit, and use the small buttons on the right of a row for the menu and delete.
- **Progress** charts the open batch between its start and end, and lists its snapshots. A Zoom menu narrows the time axis: Full batch, Start → now (from the batch start to now), or the last 30 minutes, 1, 2, 5, 10 or 20 hours, or 1, 2, 3, 5, 7, 10, 14 or 30 days. Every one of these keeps about 4% of the chart width free to the right of "now" (one constant, `CHART_ROOM`), even when the batch is about to end or has ended, so the "now" arrow, the latest point and the dashed forecast line start inside the chart and can be compared with the grey pace line. The pie chart has no time axis.
- **Shape** is an experimental way to pick what to work on: your categories as the corners of a shape that you rotate (see below).
- **Shape Progress** replays the shape growing from the first snapshot to now, on a loop (see below).
- The header also has the current-focus icon (see below), an ℹ️ button for storage, snapshot count, last backup and time zone, and a ⌨️ button for the typing tips and shortcuts. Both panels open and close with their buttons and remember their state. The ℹ️ button turns amber when a backup is overdue, so a warning never hides inside a closed panel.
- **Settings** has the time zone, snapshot behaviour, the Match device / Dark / Light theme toggle (saved in this browser and applied before the page first paints), import and export, and the storage breakdown.
- The batch chips under the header switch the open batch. Only active batches get automatic snapshots and count toward the overall total (an inactive batch is shown dimmed on the Overview).

### Inbox (the general task list)

The Inbox tab, second in the header, is a list for tasks that are not in any batch yet. Type a task and press Enter, or paste several lines to add one task each. Every task keeps the time it was entered (shown beside it) and can be ticked off (ticked ones hide behind "Show N completed"), edited in place or deleted (with Undo). **Send to…** moves a task into the end of a category of any batch, and Undo puts it back. The list is saved with everything else, is included in the full backup (restore can replace or merge it), has a row in the storage table, and has its own export and import in Settings → Import & export (`.md` as checkbox lines, `.csv` with the entered and done times, and import of a text file with one task per line). It is deliberately not part of snapshots, charts or the forecast. The bigger idea it is the first step toward, Facet as the place every task is collected and then pulled into weekly batches, is in `PLAN.md`.

### Keys in the task list

- Enter adds a row below. Backspace on an empty row deletes it (a category that still has tasks is kept).
- Tab and Shift+Tab indent and outdent a task (up to three levels, and no deeper than one more than the task above).
- Up and Down move between rows. Ctrl+Enter (or Cmd+Enter) toggles done.
- **Reordering.** Drag the ⠿ handle at the left of any row, or press Alt+Up and Alt+Down. A task moves together with its sub-tasks, and a category moves as a whole (its header and every task under it). A blue line shows where it will land, the page scrolls when you drag near the top or bottom edge, and Escape cancels a drag. A task can be dropped into any category, but never between another task and that task's sub-tasks, and it is re-indented to fit where it lands (a sub-task dropped at the top of a category becomes a normal task). With the handle focused, the up and down arrow keys move the row too. Alt+Up and Alt+Down on a task at the end of a category carry it into the next one, and with a category isolated they will not push a task out of sight. A "Moved. Undo" toast appears (one toast for a burst of moves, whose Undo goes back to before the first), and every move is recorded as a structure change.
- Type like a text file and the row changes shape as you go. `# ` at the start of a row makes it a category, `[] ` makes it a task, `- [] ` makes it a subtask, and `[x] `, `[3/10] ` and `[~] ` set a status. This works from either direction (a task becomes a category, a category becomes a task) and the caret stays in the field, so `# Errands`, Enter, `[x] buy milk`, Enter, `- [] oat milk` builds a whole section without touching the mouse. A line with no marker stays a plain task, and a `- ` prefix needs the bracket to count as a subtask.
- Backspace at the very start of a field: on an empty row it deletes the row, on a category it turns it back into a task (keeping its text), and on an indented subtask it outdents. An empty category that still has tasks becomes an empty task first, so a second Backspace is needed to delete it. Deleting an empty row never shows an Undo toast, deleting anything with content does.
- Pasting several lines in the text format splits them into rows.

### Text format

```
---
batch: Client work
color: #4fa3ff
start: 2026-10-19 10:00 America/New_York
end: 2026-10-23 22:00 America/New_York
colors: Income=#f2647c; Messages=#4fa3ff
---

# Income
[] not done
[x] done
[3/10] fraction (also [/10] and [0/10] for zero of ten)
[~] partial, counts as 50%
- [] subtask
[] original plan task {core}
[] added later {added}
```

The front matter is optional on import. `[ ]` and `[]` are the same, and a bare line imports as a task that is not done. Start and end may carry a time zone name (`America/New_York`) or an abbreviation (`EST`, `EDT`, `PT`...), otherwise your chosen zone is used. A text file with several front-matter blocks imports as several batches. A trailing `{core}` or `{added}` (any case) sets a task's plan mark; it is written back on export but kept out of snapshots.

### Counting

Every checkbox line, subtasks included, is one unit with a value from 0 to 1. Plain tasks are 0 or 1, a fraction is `n/d`, and `[~]` is 0.5. A parent task does not take its value from its subtasks. Done means value 1, partial means above 0 and below 1, to do means 0.

### Snapshots

A snapshot stores the whole batch's task state plus its name, start and end. Identical states are stored once, so frequent "nothing changed" snapshots cost almost nothing.

- Taken automatically about 15 seconds after the page opens, 1.5 seconds after you stop changing statuses or structure, and on a periodic timer (a "Save snapshot?" prompt by default, every 60 minutes). All of this is adjustable in Settings.
- **What triggers one, and what does not.** A snapshot is taken 1.5 seconds after you tick or untick a task, change a fraction or partial status, add, delete, move or indent a task, or add, delete or move a category. It is not taken for typing a task's name, collapsing a category, plan marks, theme or setting changes, or Inbox changes, and it is skipped when nothing changed since the last one.
- **Closing the tab before the snapshot.** Your list is saved the moment you change it, so nothing is lost. The only thing the snapshot adds is *when* the change is recorded, so a change is stamped with its time in the saved data as well. If you hide or close the page inside the 1.5 second wait, the snapshot is taken right then. If the page dies without a chance to do that (a crash, a phone freezing the tab), the next time you open Facet it records the change as a "recovered after closing" snapshot at the moment you made it, not at the moment you came back. A marker that is older than the last snapshot, in the future, outside the batch's dates or for a list that has not actually changed is ignored.
- Automatic snapshots only happen while the batch is between its start and end. **Snapshot now** always works. If you change a batch after it has ended, a toast offers to snapshot anyway.
- On the Progress tab you can edit any snapshot (change statuses and its time), delete it, or add one at a past time. Editing offers to carry the change forward to later snapshots and the current list, stopping for each task at the first later snapshot where its value already differs.

### Charts

Total progress (lines per category plus a bold total, with an optional pace line), Build-up (area) and Build-up (bars) (see below), Tasks completed (stacked bars of what was completed since the previous snapshot, with a small tick where nothing changed), Combined, Grid (each snapshot's state held until the next one, brightness shows completion), and Pie (with a slider to pick the snapshot). The legend toggles categories on and off, and isolating a category on the Tasks tab narrows the charts to it. Hover a chart for the numbers.

### Forecast

The Progress tab opens with a forecast card: "At this rate, all tasks will be completed on *date and time* — in *time until*", with the pace, how many tasks are left, and whether that is before or after the batch's end.

- **How the date is worked out.** The forecast looks at how fast the tasks left (total minus done, where a `[3/10]` counts as 0.3 and a `[~]` as half) have been shrinking over a basis you choose in the card: the whole batch since the first snapshot (the default), or the last hour, 5 hours, day, 3 days or 7 days. The date is the tasks left right now divided by that net burn rate, so it moves as you tick things off, add tasks or remove them, and "in 1d 5h" counts down on its own every 30 seconds while the page is open.
- **New tasks are factored in.** If you are completing 3 tasks a day but adding 2 a day, the card says so ("Completing 3 tasks/day, adding 2 tasks/day → net 1 task/day") and the date reflects the net 1 a day, not the 3. It also shows when you would finish *if you stopped adding tasks*. Removing unfinished tasks speeds the date up, deleting finished tasks changes nothing, and if work arrives as fast as you finish it, the card says the list never empties. The "count tasks I add/remove" checkbox switches this off for a completion-only forecast.
- **Task add buffer.** Early in a batch you are still writing the plan, and every task you add then looks like new work, so the card would say tasks are arriving faster than you finish them for a day or two. Tasks added within the buffer after the batch's start (default 1 hour) are treated as the plan, not as added work, so they do not feed the "adding N tasks/hour" rate. Work you finish during the buffer still counts toward your pace. Set the default in Settings → Forecast, and override it per batch in Edit batch (leave the batch field blank to use the default, enter 0 to turn it off for that batch). Use the time you actually finished planning, for example a batch that starts at 4 pm whose tasks were entered by 11 pm wants 7. The forecast card says when a buffer is in effect, until what time, and has a Change link.
- **Plan marks (core / added later).** Instead of, or as well as, the time-based buffer, you can mark individual tasks. Every task row has a small box at its far right: click it to cycle **soft green = core plan** (part of the original plan, so it is never counted as new work, even if you typed it in late), **soft red = added later** (always counted as new work, even inside the buffer), and back to **unmarked** (follows the add buffer). The box on a category header shows the marks of all its tasks (half green, half red when mixed) and sets them all: first click all core, then all added later, then clear. Alt+P cycles the mark on the row you are typing in. A mark describes the list as it is now, so it applies to the whole history (mark your first 20 tasks core at any time and the forecast is recalculated as if they had been there from the start); it does not take a snapshot. Tasks are matched to older snapshots by category and text, so renaming a marked task makes the earlier history slightly off. The forecast card says how many tasks are marked.
- **One-off re-plans are not extrapolated.** A single big jump in the task count between two snapshots (pasting or importing a list, deleting a whole category; at least 4 tasks and 20% of the list) is treated as a one-time change: the work is still counted in the tasks left, but it is not projected forward as an ongoing stream, and the card says so. Two or more such jumps of the same kind in the window are treated as a habit and do count as a trend.
- **It says so rather than inventing a date** when there is no history yet (under about 10 minutes), when nothing was completed in the chosen window, when the batch has not started, and when everything is already done (it then shows when it finished).
- **Early or late at a glance.** The dashed forecast line and its end dot are drawn in soft green when the predicted finish is before the batch ends and soft red when it is after (a batch with no end date keeps the neutral colour). The same colours mark the before/after line on the forecast card.
- **On the charts.** The Total progress and both Build-up charts draw the forecast as a dashed line from now to the predicted finish. When new tasks keep arriving, the Build-up charts also draw the rising target (a faint dotted line), so you can see the goalposts moving. The "forecast line" checkbox hides it, and the line follows whichever categories the chart is showing.
- **How accurate is it?** It was checked against simulated worlds with a known answer. With steady work it is exact, and it stays exact when tasks are added or removed at a steady pace, when finished tasks are deleted, when some tasks were already done at the start, and after one-off pastes or removals (steady work: 0% error; adding 1 a day while completing 3: 0%, where ignoring new tasks was 33% too optimistic; dropping unfinished tasks: 0%, where ignoring that was 100% too pessimistic). A worker who stops on weekends was within 1% to 13%, and a weekly dump of five new tasks stayed within about 16% at every checkpoint (ignoring new tasks was about 50% too optimistic). With random work it is honest but noisy: over 80 random trials the typical (median) error was about 17% with new tasks counted versus about 33% without, and by day 30 it matched the best any forecaster could do even knowing the true rates. Limits: it extrapolates the past, so a worker who keeps speeding up will be beaten by the shorter bases (the last day or the last 3 days), and early on it is rougher because there is little history.

### Build-up views

Total progress and the other percent views make it hard to see work piling up, so these two plot completed tasks instead of percent. Each category is a colour band stacked on the others, and the height of a band is how many of that category's tasks are done at that moment (a `[3/10]` task counts as 0.3 of a task, a `[~]` as half). The axis is in tasks and tops out at the total number of tasks being shown, with a dashed line at that ceiling, so the stack visibly climbs toward it. Build-up (area) joins the snapshots into shaded bands, and Build-up (bars) draws a stack of coloured segments at each snapshot. The pace line, the time zoom, the category toggles and the hover numbers (tasks done of the total, and each category as done / total) all work on them. Hiding a category removes its band and lowers the ceiling to the tasks that remain.

**Build-up (area, total)** is the same idea turned into a breakdown. The chart is always completely filled, and the axis is 0–100% of all tasks. Each category's band is its share of all tasks at that moment (a category that grows pushes the others down), and inside each band the solid colour at the bottom is the part that is done while the faded colour above it is still to do. So one picture shows how much of the work is which category and how much of each category is finished. The time zoom, category toggles and hover work on it (hover lists each category's share and done / total); the pace line and forecast line are not drawn because they are in tasks, not share. Hiding a category re-balances the rest to fill 100% again.

**Build-up (scope)** splits finished work by whether it was in scope. The green band is completed work that was in scope, the grey band on top is completed work that was out of scope, and the axis tops out at the total number of tasks (a faint dotted line shows how that total moved as tasks were added or dropped). A task is in scope if it was part of the original plan: marked core with the box on its row, or, if unmarked, already there when the history began or entered within the add buffer after the batch start (the same rule the forecast uses). A task marked "added later", or unmarked and added after the buffer, is out of scope. Marks describe the list as it is now and apply to the whole history; tasks are followed across snapshots by category and text, and a task that is no longer in the list counts as unmarked. The pace line, the forecast line (soft green or red), the time zoom, the category toggles and the hover numbers (done, in scope done of total, out of scope done of total) all work on it.

### Shape view

An experiment in picking what to work on, built for moving between projects when one feels like too much. It is a display over the same batch, and it never changes what the Tasks and Progress tabs show.

- **The shape.** Each category is a corner of a regular shape: a dot for one category, a line for two, then a triangle, square and so on up to eight corners. Over eight, the gear panel lets you choose which eight to show. Each corner shows its name, done/total, a progress ring, and its tasks radiating outward, with the top of your list nearest the corner.
- **Rotation.** The whole figure is one rigid body. The selected category sits at the top with flat, readable text, and every other category's text is tilted by wherever its corner currently is, so only the selected one is easy to read. The right arrow rotates counter-clockwise (so it brings the next category in your list up to the top) and the left arrow rotates clockwise. The buttons at the sides of the stage are plain → and ← arrows (there are no other rotate buttons). Clicking a corner (or its chip, or a number key 1 to 8) spins it to the top the short way, and you can drag the shape to spin it and let go to snap to the nearest corner.
- **Zoom.** Fit all shows the whole shape and all text. Focus shows the whole shape with the current category large, and the others may fall out of frame. Open zooms into the selected category so every task is large and clickable (the mouse wheel scrolls a long list), and clicking a task on the selected corner ticks it off. Up and down arrows move between the levels, Enter opens, and Escape backs out.
- **Editor panel.** Beside the shape (below it on a phone) is the normal row editor for the selected category, so typing markdown, ticking, indenting and adding categories all work, and the shape updates as you go. Ticking things creates snapshots exactly as on the Tasks tab.
- **Controls on the shape.** The categories are a vertical list down the top left corner of the stage (with a **+ Category** button at the end). The top right corner holds the zoom control (Fit all, Focus, Open), a **Show all / Hide done** control with the current choice highlighted (finished tasks on the rays; partly done tasks stay; the same setting as "Hide finished tasks on the rays" in the gear panel), **☰ Tasks** (shows or hides the task list beside the shape, the same setting as "Show the editor panel"), the ⚙ settings button and the ⛶ full screen button. The Surprise me button was removed. In the gear panel, **Move finished tasks to the end of each ray** keeps pending tasks nearest the shape and pushes finished ones farther out (hiding finished tasks wins if both are on).
- **Editing on the shape.** Everything the task list can do for the selected category can be done on the shape itself, full screen included, so the list does not have to be open. Click a task's words to edit them in a box that sits over the task; click its circle to tick it. Enter adds the next task below and keeps typing (Enter on an empty line finishes), Tab makes a subtask and Shift+Tab a main task again, Backspace at the start of a subtask outdents it, Backspace on an empty task deletes it and moves to the one before (deleting a task with text offers Undo), Ctrl+Enter ticks it, ↑ and ↓ move between tasks (↑ is the next task along the ray, because the list climbs away from the corner; ↓ past the first task reaches the category name), and Escape stops. A dim **add task** circle at the end of the selected ray (or the N key) adds a task at the end of the category, and an empty placeholder task disappears when you leave it. Click the category name to rename it. **+ Category** adds one named New category with its name box open, and Enter there moves on to its first task. A task that is not on the visible part of the ray opens the list zoom and scrolls it into view. Text typed as `[x] words` sets the status as it does on the Tasks tab. Fractions, partial marks and plan marks are still set from the task list.
- **Fits the window.** The stage is sized to the height of the window (the footer is hidden on this tab), so the whole shape is visible without scrolling; it follows window resizes. On a phone the controls wrap over the shape and the page may scroll.
- **Full screen.** The ⛶ button (or the F key) fills the screen with the shape, the controls and, if shown, the task list; ⛶ or F or Escape leaves. Browsers that cannot full-screen a page element (iPhone Safari) get a window-filling layout instead. Toggling the task list while in full screen keeps full screen on.
- **Full width.** In the gear panel, "Use the full screen width" stretches the Shape view across the whole window so a big screen is used properly, and the editor panel, if shown, sits inside that wider area on the right. Hiding the panel gives the shape everything. It never causes sideways scrolling on a narrow screen, and the setting is remembered.
- **Remembered.** Which category is selected, and the zoom level, are saved per batch, so the shape is as you left it. The header shows a small copy of the shape in its current orientation with the selected category's name in its colour on every page (click it to return to the Shape view).
- **Geometry that carries data.** In the gear panel, Regular is a plain shape, Radar draws an inner shape whose corners reach out by percent complete, Weighted moves each corner outward by how much work it has left (a bigger corner is more overwhelming), and Both does both at once, so the radar shape nests inside the weighted outline (each radar corner is that corner's own reach times its percent complete).
- **Effects, all in the gear panel and all switchable.** A bouncy spring, smooth glide or instant rotation, neon glowing edges in the category colours, a colour blend across the shape pulled toward each corner (brighter as it completes), a particle burst when you finish a task (a bigger one when a whole category reaches 100%), a starfield and nebula that counter-rotate, an option to keep every label flat, sound, haptics and phone tilt parallax (the last three are off by default). If your device asks for reduced motion, spinning is instant and the motion effects stay off.
- **Not built yet.** The same idea one level up (batches as a galaxy you zoom into) is recorded in `PLAN.md`.

### Shape Progress

A looping time-lapse of how the shape grew. It runs from the first snapshot to now, so a three-day batch can be watched in 30 seconds or three minutes. Pick the speed with the buttons: Slow takes 3 minutes for the whole start-to-now, Medium 90 seconds, Quick 60 seconds and Fast 30 seconds. With the **loop** checkbox on (the default) it holds for a moment at the end and starts again; with it off it stops on the last frame, and pressing Play at the end starts over from the beginning. The choice is remembered.

- **What the picture means.** Each category is a corner. The glowing outline is how many tasks that category has, so it grows outward as you add tasks, and the bright inner shape is how many are done. One scale is shared by every category and every moment, so corners are comparable, and the faint rings mark 25, 50, 75 and 100 percent of the biggest category ever. A ring around each corner shows its percent complete, and the big faint number in the middle is the overall percent.
- **Evolving organism.** It begins as whatever shape the first snapshot had, and categories you added or removed part-way through change the shape. Each category has a presence from 0 to 1 that eases over at least 3% of the timeline, corners share the circle in proportion to presence, a new corner buds out of the edge between its neighbours (or out of its only neighbour, like a cell dividing) and slides to its place, and a removed one folds back in. One category is a disc, two a capsule and three or more a polygon, cross-fading between them. The first frame is the first snapshot and the last frame is exactly the live list. The heading line says how many categories are present at that moment.
- **Smooth.** Between two snapshots the state is interpolated, so growth is continuous rather than jumping.
- **Controls.** Play and pause, a scrubber you can drag to any moment (the time and totals shown are for that moment), a trail checkbox for faint outlines of earlier moments, an effects checkbox (glow, colour blend, stars and a particle burst at a corner when playback passes a task being completed), and the same ⤢ Wide toggle as the Shape view. Space plays or pauses, ← → scrub 2%, Home and End jump to the start and to now.
- **Export video.** The ⬇ Export video button renders the time-lapse to a video file in the browser, with no upload and no outside tools. Pick the shape (wide 16:9, square or vertical 9:16), the size (Small 360p, Medium 720p, Large 1080p), the frame rate (24, 30 or 60) and the length (2 to 300 seconds, with presets of 15 s, 30 s, 1, 1.5 and 3 minutes; it is how long the whole start-to-now takes in the video). It draws each frame with the same code as the live view, using the trail and effects checkboxes as they are set, adds the batch name, the time, the totals and a thin timeline, holds on the last frame for a moment and downloads the file, with a preview and a "Download again" link. A progress line shows the frame, how many times faster than real time it is going, and the time left; Cancel render, or closing the dialog, stops it. The video is made faster than it plays: H.264 in an .mp4 where the browser can encode it, otherwise VP9 in a .webm; a browser without video encoding falls back to recording the canvas in real time (so a 30 second video takes 30 seconds and the tab has to stay in front). It needs at least two snapshots. Exports use a fixed random seed, so the same history gives the same video.
- **Edge cases.** With no snapshots yet it shows the current state and says the time-lapse needs at least two. A category that was removed keeps a palette colour for its name, because snapshots store task text and not colours. With reduced motion turned on it starts paused and you press Play.

### Side panel (wide screens)

On screens wider than about 1180 px, Overview, Inbox, Tasks and Progress get a column on the right with two small things, each switched on or off in Settings → Side panel (both on by default). It is not shown on Shape, Shape Progress or Settings, on narrower windows or on a phone.

- **The current shape**, with no text: the outline in the category colours, the inner shape showing how complete each category is, a marker with a completion ring per category, in the same orientation as the Shape view (the selected category at the top, and the Weighted geometry setting is followed). Click it to open the Shape view.
- **The forecast**: "Tasks done *date and time*", how long before or after the batch ends (green or red), the tasks left, and a small chart that is the Progress tab's own chart scaled down, using whichever view and zoom are chosen there (for example Build-up (area) with Start → now) and the forecast basis from the forecast card. The pie has no time axis, so it shows the line chart. Click it to open Progress.

It updates as you tick tasks and refreshes every half minute.

### Logo and icons

The mark is the "breathing facet" from the showcase, drawn with a transparent background so it reads on light and dark pages. `favicon.svg` (heavier strokes, for tiny sizes), `facet-mark.svg` (the detailed mark) and `facet-mark-animated.svg` (the same mark breathing, 9 KB, loops every 4 seconds) live in this folder, with `favicon-32.png`, `favicon-192.png` and an opaque `apple-touch-icon.png`. The app header uses the same mark inline, and the tab icon, the info page and the showcase pages all use `favicon.svg`. The Toolbox card thumbnail is an animated SVG (13 KB, `shell/images/thumbs/facet.svg`) with a still version for people who ask for reduced motion (`facet.static.svg`), and there is a `facet.gif` (270 KB) for places that cannot show an SVG, such as email or chat previews. Everything is generated by `node scripts/make-facet-assets.mjs --raster`, so a change to the mark is one edit in that script.

### Backup

Settings → Import & export has: everything (JSON, the one that counts as a backup and resets the "last backup" reminder), tasks (text), progress (JSON and CSV) and settings (JSON). Restoring a backup can replace or merge. The ℹ️ panel in the header shows storage used and the time of the last backup, and the footer is just the copyright line.

## Files

- `index.html` — the whole app, including the Shape view.
- `meta.json` — toolbox metadata (status `beta`, storage `localstorage`).
- `info.md` — the write-up at `/facet/info`.
- `PLAN.md` — design decisions and what is deliberately left out.
- `LEARNINGS.md` — bugs found and fixed, design lessons, testing approach.
- `ANIMATION-PLAN.md` — the name decision, what the two v1 animations do, ideas and hand-off notes for v2.
- `showcase/` — the trailer and logo loop (`animation-v1`, `logo-v1`) as pages and as MP4s in wide, vertical and square, with `showcase.json` listing them and flagging the primary. Seen at `/facet/showcase/`; the Toolbox card has a Trailer button and the info page links to it. See the Showcase section of the repo `README.md`.
- `shell/images/thumbs/facet.svg` (in the toolbox shell, not this folder) — the thumbnail: a triangle with a red top point, green bottom-right point and blue bottom-left point.

## Development notes

- Preview with `npm run dev` from the repo root and open `/facet/`.
- The page exposes `window.__TL` (state, parser, snapshot and time helpers) for console debugging and for browser tests. Nothing in the UI depends on it.
- Time zone work all goes through `Intl` (`zonedToMs`, `partsIn`); do not add fixed UTC offsets.
- Removing a focused input fires `change` during the redraw, so the row editor and `render()` both carry re-entrancy guards. Keep them if you restructure either.

## Known limits and ideas

- Nothing runs while the page is closed, so there are no background snapshots or reminders.
- `localStorage` is about 5 MB. The storage meter shows how close it is, and moving snapshots to IndexedDB is the escape hatch.
- No per-task deadlines, no syncing between devices. Drag-to-reorder scrolls the page, not an inner scroll area, so inside the snapshot editor use Alt+Up and Alt+Down for long lists.
- Categories that share a name are merged in the charts, and renaming a category starts a new line on the charts from that point.
- The Shape view treats every header as a category, including empty ones, plus a "No category" corner only when tasks sit above the first header.
- A category's colour is the round button on its header. It opens the same twelve presets as the batch colour picker plus a custom colour.
