Chelan Hills Fire, July 4, 2026 · the story and the record

This incident is three weeks old and one member of the public died. The story spine below adds nothing to the published record. The authoritative account is the Rapid Lesson Sharing report by the Wildland Fire Lessons Learned Center; read it first. Community additions render separately as credited testimony.

Add what you saw

What did you see, hear, or do, and when, and where. This page never asks for drama, blame, or names. Everything lands as a credited file of its own in the incident's public contribution box, rendered in the log below and kept separate from the factual spine.

How this works, in plain words. There are no accounts here. Identity is the credit name you claim plus a device fingerprint; capability is one shared write key embedded in this page, public by design, scoped write-only to the contribution box; lineage is the public invite chain. Everything is files.

Credit name (required). The name the log credits. Free text; the fingerprint beside it is how repeat contributions from the same device stay connected.

identity: reading…

Your testimony. Witness grammar: what you saw, heard, or did, with time and place.

When it happened (optional, distinct from when you write this). ISO style, partial precision welcome, e.g. 2026-07-04T15:30 or 2026-07-04.

Blast radius · who this assertion is meant for. Declared intent, recorded in the envelope.

public · render for everyone, now and later. contributors · intended for people in this incident's invite tree. rls-review · offered toward the authoritative record's stewards. Optional plain-words intent note.

The one honest enforcement line: the shared key can write only into contributions/ and can touch nothing else. Your declared radius is intent on the record; the directory is publicly readable today, and the page renders accordingly. Read-side enforcement of declared radii is named future access-layer work. Write nothing into this box you are unwilling to have public today.

What v1 does NOT claim. No per-person revocation: everyone spends the same shared key, so revoking it resets everyone at once. No read gating by blast radius yet: declared radii are recorded intent. No server-enforced append-only: the shared key can PUT any filename in the box, so the log is append-by-convention (timestamped filenames collide only by intent) and the moderator's owner-token audit is the backstop. No cryptographic delegation: an invite proves lineage because the public log says so, credited and append-by-convention as above. It is a provenance chain. Per-invitee derived tokens, read-side radius enforcement, and signed envelopes are the named next steps, in that order.

The assertion log · community testimony, credited

Every envelope in the box, newest first, rendered in full: credit name, fingerprint, kind, declared blast radius, lineage. Credit is claimed, and corroborated only by lineage and consistency; the tok: fingerprint beside each name is an attribution hash, never anyone's key. Assertions declared contributors or rls-review still render here with their radius shown, because the box is public and this page never pretends otherwise.

reading the box…

Invites · a public chain

Any contributor can invite someone who was there. The invite log is always public, outside all blast radii, by design: the lineage of who brought whom into the testimony is itself part of the record. An invite creates a record and a link; it never creates an account.

Who is it for (as you name them; they name themselves when they first contribute).

Why this person. Public, so write it as a public sentence.

The invite lineage

reading the invite log…

terrain pane · booting…

starting the 3-D terrain engine…
(if it cannot start here, a labeled 2-D terrain pane takes over; the record reads the same either way)