KTP/
github
created 26 October 2026 · last modified 26 October 2026
The next step · a worksheet, not a score

TTGD Culture Assessment.

Four dimensions of security culture from Break the Chain, each at one of four levels. Your weakest dimension sets your cultural TTGD ceiling; the result names it, so you know what to fix first.

Nothing you type leaves this browser. Answers are kept on this device only (ktp.audit.v1); nothing is collected.

These are sample answers. Change any of them, or clear them and start your own.

Dimension 01 of 04 Decision Authority (pp. 399–400)
PatternTTGD impactWhat this looks like
Diagnostic questions
  • “Can Security isolate a production system without VP approval?” If no → Levels 1–2
  • “How many approval signatures are required for an automated response?” If > 2 → Level 2
  • “Do pre-authorized playbooks exist for top 5 cascade pathways?” If no → Levels 1–2
  • “Can the automated response execute, then notify humans?” If no → Levels 1–3

What this means: If you’re at Levels 1–2 and trying to achieve TTGD < 5 minutes, you have a structural impossibility. The culture prevents what the technology enables.

The book’s table gives Level 2 as 2–4 hours; the ceiling list under it says Levels 1–2 cannot break 2 hours. The table value is used here (errata candidate for the second printing).

Dimension 02 of 04 Incentive Alignment (pp. 400–401)
What gets rewardedBehavior this drivesTTGD impact
Current state check
  • Pull your team’s last performance reviews. Count mentions of “prevented” vs. “responded to.”
  • Check bonus structures. What percentage is tied to prevention metrics vs. incident metrics?
  • Ask: “If someone prevents 10 cascades (zero incidents visible), do they get promoted or ignored?”

What this means: If you reward incident count, you get people who don’t mind having incidents. Visibility during a crisis becomes how they prove value. Prevention threatens that visibility.

This table has no ceiling column. The ceilings shown follow the book’s worked example (p. 406); Level 1 has no figure there.

Dimension 03 of 04 Trust Boundaries (pp. 402–403)
Automation trustWhat’s automatedTTGD ceiling
Diagnostic questions
  • “Can the automated response isolate a system, then notify humans?” If no → Levels 1–3
  • “Has the automated response ever isolated something incorrectly?” If not: “Then why don’t we trust it?” (irrational fear). If so: “What changed to prevent recurrence?” (learning opportunity)
  • “What’s the approval path for automated containment?” Count the steps. That’s your TTGD minimum.

What this means: Trust boundaries are risk management. But there are two risks: risk that automation acts incorrectly (isolated wrong system) vs. risk that automation doesn’t act fast enough (cascade reaches Ring 0). Most organizations only measure the first risk and ignore the second.

Dimension 04 of 04 Measurement Philosophy (pp. 403–405)
What gets measuredWhat this optimizes forCultural message
Current state check: look at your security dashboard right now. What’s on it?
  • If it’s “alerts per day” and “tickets closed” → Level 1.
  • If it’s “MTTR” and “detection rate” → Level 2.
  • If it’s “Attack Stage of detection” and “blast radius” → Level 3.
  • If it’s “TTGD” and “prevented loss quantified” → Level 4.

What this means: Your dashboard reveals your philosophy, and your philosophy determines what behavior you’ll get from your team.

This table has no ceiling column. The ceilings shown follow the book’s worked example (p. 406); Level 1 has no figure there.

The boundary

A trust score is a governance signal, not trust. The result is a worksheet of dependencies, evidence, and responsibilities. It does not certify safety or assign people a trust rating.

KTP red lines
  1. 01No permanent person score.
  2. 02No hidden human scoring.
  3. 03No unappealable autonomy denial.
  4. 04No indefinite memory without expiration.
  5. 05No purpose drift.
  6. 06No surveillance without attestation.
  7. 07No trust computation without repair path.
  8. 08No use beyond declared domain.
  9. 09No protocol without governance.
  10. 10No silent upstream value injection.

KTP scores actions and trajectories for earned autonomy. It must not become a permanent moral score on people. The red lines above are non-negotiable; an implementation that violates any one of them is not a KTP implementation, regardless of branding.

Where this comes from

The nine tests are the Trust Infrastructure Audit v0.1 from the KTP synthesis. The culture assessment is Chapter 10 of Break the Chain (pp. 399–406), reproduced in the book’s own words; the TTGD Measurement Toolkit, a separate backer reward, measures the number itself. The story that leads here: When Recovery Becomes the Outage.