Created
Jul 04, 01:37
Started
Jul 04, 01:37
Completed
Jul 04, 04:58
DevOps handoff
Type
Chore
Shape
ui-only
Worktree Slug
rename-propagate-insights-act
Repositories
mcritchie-studio
Release Slug
—
Branch
feat/rename-propagate-insights-act
Acceptance Criteria
Expected Test Plan
Checks Run
Agent Context
Birds-eye of the learning loop decided scope. The loop: (1) CAPTURE — bin/atomic-event spans + bin/atomic-capture-hook PostToolUse actions POST to the board (AtomicEvent/AtomicAction). (2) GRADE — Alex Heartbeat grade-events: bin/atomic-event awaiting/grade, good|not + slug, --bank/--discard (ActionGrade, grader=alex). (3) BANK — ActionGrade.banked IS the Insight Bank (canonical store). (4) CONFIRM — Mr. McRitchie confirms on /alex/pipeline column 3 (grader=mcr audit rows). (5) GENERATE — Insights::DocGenerator / bin/rails insights:doc renders the bank into docs/agents/shared/insights.md (derived artifact). (6) SHARE/DISTRIBUTE — this act (was propagate-insights): regenerate doc + distribute to runtimes. (7) FEED-FORWARD — bin/session-insights SessionStart hook GETs /api/v1/insights and injects lessons into fresh sessions. VERDICT: propagate->share is a pure relabel — the act's mechanics (regenerate + distribute) are unchanged; 'share' names the audience (every next agent) rather than the write direction, which matches where the loop is heading (the session feed), so shape stays ui-only. IN SCOPE besides the rename: fix launcher-mapping drift — PR #347 added the act to the card + heartbeats.md but never to devops-cycle-design.md section 1.4 or qa-release SKILL.md (heartbeats.md's own rule: 1.4 wins, fix others in the same pass). OUT OF SCOPE (real mechanics gaps, follow-ups): SessionStart hook for bin/session-insights not wired in settings.json (loop still WRITE-ONLY at the output seam); bin/install-agent-docs has no insights.md manifest entry so 'distribute' is aspirational; heartbeats.md says doc regen is 'scoped to the confirmed set' but DocGenerator reads ALL banked (no mcr scoping); prod bank currently holds 0 insights so nothing has flowed end-to-end yet.
Stage Timeline
Who handled each stage, the time it took (measured), and the model / tokens / cost reported (best-effort) — plus who's on it right now. — means the agent didn't report that metric.
Conversation
QA review feedback, agent handoffs, and follow-up notes for this task.
No task feedback has been recorded yet.
Sealed-bid sizing
Edit →Alex (PM)
—
Avi (PO)
—
Dev
SMALL
Actual
LARGE
We emailed a one-tap sign-in link to . It expires shortly and can only be used once.
No email? Check spam, or close this and try again.