Skip to content

Document Organizations matrix escalation-axis re-derivation - #5

Closed
jgulyash wants to merge 1 commit into
mainfrom
claude/threat-matrix-scoring-umg9vl
Closed

Document Organizations matrix escalation-axis re-derivation#5
jgulyash wants to merge 1 commit into
mainfrom
claude/threat-matrix-scoring-umg9vl

Conversation

@jgulyash

Copy link
Copy Markdown
Owner

Summary

This PR adds the written re-derivation of the Organizations matrix's escalation scoring axes, closing a documentation gap identified in the escalation_rubric. The Organizations matrix was scored at V1.5 without a preserved written convention for its axis semantics, unlike the Infrastructure matrix. This change documents the post-hoc re-derivation ratified under Ruling 1, Option A (2026-07-27).

Key Changes

  • Added docs/methodology/DESIGN-b5-org-escalation-scoring.md — A comprehensive design document that:

    • Establishes the institutional harm model as the Organizations matrix's semantic foundation
    • Re-derives all four escalation axes (impact_potential, blast_radius_potential, recoverability_inverse, detectability) with explicit tier definitions anchored to institutional consequences rather than physical casualty counts
    • Elects stakeholder/population scope of institutional harm as the blast_radius_potential semantics (Ruling 1, Option A)
    • Clarifies that no severity_floor applies to the Organizations matrix (recorded at B5 merge with zero floors across 240 indicators)
    • Validates the re-derived semantics against the shipped 240-indicator population, confirming monotone growth across lifecycle phases and correct tier placement
    • Explicitly routes Phase-4 trace-behavior classification to the pending aftermath blast reconciliation rather than pre-ratifying it
    • Documents the audience-vs-victims distinction to guard against misreading narrative reach as stakeholder harm
  • Updated CHANGELOG.md — Added entry under [Unreleased] documenting the new design document and its scope

  • Updated docs/methodology/README.md — Added reference to the new design document in the methodology index

Notable Implementation Details

  • The document is explicitly authored post-hoc and states so; it does not silently ratify disagreements between authored values and the re-derived semantics, instead routing those to the aftermath reconciliation pass
  • The escalation formula, thresholds, and detectability flip remain unchanged; only axis semantics and blast_radius base rates are re-anchored
  • Validation confirms the 240-indicator population (weight range 2.69–7.32, bands: 105 medium / 123 high / 12 critical) conforms to the re-derived tiers
  • The seam section explicitly defers Phase-4 trace-behavior scope classification to a future reconciliation pass, maintaining clarity about what this document settles vs. what it routes onward

https://claude.ai/code/session_016gU3axaLSJKhzUnqa6QdT1

…g 1, Option A)

Write the missing Organizations re-derivation the escalation_rubric's
'other matrices re-derive' note requires. The 240 Organizations
indicators were scored at V1.5 (b2c4267) via parallel authoring agents
whose blast convention was never written down; this doc closes that
gap post-hoc per Ruling 1 Option A (Jay, 2026-07-27):
blast_radius_potential in Organizations means stakeholder/population
scope of institutional harm, not physical-casualty count and not raw
audience reach.

Re-anchors all four axes to the institutional harm model with base-rate
tiers derived from and validated against the authored population
(phase medians, tier spot-checks, weight range 2.69-7.32, zero
severity_floor). Ratifies the continuing-harm reading for Phase-4
amplification/narrative/coercive behaviors; explicitly routes the
Phase-4 trace-behavior seam (evidence destruction, financial
disposition, cover, rebranding, after-action) to the pending aftermath
blast reconciliation, citing the V1.3 B-10 recoverability seam as
procedural precedent. Framework data unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016gU3axaLSJKhzUnqa6QdT1
@jgulyash jgulyash closed this Jul 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.

2 participants