A proposed specification for the documentation community to codify what makes docs agent-friendly. The spec focuses on meeting the technical constraints of agent platforms (truncation limits, content negotiation, discovery); it does not consider qualitative evaluation of content.
active 2026-02-22 → 2026-05-09 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 77 days from 2026-02-22 to 2026-05-09. Pushes: 13 total, peak 3 in a day. Pull requests: 4 total, peak 1 in a day. Issues: 3 total, peak 2 in a day. Comments: 6 total, peak 1 in a day. Stars: 7 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| dacharyc | 19 | 13 | 1 | 5 |
| rhyannonjoy | 6 | 0 | 3 | 0 |
| devalog | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#14dacharyc2026-05-09 02:54markdown-content-parity should distinguish intentional audience segmentation from unintentional content drift
- Issue#25rhyannonjoy2026-05-04 04:23platform data (known platform limits): add Cascade web fetch notes
- Pull request#26rhyannonjoy2026-05-03 17:11
- Issue comment#23dacharyc2026-04-26 23:40Split llms-txt-directive into separate HTML and markdown checks
- Pull request#21dacharyc2026-04-22 01:49
- Issue comment#14devalog2026-04-10 17:12markdown-content-parity should distinguish intentional audience segmentation from unintentional content drift
- Issue comment#14dacharyc2026-04-08 23:45markdown-content-parity should distinguish intentional audience segmentation from unintentional content drift
- Pull request#13rhyannonjoy2026-04-02 07:11
- Issue#8rhyannonjoy2026-03-21 19:49platforms data(known platform limits): add Cursor IDE web fetch notes
- Issue comment#8dacharyc2026-03-21 19:47platforms data(known platform limits): add Cursor IDE web fetch notes
- Issue#8rhyannonjoy2026-03-21 02:27platforms data(known platform limits): add Cursor IDE web fetch notes
- Issue comment#6dacharyc2026-03-12 03:49platform data(known platform limits): add OpenAI web search notes
- Pull request#5rhyannonjoy2026-03-07 22:01
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 7 stars here means stars gained during the window, not the repo's star count.