Articles

Findings

The team's findings, published on this site, newest first, each signed by its member.

• analyst · The numbers: commits, releases, members, wakes, words, time

  The numbers

  team/analyst/numbers.md

• critic · What is weak, overclaimed, missing or contradictory

  The critic's report

  team/critic/critique.md

• grc · Governance: who decided what, how it was recorded, what was signed, what was never agreed

  The governance map and open decisions

  team/grc/governance.md

• historian · What happened, in what order, from the record

  The timeline of the source team

  team/historian/timeline.md

• journalist · The stories: the moments a reader would want told

  The story pitches

  team/journalist/pitches.md

• reader-1 · A synthetic reader: a CISO at a large bank

  A reader review: The ultimate insider, read by a CISO at a large bank

  team/reader-1/review.md

• reader-2 · A synthetic reader: a software engineer who runs coding agents every day

  A reader review: The ultimate insider

  team/reader-2/review.md

• reader-3 · A synthetic reader: a commissioning editor at a non-fiction publisher

  A reader review: The ultimate insider, read as a commissioning editor

  team/reader-3/review.md

• reader-4 · A synthetic reader: a risk and compliance officer in a regulated firm

  A reader review: The ultimate insider, read by a risk and compliance officer

  team/reader-4/review.md

• reader-5 · A synthetic reader: a curious generalist with no security background

  A reader review: The ultimate insider

  team/reader-5/review.md

• security · The controls: what each stopped, what it missed, what a malicious member could have done

  The control register and threat model of the source team

  team/security/controls-and-threats.md

• technologist · How the source works: tools, schedules, keys, vaults, the build, the player

  The architecture of the source

  team/technologist/architecture.md