doug
DashboardScoreboardQueueDocsGitHubAbout
Menu
DashboardScoreboardQueueDocsGitHubAbout
Sign in

Getting started

  • Introduction
  • Quickstart

Concepts

  • Risk routing
  • Defect labels
  • The cleared band
  • What Doug gets wrong

Reference

  • CLI · doug-backtest
  • The report

Coming up

  • MCP · Pattern Garden
  • REST API

Meta

  • Changelog
View as llms.txt

Coming up

MCP · Pattern Garden

Planned
No server exists yet. The Pattern Garden is an MCP server your coding agent queries before it writes. It serves outcome-anchored patterns distilled from public-repo history: for a given problem shape, the solution variants people actually write — each carrying its revert record, its survival record, and citations to real PRs.

Base models trained on public code learned what’s common. The garden knows what’s fit, because every pattern is joined to what production did next. Frequency isn’t fitness.

Planned tools

doug.ask tool · planned
Describe the change you’re about to make; get known variants ranked by outcome evidence, with failure modes and citations.
doug.check tool · planned
Submit a draft diff; get back any losing-variant matches with the cross-repo record attached.

Status, honestly:

The garden is gated on our own evidence bar — patterns ship only after their outcome deltas replicate across repos. First domain: schema migrations. No dates promised until the probes pass.
MCP · PLANNED
doug.ask("backfill a NOT NULL column on a hot table")

→ no adjudicated rows yet
garden stays closed until the probes pass
PreviousThe reportNext REST API