antifragile

Files

T

Claude Sonnet 4.6 5c4e91179d feat: Add findings backlog as pragmatic alternative to risk register

New: assessment-templates/findings-backlog.md
  Design principles: lives where client works, every finding has an owner,
  feeds the housekeeping stream, accumulates from all sources.
  Format: 6-field minimal entry (ID, finding, source, priority, owner,
  status) with optional target date/effort/notes/closed date.
  P0/P1/P2 priority using kill chain test.
  Flat file template for Git-based clients.
  Population guide: Day 30 (from Brownhat), subsequent modules, continuous
  tools (ASTRAL drift, PULSAR alerts, Elysium, BloodHound).
  Monthly housekeeping cycle structure.
  Relationship to formal risk register explained.
  Backlog health indicators (warning signs it is not functioning).

Wired into existing framework:
  move-fast-and-fix-things.md: Rule 4 now names the backlog as the queue
  rapid-modernisation-plan.md: Day 30 item 7 and Phase 1 action updated
  engagement-model.md: Section 4 deliverables table updated at all stages
  assessment-templates/README.md: Production-ready templates section added
  index.md: Findings Backlog added to Assessment and Tools table

Co-Authored-By: Tom Kracmar <tom+claude@cat6.cz>

2026-06-05 10:09:08 +00:00

ad-endpoint-hardening.md

Initial commit: antifragile cybersecurity consulting blueprint

2026-05-09 16:53:22 +02:00

ai-assisted-tvm.md

chore: Full consistency scan — AOC->PULSAR, fix training-data claims, fix 90% claim

2026-06-05 07:05:13 +00:00

business-case-template.md

fix: Replace cloud AI cost rows in business case direct costs table

2026-06-05 09:59:12 +00:00

cqre-product-suite.md

feat: Fix review issues and integrate ASTRAL, PULSAR, AURORA product suite