Create a new page on the octxio site, SitWithTheDeath, at /work/digital-arson-memorial. It is an OPTIONAL companion to the Digital Arson installation: a public wall that remembers files that have been burned, without ever keeping the files themselves.

Use a Base44 entity called BurnedFile with these fields: display_name (string, the file name only, no path), kind (string: "image" or "video"), burned_at (datetime), run_seconds (number, how long the file lived in that run), and note (string, optional, max 120 chars, a line the viewer can leave). No image data, no file contents, no upload: only these fields. If anyone tries to send image bytes, reject it.

The page has two parts, same visual language as the other case studies (lowercase, no em dashes, the Chapter / Line / Mono components, the warm editorial look):

1. the wall. line: "what the fire left." under it, the list of BurnedFile records newest first, each row as quiet mono text: the display_name struck through, then "gone · lived 1:48 · oct 5", then the note in grey if there is one. it should read like a register of the dead, not a gallery. paginate or lazy load; show a running count at the top: "1,204 files, none of them still here."

2. leave a trace. a small form at the bottom: a name field, a kind toggle (image/video), an optional one line note, and a "mark it gone" button that creates a BurnedFile record with burned_at = now. make clear in one line of copy that nothing is uploaded, only the fact of the loss. after submitting, the new row appears at the top of the wall.

tone: this is a memorial, not analytics. no charts, no totals beyond the count, no download. the point is to sit with the death of the files, so keep it still and text-first. add a link back to /work/digital-arson-installation that says "burn your own →", and on the installation page's close slide add a link "sit with the death →" to /work/digital-arson-memorial.

optional, only if easy: on the installation itself, when a run ends, offer a single button "add these to the memorial" that posts one BurnedFile row per file that burned (name, kind, run length). it must be opt in, one tap, and never automatic.
