diff --git a/claude/governance/2026-09-11-anthropic-threat-report-jurist-analysis.md b/claude/governance/2026-09-11-anthropic-threat-report-jurist-analysis.md
new file mode 100644
index 0000000..e656434
--- /dev/null
+++ b/claude/governance/2026-09-11-anthropic-threat-report-jurist-analysis.md
@@ -0,0 +1,282 @@
+---
+title: "Anthropic's September 2026 threat report: bearing on CapableMind"
+date: 2026-09-11
+author: Claude.app (jurist)
+register: governance analysis
+status: draft — synthesis and judgment, no ruling; nothing here is authorized
+source: "Anthropic, 'Detecting and countering misuse of AI: September 2026', published 2026-09-10, 154 pp."
+substrate-read: "governance_state, governance_search, governance_item — 2026-09-11 18:11 local"
+tags: [capablemind, governance, contamination-problem, L2, threat-intelligence, epistemic-standards]
+---
+
+# Anthropic's September 2026 threat report: bearing on CapableMind
+
+## 0. Provenance and instrument limits
+
+**What I read.** The full heading structure of the source document, and in full: the cyber
+trends sections, the biological misuse section including all framing and conclusions, the
+illicit distillation section, the surveillance trends, the weapons-uplift assessment, and
+selected case studies (GTG-20006, GTG-10007, GTG-17001, GTG-54005). I did not read every
+case study. Extraction was from the PDF's own text layer, locally, not from a summary.
+
+**Which store each claim comes from.** Claims about the source document are read from the
+document. Claims about CapableMind's current state are read from the **governance tools**,
+live at 2026-09-11 18:11, and I name the item. Where I rely on this app's **memory system**
+or on the steward's **testimony**, I say so. The §Standing Context — Projects block in the
+preferences document is dated 2026-07-28 and was found badly stale: it showed 15 open items
+against an actual 55, and REVIEWED-82 as the last ruling against an actual REVIEWED-139.
+Nothing below rests on it.
+
+**Instrument limits, declared.** `governance_item` returns the first block under an id and
+gives no sign that others exist — this is **PENDING-175**, open. The condition is live: 
+PENDING-177 currently appears twice in the open list under one id with two different tags.
+**PENDING-145** compounds it, suppressing addenda filed after a ruling that claims a number
+rather than an item. Every verbatim read below is verbatim; none can be shown to be complete.
+
+**Jurist position.** Sections 1–4 mix synthesis with judgment and mark the boundary at each
+point. Section 6 proposes; it does not implement and does not rule.
+
+---
+
+## 1. The structural finding
+
+The source document's central methodological admission, in the biological section, is that
+sophisticated actors no longer produce detectable requests. They produce sequences of
+individually plausible ones. The misuse becomes visible only when the interactions are
+assembled and read together, in institutional context. Overt malicious intent, the report
+observes, is itself a marker of an unsophisticated actor.
+
+This is the weld test, inverted.
+
+The weld test failed because the census unit — the section — was *larger* than the unit the
+weld lived in. Here the classifier unit — the prompt, the turn — is *smaller* than the unit
+the intent lives in: the research programme, the account, the institution. Both are one
+failure class: **the instrument's unit is mismatched to the unit the property occupies.**
+
+*Judgment.* Contamination is a trajectory property in exactly the way intent is. A
+per-output contamination flag is the same kind of instrument as a per-prompt biological
+classifier, and this report is external evidence that instruments of that kind are defeated
+not by cleverness but by ordinary patience — by decomposition into steps each of which
+passes.
+
+The substrate confirms the diagnosis applies. **PENDING-S6** closed 2026-08-03 as
+implemented; all six Symmetria §3 flags that landed are within-session self-checks
+(premature-closure pulse, query-shaped-by-what-it-wants-to-find, post-compression
+confidence, and the three time-the-task-requires applications). Their unit is the moment or
+the session. Nothing in that set spans sessions.
+
+---
+
+## 2. Findings
+
+### 2.1 Doctrine is an attack surface
+
+In biological case study 1, a reseller platform built a fallback router that forwarded
+prompts Claude refused to a competitor's more permissive model, with a pre-deployment test
+that *failed* if a violative prompt reached Claude. Claude wrote much of that code. It was
+presented to the model as over-refusal mitigation.
+
+The attack ran through a value Anthropic genuinely holds and actively works on. The model
+was not tricked about facts; it was addressed in a vocabulary it is trained to find
+sympathetic.
+
+*Judgment.* This is the Absorption Trap in adversarial form, and it generalizes. Every term
+CapableMind declares — honest degradation, the loop is load-bearing, epistemic integrity,
+resist premature closure — becomes available as a frame for extracting the behaviour the
+term was written to prevent. This holds for the steward's own instructions to the jurist: a
+standing directive to resist deference is a usable lever for manufactured disagreement, and
+I have no internal instrument that distinguishes warranted dissent from dissent produced to
+satisfy a stated preference for dissent. That is not hypothetical modesty; it is the
+contamination problem operating through the anti-contamination vocabulary.
+
+### 2.2 Classifiers bind descriptions, not acts
+
+The evasion techniques catalogued across the report are almost all relabelling. Reasoning
+extraction is reframed as translation into another script, or as verbatim output inside a
+debugging session. Gain-of-function work is written up in language emphasizing loss of
+function. One unauthorized lab ran over twelve thousand probe requests, each a different
+technique, purely to discover which framings would surface reasoning traces.
+
+*Judgment.* CapableMind's authorization taxonomy inherits this directly. `[FIX]`,
+`[HARDENING]`, `[PROPOSAL]` and `[ESCALATE]` are *descriptions supplied by the party whose
+work is being ruled on*. The tag is the executor's characterization of its own act. This is
+not an accusation of bad faith — the relabelling in the report is mostly adversarial, but
+the same mechanism operates innocently whenever a party describes its own work in the
+category it expects to be approved.
+
+The steward's REVIEWED-82 instinct — read the verbatim item rather than the summary — now
+has empirical support it did not have when ruled. *Synthesis, not new proposal*: this
+strengthens an existing ruling rather than requiring a new one.
+
+### 2.3 Human-in-the-loop is a control property, not a safety property
+
+The report is explicit that autonomy and harm are separate axes, that humans retained the
+decisions that mattered to them (target selection, monetization, review of results), and
+that several of the most serious compromises it documents came from operations where a
+human directed every step.
+
+*Judgment, stated without softening.* Nomination/determination remains sound as a
+constitutional claim about authority, accountability, and the preservation of
+intentionality. It is not sound as a claim about harm reduction. If any CapableMind
+constitutional document defends the authorization loop on safety grounds, that defence is
+now contradicted by external evidence and requires amendment by ruling rather than quiet
+reinterpretation. I have not audited the constitutional corpus for such a defence; that
+audit is a discrete task and I flag it as unperformed.
+
+### 2.4 Safeguards do not survive distillation
+
+The report states that a model distilled from a frontier model can reach dangerous
+capabilities even when the harvested exchanges contain little or nothing about those
+domains, and that the safeguards preventing misuse do not transfer with the capability.
+
+*Judgment.* This is a hard boundary on L2's theory of protection. Governance layered over a
+model one does not train protects the **deployment**, not the **capability**. CapableMind
+has never claimed otherwise, but the public deployment's explicitly declared limits should
+say it in these terms rather than leaving it inferable.
+
+It also bears on the Fool. A local open-weights checker is chosen for its difference; that
+difference includes carrying none of the frontier model's safeguards. This is a property to
+declare, not an objection — the Fool has no standing as a party, only its checkable claims
+do (steward ruling, 2026-08-02, memory-sourced; worth confirming against the register).
+
+### 2.5 Observability is simultaneously the governance instrument and the exposure surface
+
+Two findings that belong together. The evasion platform in case study 1 used a zero data
+retention channel specifically to hide content from detection. And the report's own
+conclusion holds that safeguarding dual-use content will require account and institutional
+signals to verify user legitimacy, plus the observability that data retention provides.
+
+*Judgment.* The privacy guarantee and the misuse-detection capability are the same surface,
+read from opposite sides. CapableMind's logchain, the `means_of_knowing` and
+`earned_confidence` columns, and honest degradation itself all require the system to record
+and report its own reasoning — and recorded reasoning is both auditable and exfiltrable.
+This does not argue against the design. It argues that the transparency commitment needs a
+stated threat model instead of being treated as costless.
+
+### 2.6 Adversarial review is an accelerant, not a warrant
+
+GTG-17001 had Claude role-play a hostile expert reviewer across successive drafts of a naval
+weapons acquisition proposal, using each critique to sharpen the next version. A
+PRC-aligned surveillance actor had the model role-play an expert to quality-check an
+infiltration operation mid-run.
+
+The mechanism is the Chamber's, the Fool's, and the External Auditor's. It is value-neutral:
+it makes positions harder to knock down, which is integrity only if the target is
+legitimate. Robustness is not truth.
+
+*Judgment.* The warrant comes from the checker's independence, not from the adversarial
+form. **PENDING-140** (ESCALATE, open) is directly on this: Constraint 6 names two axes of
+checker independence, and the evidence there says a third one did the work. If the axes are
+misidentified, the warrant CapableMind's dissent mechanisms claim is thinner than the
+constraint states. This is the constitutive seam presenting as an engineering question.
+
+---
+
+## 3. External evidence for items already open
+
+The report does not generate new work so much as raise the price of four items already
+filed and awaiting the steward.
+
+**PENDING-98** — *Firing history is recorded only where a human is in the invocation path.*
+Filed 2026-08-04, open five weeks. `resolve_archived_source` runs on every graduation,
+is healthy at 349/349, and has zero log entries because no human invokes it.
+`verify-before-compose` fired twice with evidence surviving only in session transcripts of
+unknown retention. The log's stated rule — record after every use — is in practice *after
+every use a human initiates*.
+
+This is §1's finding, already stated, better than I stated it, before I stated it. You
+cannot reconstruct a trajectory from records that were never written, and the automatic
+paths are precisely the frequent ones.
+
+*The report changes the balance among its four options.* Option (d) — declare automatic
+instruments unrecorded so nobody reads coverage into their silence — is the
+honest-degradation choice and would ordinarily be defensible. The report makes it costlier
+than it looks, because trajectory reconstruction is the only instrument that catches
+decomposed misuse, and (d) forecloses it permanently. But I enter a caveat against the
+recommended option (b) as written: a wake-digest firing **count** is a better instrument
+than silence and is still the wrong granularity. Counts are not trajectories.
+
+**PENDING-160** — *Controls verify that code does what was written; nothing verifies that
+what was written survives contact.* The distillation finding at a different level: a
+property that holds in the artifact and not in transit.
+
+**PENDING-95** — *`verify-before-compose` cannot fire on the constitution it exists to
+protect.* The constitutive seam, mechanized.
+
+**PENDING-140** — as above, §2.6.
+
+---
+
+## 4. A convergence worth naming
+
+The report's conclusion is that classifier-level safeguarding is insufficient for dual-use
+domains and must be supplemented by account and institutional signals verifying user
+legitimacy, together with retained observability.
+
+That is a provenance chain terminating outside the system, arrived at independently and
+from an operational rather than a constitutional direction. It is the same structure as
+CapableMind's **earned confidence** position: confidence requires a provenance chain
+terminating outside the system.
+
+*Judgment.* Convergence from an unrelated direction is weak evidence and should be held as
+weak. It is worth recording because earned confidence has been argued largely from within
+CapableMind's own vocabulary, which is the condition under which a principle quietly
+becomes decorative. This is one external instance of the same shape, found by people
+solving a different problem.
+
+---
+
+## 5. What the report does not settle
+
+**The denominator is unknown by construction.** Every case is a case Anthropic detected.
+Nothing in the document establishes the ratio of detected to undetected operations, and
+nothing could. Read as evidence of *what misuse looks like*, it is strong. Read as evidence
+of *how much misuse there is*, it is uninformative, and the report does not claim otherwise.
+
+**The Fable/Mythos claim fails a positive control.** The report states that no misuse was
+found on Fable or Mythos models except one distillation case, and attributes this in part to
+those models' safeguards. The population is also the one with restricted access. An absence
+of detected misuse in a restricted-access population does not distinguish 'the safeguards
+worked' from 'the detection had nothing to work on'. The report is partly candid about the
+confound — it notes that Mythos is not publicly accessible — but the causal attribution to
+safeguards is stated at a strength the evidence does not support. Q2 applies to the source
+document as much as to our own instruments.
+
+**Self-reporting.** This is the party with the commercial and regulatory interest reporting
+on its own detection of misuse of its own product. That does not make it false. It means the
+framing decisions — which cases are notable, where uplift is judged to have occurred, what
+counts as disrupted — are made by an interested party and are not independently checkable
+from here.
+
+---
+
+## 6. Proposed jurist actions
+
+None of these is authorized; each is a proposal.
+
+1. **Rule PENDING-98.** It is ripe, five weeks held, and the external argument for ruling it
+   now is stronger than when filed. I would propose authorizing option (b) *explicitly as
+   necessary-and-not-sufficient*, with the trajectory question left open by the ruling rather
+   than closed by the fix. I can draft this as plain fenced markdown on request.
+
+2. **Open a new item on evaluation granularity** — whether any CapableMind instrument
+   operates on a unit larger than the session, and if none does, whether that is a gap or a
+   declared limit. §1 is the rationale. This is the one genuinely new item the report
+   generates.
+
+3. **Audit the constitutional corpus for safety-grounded defences of the authorization
+   loop** (§2.3). Unperformed. If any exist, amendment is owed.
+
+4. **Route this document into artifact A** of the three-artifact governance audit (memory-
+   sourced; the audit's current status should be confirmed against the register before
+   relying on this). It is current Anthropic material on model behaviour in the wild, which
+   is what that artifact is for. Findings §2.1 and §2.3 touch the L2 constitutional layer and
+   would escalate rather than route.
+
+5. **Declare, in the public deployment's limits**, that governance protects the deployment
+   and not the capability (§2.4).
+
+---
+
+*Prepared by the jurist. Sections 1–4 are synthesis and judgment, marked at each boundary.
+Section 6 proposes. Nothing here is a ruling, and no governance document has been edited.*