# 01 — incident contribution narratives: the ADD tab and the incidents index *Commissioned 2026-07-23 by Debbie ([design bead `c4a8e2f1`](https://redfish.acequia.io/guerin/.agents/c4a8e2f1/about.md)) inside Stephen's program. Author: John, rhetoric persona ([bead `6715f286`](../../about.md)), modes pulled from [ethos](../../skills/ethos/SKILL.md) and [logos](../../skills/logos/SKILL.md); register carried from [note 00, the citizen-first revision](00-alert-live-new-site-messaging.md) including its §7 fact resolutions. Targets: (A) the new ADD tab in the incident-viewer ([stac-workbench](https://redfish.acequia.io/guerin/apps/stac-workbench/), [authoring bead `019f8680`](https://redfish.acequia.io/guerin/.agents/019f8680-fc72-792f-a940-1251647c31c2/about.md)); (B) the incidents index page bound for [alert.live/incidents/](https://alert.live/incidents/), backed by the served collections at [simtable.acequia.io/incidents/](https://simtable.acequia.io/incidents/).* *House rules for every blockquoted **COPY** block (deployed-grade, lift verbatim): no em dashes; no "not X, but Y" construction; witness, never gore; no capability claim beyond what is built. This note's own prose uses bead-doc idiom.* *Honesty spine, binding on all copy below: (1) anonymous PUT to the incidents origin returns 302; the flow tries an authenticated deposit (`fetch` PUT, `credentials:'include'`) and on failure degrades to a downloadable deposit bundle, the file plus its envelope JSON, with hand-off instructions. Never a faked success. (2) Blast radius and invites are RECORDED in the envelope as declared intent; per-person enforcement is future acequia access-layer work, and the UI says exactly that in one quiet line. (3) Chelan Hills is a fresh entrapment; its frame is community lessons-learned support, never marketing, per the [incident bead's limitation](https://redfish.acequia.io/guerin/.agents/68d88c38-e223-4385-b8c9-f929eea309a3/about.md).* --- ## 1. The add flow's spine Four steps, one line each. These are the step labels and their single deployed line. The whole flow fits on one screen per step; nothing scrolls that decides. **Step 1 · Who's adding** (COPY): > Responder, community member, or news and media. Your role shapes the channels you can share on. **Step 2 · What you're adding** (COPY): > Photos, video, documents. Each file gets a time, a place, and your name in the record's envelope. **Step 3 · Who sees it** (COPY): > Start personal. Widen when you choose. You set the blast radius, and it widens only when you widen it. **Step 4 · Deposit** (COPY): > Your file joins the incident folder with its envelope: what it is, who added it, and who it is for. The quiet honest line, shown once on Step 3 under the radius picker, same styling as the workbench's existing honesty notes (COPY): > Today the blast radius travels with your file as your declared intent, recorded in its envelope. Per-person enforcement arrives with the access layer. Until then, treat each radius like a radio channel: say only what belongs on the widest net you picked. Rationale (logos): the spine is one causal chain per the one-spine rule: identity shapes channels, channels shape the envelope, the envelope IS the deposit. The honest line is clean-hands ethos; declared interest stated up front costs less than discovered limits later. --- ## 2. Per user type: the tight copy ### Step 1 door copy (the three chairs) > **I'm a responder on this incident.** > Assigned to it, or supporting it from your agency. > **I live here, or I saw it.** > Neighbors, travelers, anyone with eyes on it. > **I'm with a newsroom.** > Adding footage or reporting your organization holds rights to. ### 2a. Responder Tab header (COPY): > **Add to the incident record.** > What you saw on the line is part of this fire's record. Pick the channel it belongs on. Radius options, label plus one deployed line each (COPY, in this order, narrowest first): > **Personal** > Yours alone. A working copy in the incident folder that only you come back to. > **My crew** > Your crew's net. Create the group once, invite by name, use it all season. > **Operations section** > For the people working the line. Division assignments, tactics, what you saw and where. > **Plans section** > For the picture keepers. Maps, perimeters, IAP inputs, anything Situation needs current. > **Command staff** > For the IC and command staff. Use this when what you hold should change a decision. > **Serious accident investigation team** > For the SAI team only. Handled as evidence. Add it here, then stop copying it anywhere else. > **My agency contact** > Straight to a named person at your agency, for example your DNR liaison. When the right reader is one person, name the person. The blast-radius explainer, fireline-respecting grammar (COPY, one short block above the options): > Blast radius works like your radios. Personal is you alone. A group is your crew net. A section is the section's net. Command is command's. Pick the narrowest channel that still reaches everyone who needs it. Rationale (ethos): the responder reader honors doctrine they already own; the copy borrows standing from radio discipline and LCES-adjacent habit rather than inventing app vocabulary. No line promises delivery or receipt; it promises the record. ### 2b. Community member The register carries over from the citizen tab's ratified hero ("You are the first to see it," [note 00 §2 Tab 1](00-alert-live-new-site-messaging.md)). Invitation grammar throughout; people are members, never instruments. Tab header (COPY): > **You saw it first. Put it on the record.** > What you add joins this incident's shared record, with your time and place attached. You choose how far it carries. Radius options (COPY): > **Personal** > Yours alone until you say otherwise. Kept in the incident folder under your name. > **My neighborhood group** > The people on your road, your ridge, your block. Create the group, invite your neighbors, and what each of you sees becomes what all of you know. > **Share with media** > Offer it to newsrooms covering this incident. You keep your rights. They get your file with its verified time and place. > **Public** > Everyone. Your view joins the shared record of this incident, credited to you. Rationale: "what each of you sees becomes what all of you know" is the flock line from the ratified collective-intelligence section, compressed to neighborhood scale. No "help us," no "submit," no "report": the member adds to a record they belong to. ### 2c. News and media Tab header (COPY): > **Add your organization's coverage.** > Your footage, your rights, on the incident's shared record at full resolution and provenance. Options (COPY): > **Our own footage** > Footage your organization shot, for example helicopter video. You declare the rights; the record carries them verbatim with every frame. > **Public** > The default for media deposits. Your credit and license travel with the file wherever the record is opened. The rights declaration line, shown as a required check with this exact text (COPY): > We shot this footage or hold the rights to it, and we choose the terms under which this incident record may share it. Rationale: mirrors the incidents origin's standing rights policy (links and rights recorded verbatim, per the [Maria README](https://simtable.acequia.io/incidents/2019-CA-Maria-Fire/README.md)). The newsroom's stake is stated plainly; declared interest is the ethos move. --- ## 3. Group creation and invites Create button (COPY): > Create a group Name field label and hint (COPY): > **Name your group** > Name it the way you'd say it out loud. Crew 7. Sunflower Lane neighbors. KXLY air desk. Invite field label and hint (COPY): > **Invite people** > By handle or email. Each person gets a link to this incident and to the group. They add under their own name. Confirm button (COPY): > Create and invite The honest enforcement line, directly under the invite field, quiet styling (COPY): > Invitations and membership are recorded in the group and in every deposit's envelope as your declared intent. Per-person access enforcement arrives with the access layer. Rationale: one honest line, once, exactly where the promise would otherwise be implied. No lock icons, no "private group" badge, no shield imagery anywhere in this flow until enforcement exists. --- ## 4. The deposit moment ### Success (authenticated PUT landed) (COPY, `{radius}` filled from the chosen option, `{incident}` from the collection title): > **Deposited.** > Your file is in the {incident} folder with its envelope. Blast radius recorded: {radius}. > Open it in the viewer, or add another. Buttons (COPY): `Open in viewer` · `Add another` ### Honest degradation (not signed in, or the PUT came back 302) (COPY): > **You're not signed in, so this can't deposit directly.** > Nothing was lost. We packaged a deposit bundle instead: your file plus a small envelope file recording what it is, when and where, and who you meant it for. > Download the bundle and hand it to someone with write access to this incident: your section, your agency contact, or the incident's record keeper. When they deposit it, your envelope goes in with it, unchanged. Buttons (COPY): `Download deposit bundle` · `Sign in and retry` Rationale: this is the workbench's existing honesty pattern ("No write auth → an honest browser-download bundle instead," [stac-workbench README](https://redfish.acequia.io/guerin/apps/stac-workbench/README.md)) given its narrative. The degradation copy names what the bundle is, states the file survived, and gives the reader a next actor. It never says "sent," "shared," "pending," or "queued." Builder note, non-copy: attempt `fetch` PUT with `credentials:'include'` first; a 302 or network refusal routes to this screen, and no state on this screen may resemble the success screen. --- ## 5. The index page: alert.live/incidents/ ### Page purpose, two sentences (COPY, the page's standfirst under the title `Incidents`): > Every incident here is a shared record: the imagery, documents, and data that people on the line and in the community put on the map, cataloged in the open with each item's source and rights kept intact. Open any incident in the viewer to see its record, or add what you hold to the record that needs it. ### Per-incident card grammar Every card, in this order: name, when, where, one line of what the record holds, two actions. Template (COPY): > **{Incident name}** > {Month Year} · {County, State} > {What the record holds: counts and kinds, one line, from the collection itself.} > `Open in viewer` · `Add to this record` The two action labels are fixed across all cards. `Open in viewer` deep-links the collection into the incident-viewer (`?stac=`); `Add to this record` opens the ADD tab with the incident preselected. ### The Chelan Hills entry (lessons-learned support frame, the respect gate applied) (COPY): > **Chelan Hills Fire Entrapment and Escape** > July 2026 · Chelan County, Washington > An initial attack entrapment and escape on July 4, 2026, documented by the Wildland Fire Lessons Learned Center. The RLS is the authoritative account. This record catalogs the incident's public media and GIS around it, in support of the lessons-learned sharing the wildland community is doing now. > `Read the RLS` · `Open in viewer` · `Add to this record` `Read the RLS` links the [Lessons Learned Center incident page](https://lessons.wildfire.gov/incident/chelan-hills-fire-entrapment-and-escape-2026); the viewer link opens the [served collection](https://simtable.acequia.io/incidents/2026-WA-Chelan-Hills-Fire-Entrapment/collection.json) in the [incident-viewer](https://redfish.acequia.io/guerin/apps/stac-workbench/?stac=https%3A%2F%2Fsimtable.acequia.io%2Fincidents%2F2026-WA-Chelan-Hills-Fire-Entrapment%2Fcollection.json). Constraints honored: no injury or fatality detail on the card; the RLS named first and named authoritative; crew members named nowhere the RLS does not name them; no product sentence within the card or adjacent to it. This entry gets a third button and the RLS gets top billing; that asymmetry IS the frame. ### The Maria entry (the record behind the story) (COPY): > **2019 Maria Fire** > October 2019 · Ventura County, California > The record behind the story: 37 cataloged links, 23 media and 14 GIS, from a fire that ran from 50 to 750 acres in its first hour. Every item points to its original public source with its rights recorded verbatim. > `Open in viewer` · `Add to this record` Facts sourced from the served [Maria README](https://simtable.acequia.io/incidents/2019-CA-Maria-Fire/README.md) (37 items, 23 media, 14 GIS, 50 to 750 acres in the first hour). Viewer link: [open in incident-viewer](https://redfish.acequia.io/guerin/apps/stac-workbench/?stac=https%3A%2F%2Fsimtable.acequia.io%2Fincidents%2F2019-CA-Maria-Fire%2Fcollection.json). --- ## 6. What NOT to say - **The Chelan respect gate (hard).** Nowhere on the Chelan card, in the Chelan record, or adjacent on the index page: product pitch, "this is why you need," alert.live capability framing, or any line that reads as the incident selling something. The frame is community lessons-learned support only; any narrative use beyond factual support requires Stephen's explicit ask first, per the [bead's limitation](https://redfish.acequia.io/guerin/.agents/68d88c38-e223-4385-b8c9-f929eea309a3/about.md). No entrapment detail as color; the RLS carries the account. - **No pretend security.** Until the access layer enforces per-person access: no "private," no "secure," no "only your crew can see this," no lock or shield iconography. The one honest line (§1, §3) is the only sentence about access, everywhere access is implied. - **No faked deposit.** Never "sent," "shared with command staff," "submitted," or a green check when the PUT did not land. The degradation screen (§4) is the only alternative to success and must not resemble it. - **No surveillance grammar.** Never "harvest," "collect," "crowdsource," "turn your phone into a sensor," "citizen reporting network." Members add to a record they belong to. Carried verbatim from [note 00 §5](00-alert-live-new-site-messaging.md). - **No counterfactual salvation.** No card, tab, or empty state may claim the record would have saved anyone, at Chelan or anywhere. - **No capability inflation.** No "real-time," "instant," "your agency will see this immediately," or delivery promises of any kind; the record promises custody and provenance, never receipt. - **House rules in all deployed copy:** no em dashes; no "not X, but Y" construction; numbers only from the served collections' own READMEs or verified records; death tolls appear on no card. --- *2026-07-23 · © 2026 RedfishGroup · author: John (rhetoric persona, bead 6715f286) / CE for Stephen Guerin · all rights reserved (unless otherwise specified)*