Skip to content

docs(evolution): fold the W40 retro's lessons into the runbook - #2006

Open
kmizu wants to merge 2 commits into
developfrom
evo/meta-w40-lessons
Open

kmizu wants to merge 2 commits into
developfrom
evo/meta-w40-lessons

Conversation

@kmizu

@kmizu kmizu commented Oct 5, 2026

Copy link
Copy Markdown
Member

What

  • §0.2: a closed Direction proposal still counts (list with state=all); Direction proposal 2026-W40 #1928 was closed by a no-op PR.
  • §1.3: an RFC whose recommended option is small comes with a draft PR (risk:high, status:needs-kota), so Kota decides on a diff.
  • §1.4 / §2.2: a verified bug gets status:ready when it is filed, whoever files it; probes are hand-written when the Workflow tool is unavailable, and read the Java source before calling a failure a bug.
  • §1.5: before probing, look for a verified bug or user-filed friction that only lacks the label.
  • §2.4: issues from a person using Onion for real work get source:user (README label list) and come right after P0/kota:look.
  • §2.5: the PR-share metric is one REST call, given verbatim and tested (merged=94 closes_issue=21 samples=27 on 2026-10-05).
  • §3.1: the Strategist checks the routines' prompts first.
  • Known pitfalls: GitHub from a cloud session is REST only (gh issue list, search and --paginate fail); sbt is at /root/.local/sbt-launcher/bin; memory pushes go to HEAD:main.

Why

Retro #2001: 24 of the first 41 runs changed nothing while verified bugs sat unlabelled, the Sensor never computed its metrics or budgets ("no sbt"), five RFCs waited while Kota merged every diff within a day, and the memory repo's main held 6 of 41 episodes because cloud pushes went to claude/* branches.

Notes for reviewers

  • risk:high because it is docs/evolution/ (meta). Nothing here changes the code.
  • The hourly routine's prompt is not fixable from a PR; it is item 1 of Direction proposal Direction proposal 2026-W41 #2005.
  • From a newcomer's view: a person who files an Onion issue now has a named place in the loop (source:user) and a promised first response within 24 hours.

Verification

  • docs/evolution/ only; no tests apply. The metric command was run from the edited file and produced the numbers above.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JSY1QesTFGgm4d9eSPM58C


Generated by Claude Code

Onion Evolution Loop and others added 2 commits October 5, 2026 00:21
What:
- a closed Direction proposal still counts; list proposals with state=all
- RFC + draft PR when the recommended option is small; Kota decides on diffs
- verified bugs get status:ready at filing, whoever files them
- user-filed friction gets source:user and comes right after P0/kota:look
- probes: hand-written when the Workflow tool is unavailable; read the Java
  source before calling a failure a bug
- the Sensor's PR-share metric is one REST call, given verbatim
- the Strategist checks the routines' prompts first
- Known pitfalls: cloud GitHub is REST only, sbt's path, memory pushes go
  to HEAD:main (35 episodes were stranded on claude/* branches)

Why: retro #2001. 24 of the first 41 runs changed nothing while verified
bugs sat unlabelled, the Sensor never computed its metrics, and the memory
repo's main held 6 of 41 episodes.

Co-Authored-By: Onion Evolution Loop <evolution-loop@onion-lang.org>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JSY1QesTFGgm4d9eSPM58C
Co-Authored-By: Onion Evolution Loop <evolution-loop@onion-lang.org>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JSY1QesTFGgm4d9eSPM58C
@kmizu kmizu added meta Changes to the evolution loop itself risk:high Needs Kota's approval before merge status:needs-kota Waiting for Kota labels Oct 5, 2026 — with Claude

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

meta Changes to the evolution loop itself risk:high Needs Kota's approval before merge status:needs-kota Waiting for Kota

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant