Momentum

Approval is the most-sighted pattern of the last 90 days
Approval
47none prior
Observability
46none prior
Permissions
39none prior
Review
23none prior
Context
21up from 1
Human Handoff
21none prior
Agent-to-Agent
20none prior

Published, annotated sightings attached to each pattern, trailing 90 days (Jul 28 – Oct 26). The 1px tick on each track is the prior 90 days (Apr 29 – Jul 28). n = 238.

View as table
PatternTrailing 90dPrior 90d
Approval470
Observability460
Permissions390
Review230
Confidence Signaling210
Context211
Human Handoff210
Agent-to-Agent200
Where the momentum came from, week by week
Approval8 this week
Observability3 this week
Permissions3 this week
Review5 this week
Context1 this week
Human Handoff5 this week
Agent-to-Agent5 this week

Weekly counts of published, annotated sightings per pattern over the last 12 weeks (Aug 10 – Oct 26), every row on one scale; the dot is the latest week. Hover a week to read every pattern at once. n = 238.

View as table
PatternAug 10Aug 17Aug 24Aug 31Sep 7Sep 14Sep 21Sep 28Oct 5Oct 12Oct 19Oct 26
Approval000832632878
Observability000758925253
Permissions100842732453
Review000121522145
Confidence Signaling000221143152
Context000331603221
Human Handoff010400430045
Agent-to-Agent000231213125

Coverage & Divergence

Which products show which interactions, computed from anatomy-level sightings. Anthropic first, OpenAI as the standing counterpart. Full map →

Claude CodeMCP + MCP AppsApps SDK (apps in ChatGPT)ChatGPTChatGPT AtlasChatGPT agent modeCodex
Approval
Delegation
Planning
Progress
Human Handoff
Interruption
Recovery
Agent Identity
Memory
Generative UI

⬤ ring = one pattern's anatomy · 1 segment = 1 anatomy part · filled segment = part evidenced for that surface · hover a cell for its parts and last evidence · blank = no sighting yet

How to read a pattern

  1. The problem line. One sentence on what the person needs, product-agnostic. If it isn't your problem, it isn't your pattern.
  2. The maturity status. Watching → emerging → established → contested → fading, re-scored from sighting velocity. Methodology.
  3. Field notes. Every claim traces to a dated source; the side-by-side shows how each vendor handles each part of the interaction.
  4. Get the code. Patterns with components install via the shadcn registry. Install & MCP.

Watching

Candidate interactions accumulating sightings. Three or more from two independent vendors and they get a page.

  • Confidence Signaling 21 sightings Knowing how much to trust a particular answer.
  • Reach Preview 18 sightings Sizing the blast radius of an agent before it starts, and the ground it has covered since.
  • Emergency Stop 17 sightings Stopping agents fast, in each place they run, and knowing they stopped.
  • Off-Brief Alert 15 sightings Telling a person fast when an agent does something the brief did not cover.
  • Budget Scoping 14 sightings Setting limits on spend, time, or reach before handing work over.
  • Comparison View 10 sightings Answering "better or worse than what, and for whom" after a prompt change.
  • Eval Set Authoring 10 sightings Turning "I know it when I see it" into examples and a standard a test can use.
  • Case Drilldown 9 sightings Judging one answer, and deciding whether the judge got it right.
  • Release Decision 9 sightings Deciding whether a prompt change ships, with the evidence in view.
  • Production Drift 8 sightings Knowing when quality slips in production, measured the same way as the tests.
  • Multi-Agent Roster 6 sightings Keeping a team of agents legible: who exists, who is doing what.
  • Ambient Status 4 sightings Knowing what background agents are doing without opening them.
  • Eval Run Setup 4 sightings Choosing what to test and knowing what it will cost before pressing run.