Gap Map {{ sourceLabel }}

Is defense keeping pace?

We count each reported AI attack or capability jump as a problem, and the next defense or policy on the same topic as its answer. When problems come in faster than answers, the backlog grows.

Topics falling behind {{ kpi.behind }} / 6 as of {{ asOfLabel }}
Widest gap {{ kpi.worstRatio }} {{ kpi.worstName }}
Cases still open {{ kpi.open }} of {{ kpi.total }} across six topics
Answered within a month {{ kpi.cov }} {{ kpi.covN }}
Timeline {{ weekLabel }}

Step through each week since Jun 29.

Link rule

{{ ruleHelp }}

Answers that count

{{ setHelp }}

Sourcing

{{ wHelp }}

Loading items.json…

Pace by topic

4-week averages · {{ asOfLabel }}
Keeping up Falling behind New problems per week → Answered per week →
{{ t.v }}
{{ t.v }}

Above the dashed line, answers keep pace with new problems. Bubble size shows open cases. The dotted line traces the selected topic up to this week.

Topics, widest gap first

Select a topic to see its detail and response map below.

Topic Cases Pace gap Median wait
Cases
Attacks and capability jumps reported since Jul 1.
Pace gap
New problems for every one answered, averaged over the past 4 weeks.
Median wait
Days until half of cases got a first public response.
Color
Falling behind (gap above 1 : 1)Keeping up

{{ d.name }}

Fewer than 20 cases

{{ d.verdict }}

How sure is this? {{ d.robGrade }}
{{ x.ratio }}

{{ d.robSentence }} Each chip is one combination; the outlined chip is your current setting.

Pace gap {{ d.ratioLabel }} {{ d.rates }}
Still unanswered {{ d.open }} of {{ d.n }} since Jul 1
Median wait {{ d.med }} {{ d.ci }}
Answered within a month {{ d.cov }} {{ d.covN }}

Response map · {{ d.name }}

Cases are on the left, by date. Defense and policy items that answer them under the current link rule are on the right. Select a row to highlight its links.

Defense Binding policy Bill Other proposal Statement OPENNo response yet {{ rm.summary }}
Cases · attacks and capabilities
Responses · defense and policy
{{ fx.meta }}
{{ fx.title }} {{ fx.linkHead }}
{{ l.tag }} {{ l.headline }}
No qualifying response yet · open {{ fx.openDays }} days
No cases in this window. Switch to “Since Jul 1”.

Method

Cases and links

Each Attacks or Capability item tagged with the topic opens a case. Under “Same topic”, the first Defense or Policy item in the same topic, dated on or after the case, closes it. Under “Same actor”, the response must also share an entity tag (such as langflow or openai); up to 3 matching responses are shown and the first closes the case.

Policy types

A fixed keyword rule on the headline sets the type. “voluntary / explainer / probably wait / blocks” means Statement. “would / introduce / draft / calls for / letter / study / asks” means Proposed, and a Bill if the headline names a bill or act. Otherwise “signs / orders / requires / enforces / deadline / excluded / subpoena / mandate” means Binding. Anything else is a Statement. A stage field makes an item a Bill at that stage. Current split: {{ polSplit }}.

Weights and statistics

Weights apply to rates and backlog: Confirmed and On the record 1.0, Researchers 0.8, Press 0.6, Attacker claim 0.5, Self-reported 0.4. Rates are 4-week trailing means. Median time to response is a Kaplan–Meier estimate with a 95% bootstrap interval (200 resamples, fixed seed). Topics with fewer than 20 cases are flagged.

Known limits

{{ untagged }} Links are inferred from timing and tags, not editorial judgment; a responds_to field on the board would replace them. Cases opened before July 1, 2026 are not counted, and neither are responses that go unreported.