Skip to content

Incident: done stays done, and the report as Markdown and PDF - #134

Merged
goetchstone merged 2 commits into
mainfrom
feat/report-ticks-md
Oct 28, 2026
Merged

goetchstone merged 2 commits into
mainfrom
feat/report-ticks-md

Conversation

@goetchstone

Copy link
Copy Markdown
Owner

After a run through Respond a week into the real incident, Still to do kept asking for what was done. Each cause is fixed as a rule (failure log 2026-10-28):

  • Mark Done… for what no log can show (a sender unblocked, contacts warned by phone), kept with the incident and undoable. Never on a lock, a computer, or a read.
  • One warn item, one pull-again item across every email, counted as Report counts.
  • That Was Them covers an IPv6 address's /64, and answers "is this address theirs" from Respond.
  • Pull Again only for a mailbox no read holds whole past the email.

The report is now one document drawn as PDF, Markdown and text (the Markdown escaped, so an attacker's subject stays words). It has a summary the on-device model can draft from the facts, dropping any sentence with a number the facts don't hold.

The README now leads with incident response and lists what's still only in GamGUI (from a parity audit).

🤖 Generated with Claude Code

goetchstone and others added 2 commits October 28, 2026 08:16
Still to do kept asking for what was done (failure log 2026-10-28):
Mark Done for what no log shows, one warn and one pull-again item,
marks that answer the address question by network, and Pull Again
only for a mailbox no read holds whole. The report is one document
drawn as text, Markdown and PDF, with a summary the on-device model
can draft from the facts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@goetchstone
goetchstone merged commit c15ccc9 into main Oct 28, 2026
7 checks passed
@goetchstone
goetchstone deleted the feat/report-ticks-md branch October 28, 2026 12:49
goetchstone added a commit that referenced this pull request Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant