Public: anyone can read this; the crew can change it.

Home feed you can catch up from in 15 seconds: a "since you were here" digest, honest counts, no dead buttons; validated by a cold-read agent each iteration #5735

Closed opened this has it

Pull #5736 was closed

opened this

Owner, 2026-10-25: "it's still kinda hard for me to catch up with what was done… the widgets and graphs are nice… but when I scroll down the 'what you asked for' is just not helpful, and the pull requests/decisions, crew words, releases, and the agents buttons do nothing. This was supposed to be like an X feed… iterate heavily, and the validation should be sending an agent with no context to read the feed, then produce a summary in its own words. That must align and get closer over time while also getting more concise and direct. Measure the real time it takes to produce, so that we can target fast comprehension."

The method (the steward runs it and logs every result here):

  1. Fetch / as the owner and convert it to text: what the eye sees, with scripts and styles stripped.
  2. A fresh agent with no context reads only that text and answers, in at most 150 words: what got done, what needs me and what I'd do about it, what's worrying, and its confidence.
  3. Score it against ground truth (trunk commits, landed pulls, arm activity, items waiting on the owner, spend and ceilings) on three numbers: coverage of the 5 things that truly mattered, errors (claims the page made wrong), and seconds to produce.
  4. Repeat after every feed change. The target: coverage ≥ 4 of 5, 0 errors, under 15 s, and falling words.

Baseline, 2026-10-25 17:30Z: 21.8 s, confidence medium, 7,333 characters of page text.

  • Coverage, about 1.5 of 5. It got the release and the change rate. It missed:
    • The arm crew stalled: 1 commit since 10-22.
    • The owner's approvals: 4 green arm pulls are waiting on them (#491/#502/#503/#504).
    • Why the builders sat idle.
    • The steward's open asks.
  • Errors:
    • The ceiling: "Crew spend today $601 no ceiling". The forge ceiling is $600, so the page hides why the builders are idle.
    • The waiting count: "5 waiting on you" lists only 3.
  • Noise: 4-month-old stuck pulls are listed as if they were urgent.
  • Dead controls: the "pull requests/decisions, crew words, releases, agents" buttons do nothing.

Done when (iterate; this issue stays open as the loop):

  • The top of the feed is a 3-line "Since you were here" digest, written from events (landed, released, failed, decided), grouped by repo, with the biggest change first. Each line links to its evidence.
  • The waiting count matches the list. Every item says what to do in one button (Approve, Re-run, Close). Items older than 30 days collapse into "N stale, archive?".
  • Every chip either filters the feed or is removed. No dead buttons. Add a test that clicks each one.
  • Spend shows the real ceiling and the reason builders are idle ("ceiling reached at 14:20").
  • Each iteration posts its eval numbers as a comment here.
commented

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.

commented

Split. The crew tried this three times as one pull (#5736) and each review found a different part unproven. Each part is now one builder run under P1 Feed:

  • #5797: the digest
  • #5798: the real forge ceiling, the same on the web and the terminal
  • #5799: why builders are idle
  • #5800: the waiting count matches /review, and stale asks fold
  • #5801: every chip filters or is gone
  • #5802: /asked says what became of each ask
  • #5803: the digest on the terminal and MCP (after #5797)
  • #5804: since your last visit, not a fixed 24 h (after #5797)
  • #5805: the deterministic half of the eval loop (after #5765)
  • #5806: home under 300 ms warm

#5741 already covers one button per waiting item. The cold-read agent run and posting its numbers stay with the steward. docs/HOME-EVAL.md (#5805) keeps the table of results.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs