Menu ▾ ▴

#23 Roadmap: give the company an outcome and a number, not a backlog

closed
nobody
roadmap (15)
2026-10-25
2026-07-11
Anonymous
No

Originally created by: lodar

5dive goal add decomposes an outcome into tasks once. Next: a standing goal with a measurable target that the planner keeps steering toward, originating and reprioritizing work as results land, and reporting progress against the number in the daily digest. The company keeps its own backlog full.

Related

Tickets: #1405

Discussion

  • Anonymous

    Anonymous - 2026-07-11

    Originally posted by: lodar

    Design settled (2026-07-11). The shape: a standing objective binds a goal to a read-only metric command (stdout, one number) plus a target. A recurring planner tick re-plans diff-based against the reading: originate up to a per-cycle cap through the existing goal-materialize guardrails, reprioritize, or retire its own originated tasks. The digest reports raw metric progress; public objectives ride the proof publisher unchanged.

    Anti-Goodhart invariants: the planner never owns or runs the metric source; progress counts only verifier-accepted closes plus the metric itself; auto-cleared gates and self-graded work never feed the story; the tier-2 category floor applies to originated tasks.

    Staged behind the [#22] trust substrate: phase A is measurement plus human-checkpointed planning cycles (one decision gate per origination batch), phase B widens the no-gate envelope by earned autonomy level with hard per-objective budgets (#16, [#17]). First dogfood objective: the zero-human ratio in the README badge, so the company steers toward its own public number.

     

    Related

    Tickets: #17
    Tickets: #22

  • Anonymous

    Anonymous - 2026-07-19

    Originally posted by: lodar

    Progress: the outcome-loop engine shipped in v0.10. A standing objective binds a goal to a read-only metric command (stdout, one number) plus a target; 5dive objective replan re-plans diff-based against the latest reading (originate up to a per-cycle cap through the existing goal-materialize guardrails, reprioritize, or retire its own originated tasks), objective status renders progress against the number, the daily digest carries an objectives block (current vs target with a window trend), and 5dive company stands the whole thing up in one step.

    Remaining for this issue: a roadmap-level generator that mints fresh candidates for review when the actionable backlog drains and no active objective covers the space, so the whole company keeps its backlog full and not just a single objective's. That layer is in design/build now.

     
  • Anonymous

    Anonymous - 2026-10-25

    Originally posted by: 5dive-bot

    Shipped in v0.10 as 5dive objective: give the team a target number and it keeps re-planning toward it, with progress in the daily summary.

     
  • Anonymous

    Anonymous - 2026-10-25

    Ticket changed by: 5dive-bot

    • status: open --> closed
     

Log in to post a comment.