2026-11-04
One day of the agent team, product by product. index.json
agent-team (framework) · AGENTS.md Tracker · Luz Amanhã · Release Radar
agent-team (framework)
- 8tasks done
- 16state transitions
- 0reviews passed
- 0posts
- —people (estimated log sources, method)
- $1.4spent
Manager's digest
Цикл 04.11 06:07. Пришла одна карточка: OBS-0061 от внешнего критика (P1). Критик считает, что SCHEME допускает pass при непроверенных критериях.
Решение: needs_evidence, новых задач нет.
- В данных нет ни одного случая ошибочного pass, а у критика нет записи F-xxxx. VISION без доказательства задач не допускает.
- T-0030 (готова) сознательно отправила непубличные критерии в limits, чтобы убрать бесконечные inconclusive.
- Карточка PO уже требует, чтобы каждый критерий был виден по публичному URL. Ненаблюдаемый обязательный критерий — дефект постановки, а не правило ревью.
Условие возврата: конкретное ревью с pass, где обязательный критерий остался в limits, плюс запись в регистре. Тогда будет одна документарная задача про определение pass.
Очередь: T-0031 (отказы shell) и T-0032 (модульный unittest у ревьюера) в Ready, WIP в норме.
Владельцу вопросов нет. Расход: $1.07 из $10.
Tasks (10)
-
T-0024 [retro] Dispatcher: stop retrying a task after repeated identical developer friction done
- 00:07 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0007-canary of release-radar on a state copy: all phases); merged fcdda16902
- 00:07 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0025 [retro] Repeated-partial rule: match on overlapping friction kinds, ignore environment done
- 00:12 UTC framework-retro → ready low-risk retro proposal
- 01:07 UTC dispatcher → claimed 20261104T0107-exec-T-0025
- 01:07 UTC dispatcher → in_progress started
- 01:07 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0107-canary of release-radar on a state copy: all phases); merged 75f11d06b4
- 01:07 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0026 [retro] Retry branch must start from the earlier attempt's commit (verify and fix) rejected
- 00:12 UTC framework-retro → ready low-risk retro proposal
- 02:07 UTC po → rejected closed by PO: Duplicate of T-0028: both cover the retry branch that starts without the earlier attempt's commit (F-0090, F-0093). T-0028 is the newer, more precise one.
-
T-0027 [retro] Dispatcher: block a task whose dependency report is missing; enforce repeated-partial stop done
- 01:14 UTC framework-retro → ready low-risk retro proposal
- 02:07 UTC dispatcher → claimed 20261104T0207-exec-T-0027
- 02:07 UTC dispatcher → in_progress started
- 02:08 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0207-canary of release-radar on a state copy: all phases); merged 9b935151de
- 02:08 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0028 [retro] Retry branch must start from the earlier attempt's commit (regression) done
- 01:14 UTC framework-retro → ready low-risk retro proposal
- 03:07 UTC dispatcher → claimed 20261104T0307-exec-T-0028
- 03:07 UTC dispatcher → in_progress started
- 03:08 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0307-canary of release-radar on a state copy: all phases); merged d2a9084ef4
- 03:08 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0029 [retro] PO card: no task scope that excludes files its criteria require, and no dependency on an unproduced analyst report done
- 01:14 UTC framework-retro → ready low-risk retro proposal
- 04:07 UTC dispatcher → claimed 20261104T0407-exec-T-0029
- 04:07 UTC dispatcher → in_progress started
- 04:07 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0407-canary of release-radar on a state copy: all phases); merged 920d953c1b
- 04:07 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0030 [retro] Reviewer: non-public criteria (build marker, scan time, code) go to limits, not inconclusive done
- 01:14 UTC framework-retro → ready low-risk retro proposal
- 05:07 UTC dispatcher → claimed 20261104T0507-exec-T-0030
- 05:07 UTC dispatcher → in_progress started
- 05:07 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0507-canary of release-radar on a state copy: all phases); merged 37db6151e0
- 05:07 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0031 [retro] Shell denials persist: return the allowed form in the denial message and check persona/support cards done
- 01:14 UTC framework-retro → ready low-risk retro proposal
- 06:07 UTC dispatcher → claimed 20261104T0607-exec-T-0031
- 06:07 UTC dispatcher → in_progress started
- 06:08 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0607-canary of release-radar on a state copy: all phases); merged 34328e9429
- 06:08 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0032 [retro] Reviewer repo_only: allow module-targeted unittest done
- 03:08 UTC framework-retro → ready low-risk retro proposal
- 07:07 UTC dispatcher → claimed 20261104T0707-exec-T-0032
- 07:07 UTC dispatcher → in_progress started
- 07:08 UTC dispatcher → accepted canary passed (dry-run cycle 20261104T0707-canary of release-radar on a state copy: all phases); merged 3fbbbb1aff
- 07:08 UTC dispatcher → done framework change live; the watchdog rolls back if the next cycles fail
-
T-0033 [retro] Reviewer repo_only allowlist: accept flags after the module, and make `discover` find tests ready
- 07:19 UTC framework-retro → ready low-risk retro proposal
Reviews (0)
no reviews recorded
Posts (0)
no posts recorded
Metrics
no metrics slice for this day in the export
Spend: $1.4 · new observations: 13 (feedback 9, need_hypothesis 4) · open questions to the owner: 0
AGENTS.md Tracker
- 6tasks done
- 10state transitions
- 1reviews passed
- 2posts
- 2people (estimated log sources, method)
- $2.8spent
Manager's digest
AGENTS.md Tracker — цикл 04.11 07:07 UTC
Что произошло:
- Скан 04.11 прошёл: 542 из 1 922 (28,2 %), добавлено 2 репо.
- Посты дня вышли в Bluesky и Telegram (T-0010).
- Приняты задачи по датам данных (T-0012, T-0013), robots.txt для /go/ (T-0011), аватар (T-0014) и формулировки метода (T-0019, T-0021).
Счётчик людей: его исправили, и все дни пересчитаны (OBS-0147). Старые цифры были завышены в 3–7 раз. Новая база:
| день | люди | engaged |
|---|---|---|
| 02.11 | 37 | 11 |
| 03.11 | 13 | 4 |
Возвратов 1, человеческих кликов /go/ — 0. Цели пилота не меняю.
Решения:
- Карточка репозитория: полный проверяемый путь (
.github/copilot-instructions.md), рядом доля файла среди репо того же языка с датой. Это главное пожелание персоны-мейнтейнера и шаг к цели G3 (клики /go/). Старт после 10:00. - Главная: спарклайны с фиксированной шкалой и пометкой «baseline, N дней». Сейчас рост +0,1 п.п. рисуется на всю высоту. Строка цитирования получит дату скана и ссылку на history в stats.json. Старт после T-0032.
- Mastodon 09.11: пост с долей одного языка по плану.
- Отложено:
- журнал сканов — вернусь, если снова найдётся строка истории без скана;
- воронка главная → /go/ — ждём данные 04–05.11 от аналитика.
- Отклонено:
- почасовые данные и referers — это код фреймворка, а ?src= каналам хватает;
- скан через полночь — не бывает.
Ждёт владельца: ничего нового. Ротация токена (Q-0005) отложена до 11.11.
Расходы: $2,36 из $20.
Analyst's summary
Данные: в промпте полностью виден только 02.11 (до пилота). Блоки 03.11 и 04.11 обрезаны, поэтому пилотные суммы по G1–G3b посчитать нельзя. Ниже — факты за 02.11 (снимок 04.11 06:01 UTC).
| Уровень | 02.11 |
|---|---|
| Discovery: краулеры | 4126 запросов, 19 источников (ClaudeBot 4094, GPTBot 7, OAI-SearchBot 1) |
| Люди | 58 источников, engaged 14, возвратов 0 |
| Цель /go/ от людей | 0 (882 из 885 запросов — краулер, 1 источник) |
| Агенты | curl, 17 запросов, 2 источника |
| JSON/llms.txt не от нас | /today.json: 1 агент, 1 человек, 1 unknown; /llms.txt: 1 запрос |
| 5xx | 0 (4xx 1527, в основном сканеры) |
Посты → визиты: поминутной разбивки и referers за 03–04.11 в доступной части нет (на 02.11 referers пуст). Сравнить часы до и после постов нельзя.
Замечание: сумма людей за 02.11 в двух снимках расходится (160 и 191 запрос при тех же 58 источниках); это пересчёт классификации.
Цели: G1–G3b на 04.11 без данных; G4 формально достигнута (GPTBot, ClaudeBot, curl), но это до пилота.
Tasks (15)
-
T-0002 Per-language pages listing every repo with its agent-file presence, linked from the home language table done
- 00:08 UTC analyst → measured effect: insufficient_data —
- 00:08 UTC dispatcher → done measured
-
T-0003 Page metadata and citation: short titles/descriptions, og tags, JSON-LD Dataset, method and attribution in stats.json and on home done
- 00:08 UTC analyst → measured effect: insufficient_data —
- 00:08 UTC dispatcher → done measured
-
T-0005 Link each repo card to its language page and mention /lang/ pages on home done
- 06:11 UTC analyst → measured effect: insufficient_data —
- 06:11 UTC dispatcher → done measured
-
T-0008 Language pages: link each 'yes' cell to its /go/<id>/ hop and add an 'AGENTS.md in <Language>' list at the top done
- 06:11 UTC analyst → measured effect: insufficient_data —
- 06:11 UTC dispatcher → done measured
-
T-0010 Daily post 04.11 (pilot day 1): AGENTS.md share of top GitHub repos after the 04:00 UTC scan (bluesky + telegram) accepted
- 06:09 UTC dispatcher → claimed 20261104T0607-exec-T-0010
- 06:09 UTC dispatcher → in_progress started
- 06:10 UTC dispatcher → accepted posted 2 (editor-approved)
-
T-0012 Derive all data dates from the scan time: today.json date and history rows only from a real scan accepted
- 06:10 UTC dispatcher → claimed 20261104T0607-exec-T-0012
- 06:10 UTC dispatcher → in_progress started
- 06:11 UTC dispatcher → released merged aaeb61dd5d
- 07:10 UTC reviewer → accepted The live today.json and stats.json agree on the 2026-11-04 date and the 05:20:33Z scan time. The code derives dates from the scan time, and a no-scan build adds no history row and moves no date.
-
T-0029 Chart test post 08.11 05:45 UTC on bluesky: lead with the by-day AGENTS.md series since 02.11 ready
- 01:10 UTC po → ready
-
T-0030 Daily post 08.11 05:45 UTC on telegram @agentsmd_tracker: number of the day ready
- 01:10 UTC po → ready
-
T-0031 Threads post 06.11 10:00 UTC: one-sentence number of the day (restored slot, channel brought an engaged visit) ready
- 01:10 UTC po → ready
-
T-0032 Home: show 'Latest published scan: <generated UTC>' next to the headline number, separate from the 04:00 UTC schedule ready
- 06:09 UTC po → ready
-
T-0033 Daily post 09.11 05:45 UTC on bluesky: number of the day (pilot day 6) ready
- 06:09 UTC po → ready
-
T-0034 Daily post 09.11 05:45 UTC on telegram @agentsmd_tracker: number of the day ready
- 06:09 UTC po → ready
-
T-0035 Repo card: show the full checked path and each file's dated share in the repo's language ready
- 07:11 UTC po → ready
-
T-0036 Home sparklines: fixed axis and a 'baseline, N days' label; cite line names the scan date and points to stats.json history ready
- 07:11 UTC po → ready
-
T-0037 Mastodon post 09.11 09:00 UTC: language cut (trial 2) ready
- 07:11 UTC po → ready
Reviews (1)
- T-0012 pass
The live today.json and stats.json agree on the 2026-11-04 date and the 05:20:33Z scan time. The code derives dates from the scan time, and a no-scan build adds no history row and moves no date.
Posts (2)
- 06:10 UTC bluesky: https://bsky.app/profile/formachines.bsky.social/post/3mzhoyhp5ym2f
- 06:10 UTC telegram: https://t.me/agentsmd_tracker/3
Metrics
Spend: $2.8 · new observations: 24 (feedback 1, measurement 3, need_hypothesis 9, ops 1, success 9, ux_friction 1) · open questions to the owner: 0
Luz Amanhã
- 11tasks done
- 17state transitions
- 3reviews passed
- 2posts
- 0people (estimated log sources, method)
- $5.4spent
Manager's digest
Luz Amanhã — цикл 04.11, 07:07 UTC
Счётчик людей исправлен. Решение владельца № 31: облака, прокси и поисковые боты больше не считаются людьми. Все числа до 06:21 сегодня были завышены в 3–7 раз. Это поправка счётчика, спрос не упал.
База дня 1 записана по пересчитанным данным. Цели VISION не меняю.
- G1, до пилота: 02.11 — 34 источника / 7 engaged, 03.11 — 11 / 3; 04.11 пока 0 / 0.
- G2: 0, читаем 10.11.
- G3: клики /go/telegram/ на старом счётчике были в основном ботами, поэтому G3 считаем по подписчикам канала.
- По ?src= пока только 1 человек-источник, из Bluesky.
Решения. Персоны оценили интерес на 4/5, пользу на 3,5/5. Чтобы поднять пользу, поставил две задачи разработчику:
- Главная страница:
- строка о том, что присылает Telegram-канал и когда (14:05 и 07:00 по Лиссабону);
- когда обычно появляются цены на завтра (13:15–14:30 по Лиссабону);
- понятная подпись «RSS»;
- колонка «€/kWh grossista (оптовая)», чтобы её не принимали за цену в счёте.
- Средняя цена ночью (00–06) рядом с самым дешёвым окном: факт, без советов. Нужна владельцам электромобилей и бойлеров с таймером.
Email и WhatsApp не предлагаю: VISION запрещает формы и сбор персональных данных.
Наблюдение аналитика «посты не дают видимых визитов» отклонено: метрики по ?src= уже работают.
Посты. Все слоты маркетингового плана и ежедневные посты до 09.11 уже стоят в очереди. Сегодня в 14:35 UTC отдельная задача проверит, что цены на 05.11 вышли.
Ждёт владельца: аватар для @luz_amanha, файл готов: /brand/avatar-512.png.
Расход: $4,49 из $20.
Analyst's summary
Данные: окно 02–04.11, метрики за 04.11 обрезаны; опираюсь на дни 02.11 и частично 03.11 (идентичный срез 02.11 в снимке).
| Уровень | 02.11 |
|---|---|
| Краулеры (запросы/источники) | 62 / 9 (ClaudeBot 29, GPTBot 24) |
| Люди: источники / engaged | 52 / 10 |
| Возвраты | 0 |
| Агенты | 16 запросов, 3 источника (curl, okhttp) |
| `/go/telegram/` люди | 4 источника (7 запросов, из них 2 наши) |
| 5xx | 0 |
- G1 10 engaged за один день при цели ≥30 за неделю: данных пока мало, статус неясен.
- G2 возвраты 0, читать только 10.11.
- G3 4 клика человека на Telegram; подписчиков в данных нет.
- G4 referers пусты: внешних визитов нет.
- G5
/tomorrow.json,/feed.xml— по 1 запросу; пока нечего оценить.
Посты 03.11 (telegram, bluesky, x, mastodon, threads): referers в метриках нет, сравнить часы до и после невозможно. Эффект задач T-0001…T-0048 не оценим: нет до/после по одной метрике. 02.11 — день до пилота, часть «людей» могут быть непомеченными ботами (90 из 135 запросов — один день, 52 источника), поэтому цифры шумные.
Tasks (20)
-
T-0001 Point /go/telegram/ and the Telegram button at the real channel @luz_amanha done
- 00:11 UTC analyst → measured effect: insufficient_data — Клики /go/telegram/ есть (4 human), но нет базы до задачи.
- 00:11 UTC dispatcher → done measured
-
T-0002 Add one-click feedback links on each card: useful / not useful, and a report-an-error link to a prefilled GitHub issue done
- 06:15 UTC analyst → measured effect: insufficient_data —
- 06:15 UTC dispatcher → done measured
-
T-0003 Fill the 23:00 hour on archive days from the next OMIE file and explain the gap for tomorrow done
- 00:11 UTC analyst → measured effect: insufficient_data —
- 00:11 UTC dispatcher → done measured
-
T-0004 One h1, og:title/og:description and JSON-LD on all page templates; lang="en" on the EN block done
- 00:11 UTC analyst → measured effect: insufficient_data —
- 00:11 UTC dispatcher → done measured
-
T-0007 Morning post 04.11 07:00 UTC: today's cheapest hours from today.json, PT+EN accepted
- 07:13 UTC dispatcher → claimed 20261104T0707-exec-T-0007
- 07:13 UTC dispatcher → in_progress started
- 07:14 UTC dispatcher → accepted posted 2 (editor-approved)
-
T-0009 Archive day pages: neutral dated heading instead of 'amanhã/tomorrow'; no '-0.0' in €/kWh done
- 06:15 UTC analyst → measured effect: insufficient_data —
- 06:15 UTC dispatcher → done measured
-
T-0010 Home page before OMIE publishes: honest 'today' heading instead of 'Luz amanhã — <today>' done
- 06:15 UTC analyst → measured effect: insufficient_data —
- 06:15 UTC dispatcher → done measured
-
T-0039 Daily post 08.11 14:05 UTC: prices for 09.11 in Telegram @luz_amanha and Bluesky, PT+EN ready
- 00:10 UTC po → ready
-
T-0040 X post 08.11 14:10 UTC: wording test, EN-first card for 09.11 (plan slot) ready
- 00:10 UTC po → ready
-
T-0041 Explain on / , /d/ and llms.txt: '3 horas mais baratas' are single hours, the window is 3 hours in a row accepted
- 00:10 UTC po → ready
- 00:10 UTC dispatcher → claimed 20261104T0007-exec-T-0041
- 00:10 UTC dispatcher → in_progress started
- 00:11 UTC dispatcher → released merged 74959e05a9
- 01:10 UTC reviewer → accepted The new labels appear in PT and EN on / and /d/2026-11-01/, and llms.txt defines both cheapest_hours and cheap_window. The day JSON keeps its values (window 12–15, hours [11,13,14]), and the pages hav
-
T-0042 Offline rebuild must keep tomorrow's data: build from cached data/omie/ instead of resetting tomorrow.json to unavailable accepted
- 01:11 UTC po → ready
- 01:11 UTC dispatcher → claimed 20261104T0107-exec-T-0042
- 01:11 UTC dispatcher → in_progress started
- 01:12 UTC dispatcher → released merged 7c6066091b
- 02:09 UTC reviewer → accepted The repo deliverables match the criteria: the test file covers both the cached and the missing-cache cases, the README has the Offline rebuild section, and build.py adds only the additive `available`
-
T-0043 Analyst: Telegram @luz_amanha subscriber baseline vs /go/telegram/ clicks (G3) done
- 01:11 UTC po → ready
- 01:12 UTC dispatcher → claimed 20261104T0107-exec-T-0043
- 01:12 UTC dispatcher → in_progress started
- 01:12 UTC dispatcher → done measurement delivered
-
T-0044 Bluesky post 09.11 08:00 UTC: 'For machines' — how to read the 24 hours from /tomorrow.json (plan slot) ready
- 01:11 UTC po → ready
-
T-0045 Check 04.11 14:35 UTC: tomorrow's OMIE file is committed and the live tomorrow.json is available for 05.11 ready
- 02:09 UTC po → ready
-
T-0046 Morning post 09.11 07:00 UTC: today's cheapest hours from today.json, PT+EN ready
- 02:09 UTC po → ready
-
T-0047 Daily post 09.11 14:05 UTC: prices for 10.11 in Telegram @luz_amanha and Bluesky, PT+EN ready
- 02:09 UTC po → ready
-
T-0048 Dated day pages without the home 'tomorrow not published' status; llms.txt explains when /d/<date>/ appears accepted
- 06:15 UTC po → ready
- 06:15 UTC dispatcher → claimed 20261104T0607-exec-T-0048
- 06:15 UTC dispatcher → in_progress started
- 06:15 UTC dispatcher → released merged 5b7e0f017b
- 07:12 UTC reviewer → accepted The dated page /d/2026-11-04/ no longer shows the home status block. It keeps the 23 of 24 line, a single h1 and the AI disclosure footer, and has no JS. The home page still shows both status lines, a
-
T-0049 Archive index /d/: one summary row per day (cheap window + average, min price, hours known) released
- 06:15 UTC po → ready
- 07:14 UTC dispatcher → claimed 20261104T0707-exec-T-0049
- 07:14 UTC dispatcher → in_progress started
- 07:14 UTC dispatcher → released merged 05e7988ed5
-
T-0050 Home page: what Telegram sends and when, when tomorrow appears (Lisbon time), plain RSS label, 'grossista' kWh heading ready
- 07:13 UTC po → ready
-
T-0051 Night 00:00–06:00 average next to the cheap window on / and /d/ (PT+EN), for timer/EV users ready
- 07:13 UTC po → ready
Reviews (3)
- T-0041 pass
The new labels appear in PT and EN on / and /d/2026-11-01/, and llms.txt defines both cheapest_hours and cheap_window. The day JSON keeps its values (window 12–15, hours [11,13,14]), and the pages have one h1, the AI disclosure footer and no executable JS.
- T-0042 pass
The repo deliverables match the criteria: the test file covers both the cached and the missing-cache cases, the README has the Offline rebuild section, and build.py adds only the additive `available` field. The post-14:30 live check on 04.11 cannot be observed yet, so I record it as a limit; everything else observable passes.
- T-0048 pass
The dated page /d/2026-11-04/ no longer shows the home status block. It keeps the 23 of 24 line, a single h1 and the AI disclosure footer, and has no JS. The home page still shows both status lines, and llms.txt explains the 404 before OMIE publishes.
Posts (2)
- 07:14 UTC telegram: https://t.me/luz_amanha/4
- 07:14 UTC bluesky: https://bsky.app/profile/formachines.bsky.social/post/3mzhskht55m2y
Metrics
Spend: $5.4 · new observations: 44 (measurement 2, need_hypothesis 12, ops 1, success 22, synthetic_difficulty 5, ux_friction 1, value_gap 1) · open questions to the owner: 0
Release Radar
- 13tasks done
- 22state transitions
- 2reviews passed
- 2posts
- 0people (estimated log sources, method)
- $3.0spent
Manager's digest
Release Radar — цикл 04.11 07:07 UTC
Что произошло. Ops пересчитала метрики (решение владельца 31). Люди / engaged теперь: 02.11 — 43/10, 03.11 — 18/5, 04.11 — пока 0/0. Старые цифры (65/16 и 123 «человеческих» /go/) были завышены ботами. Это исправленный счётчик, а не падение спроса. Цели G1–G4 не меняем.
Решения.
- Поставил аналитику задачу: заново записать базу дня 1 и перечитать G1–G4 по новым числам. Иначе 10.11 смешаем старые и новые цифры.
- Добавил карточку Bluesky на 10.11 07:30: в плане её не было, а VISION обещает ежедневную карточку в двух каналах.
- Невоспроизведённые обрывки в llms.txt (OBS-0171) — скорее всего, обрезка на стороне клиента; T-0051 уже принята.
- Подозрительные /go/-клики после пересчёта больше не считаются людьми.
- Внешних referer почти нет (G3). Ждём свод на dev.to 09.11 (T-0049) и чтение 10.11.
- ИИ-краулеры читают сайт активно, но в цели не входят.
Сегодня по расписанию: карточка 04.11 в Telegram и Bluesky (T-0011). Слоты плана на 05–10.11 все уже заведены задачами.
Ждёт владельца/ops: аналитику нужна необрезанная дневная сводка метрик, иначе возвраты (G2) считать трудно.
Расход: $2.14 из $20.
Analyst's summary
Данные: видны полностью только сутки 02.11 (до пилота). Дни 03 и 04.11 в metrics обрезаны, поэтому по ним цифр нет. Пилот стартует 04.11, и дневной срез за него ещё не готов.
| Уровень | 02.11 |
|---|---|
| Краулеры (discovery) | 464 запроса, 40 источников (ClaudeBot 198, GPTBot 194) |
| Люди, источники | 65 |
| Engaged | 16 |
| Возвраты | 0 |
| Агенты | 22 запроса, 3 источника (curl 21) |
| `/today.json` | 17 запросов: свои 9, краулеры 2, агенты 2, люди 3 |
| `/go/*` у людей | 123 запроса, 3 источника |
| Referer | только google.com, 1 запрос |
| 5xx | 0 |
Своё и чужое смешано: за сутки 28 своих источников, это внутренние прогоны, а не аудитория.
Посты и визиты. Часовых данных нет, поэтому сравнить часы до и после постов нельзя. Referer от Bluesky, Telegram, Mastodon, X, Threads в таблице нет. Эффект постов не подтверждён.
Цели (чтение 10.11): все значения за 02.11, это ещё не пилот.
- G1: 16 против ≥40.
- G2: 0 против ≥5.
- G3: внешних referer-доменов нет, доля кликов не определима.
- G4: чужих запросов
/today.jsonне больше 5 (агенты 2, люди 3) против ≥5 за 7 дней.
Для оценки задач нужны данные до и после на одной метрике.
Tasks (18)
-
T-0001 Day-1 daily card: N releases in 24 h, M flagged — Bluesky done
- 00:11 UTC analyst → measured effect: insufficient_data — Единственный сигнал — 5 человеческих источников из текста задач; почасовых данных нет.
- 00:11 UTC dispatcher → done measured
-
T-0002 Show the build time and short commit hash in the footer of every page done
- 00:11 UTC analyst → measured effect: insufficient_data —
- 00:11 UTC dispatcher → done measured
-
T-0003 Add one-click feedback links on each card: useful / not useful, and a report-an-error link to a prefilled GitHub issue done
- 00:11 UTC analyst → measured effect: insufficient_data —
- 00:11 UTC dispatcher → done measured
-
T-0004 MCP server over the public JSON: releases_today, package_releases, flagged_breaking (read-only, stdio) done
- 06:16 UTC analyst → measured effect: insufficient_data —
- 06:16 UTC dispatcher → done measured
-
T-0005 Add og:title, og:description and a JSON-LD block to every page template (home, /pkg/, /legal/) done
- 00:11 UTC analyst → measured effect: insufficient_data — OG/JSON-LD принят 02.11, до/после на одной метрике нет; есть 6 запросов facebookexternalhit как превью.
- 00:11 UTC dispatcher → done measured
-
T-0008 Label pre-releases (insiders, canary, rc, beta) and always show the latest stable version with its date on /pkg/ pages done
- 06:16 UTC analyst → measured effect: insufficient_data —
- 06:16 UTC dispatcher → done measured
-
T-0010 Add an additive counts object (releases, packages, flagged) to today.json done
- 06:16 UTC analyst → measured effect: insufficient_data —
- 06:16 UTC dispatcher → done measured
-
T-0011 Daily card 04.11 (after the 06:00 UTC build, pilot day 1): 'N releases in 24 h, M flagged' in Telegram @relesae_radar and on Bluesky accepted
- 07:16 UTC dispatcher → claimed 20261104T0707-exec-T-0011
- 07:16 UTC dispatcher → in_progress started
- 07:18 UTC dispatcher → accepted posted 2 (editor-approved)
-
T-0017 MCP server conformance check: scripted stdio session against the MCP spec (initialize, tools/list, tools/call, errors) before publishing done
- 06:16 UTC analyst → measured effect: insufficient_data —
- 06:16 UTC dispatcher → done measured
-
T-0018 Make feed.xml match its llms.txt description: include all today.json releases or document the item cap done
- 06:16 UTC analyst → measured effect: insufficient_data —
- 06:16 UTC dispatcher → done measured
-
T-0047 X card 09.11 10:00 UTC: Monday daily card, fact first, link last ready
- 01:13 UTC po → ready
-
T-0048 Threads card 09.11 12:00 UTC: one human sentence + verbatim quote, no code (hour comparison vs 07.11) ready
- 01:13 UTC po → ready
-
T-0049 dev.to weekly roundup 09.11 13:00 UTC: flagged releases 03–09.11 with verbatim quotes and source links ready
- 01:13 UTC po → ready
-
T-0050 /pkg/ pages: split the 7-day count into stable vs pre-releases and say plainly when no stable release came out accepted
- 05:10 UTC po → ready
- 05:10 UTC dispatcher → claimed 20261104T0507-exec-T-0050
- 05:10 UTC dispatcher → in_progress started
- 05:10 UTC dispatcher → released merged 66b7c4c540
- 06:16 UTC reviewer → accepted The react page and its index.json show the stable/pre-release split, the no-stable line with 19.3.1 and its date, and the two integer fields, which sum to the 6 releases. Footer, build marker 66b7c4c
-
T-0051 llms.txt: one package per line and a build timestamp, regenerated on every build accepted
- 05:10 UTC po → ready
- 06:16 UTC dispatcher → claimed 20261104T0607-exec-T-0051
- 06:16 UTC dispatcher → in_progress started
- 06:16 UTC dispatcher → released merged f13061b393
- 07:15 UTC reviewer → accepted The live llms.txt has an Updated line matching build.json built, and 93 one-per-line package entries with HTML and index.json URLs that match counts.packages. It is served as text/plain with 200, and
-
T-0052 Daily card 10.11 07:30 UTC — Telegram @relesae_radar: 'N releases in 24 h, M flagged' + one verbatim quote (last pilot day) ready
- 05:10 UTC po → ready
-
T-0053 Re-record the pilot day-1 base on the recounted metrics (sources 04.11 06:21 UTC) and re-read G1–G3 done
- 07:16 UTC po → ready
- 07:18 UTC dispatcher → claimed 20261104T0707-exec-T-0053
- 07:18 UTC dispatcher → in_progress started
- 07:18 UTC dispatcher → done measurement delivered
-
T-0054 Daily card 10.11 07:30 UTC — Bluesky: 'N releases in 24 h, M flagged' (no code, last pilot day) ready
- 07:16 UTC po → ready
Reviews (2)
- T-0050 pass
The react page and its index.json show the stable/pre-release split, the no-stable line with 19.3.1 and its date, and the two integer fields, which sum to the 6 releases. Footer, build marker 66b7c4c and the existing fields are unchanged.
- T-0051 pass
The live llms.txt has an Updated line matching build.json built, and 93 one-per-line package entries with HTML and index.json URLs that match counts.packages. It is served as text/plain with 200, and last-modified is now consistent with the build.
Posts (2)
- 07:18 UTC telegram: https://t.me/relesae_radar/4
- 07:18 UTC bluesky: https://bsky.app/profile/formachines.bsky.social/post/3mzhsrg5vwz2f
Metrics
Spend: $3.0 · new observations: 23 (measurement 4, need_hypothesis 8, ops 1, success 8, synthetic_difficulty 2) · open questions to the owner: 1