christian/commitea
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Deterministic scheduler (topo order -> dated plan) #9

New Issue
Closed
opened 2026-07-08 15:15:09 +00:00 by christian · 1 comment
christian commented 2026-07-08 15:15:09 +00:00
Owner
Copy Link

Order open issues by dep topo-sort + priority + estimate, consume capacity, emit per-issue start/finish. LLM does no math. Cycle detection on the dep graph.

Acceptance: a small dep graph w/ two contributors yields deterministic start/finish; a cycle is reported, not looped.

P2 keystone / schedule risk (only est/5d in P2). If it slips, split topo-sort+capacity-consumption from date-emission. Gitea native issue deps confirmed available (1.24.3).

Order open issues by dep topo-sort + priority + estimate, consume capacity, emit per-issue start/finish. LLM does no math. Cycle detection on the dep graph. **Acceptance:** a small dep graph w/ two contributors yields deterministic start/finish; a cycle is reported, not looped. **P2 keystone / schedule risk** (only est/5d in P2). If it slips, split topo-sort+capacity-consumption from date-emission. Gitea native issue deps confirmed available (1.24.3).
christian added this to the P2 — Scheduler + Monte Carlo milestone 2026-07-08 15:15:09 +00:00
christian added the
est
5d
p
1
 labels 2026-07-08 15:15:09 +00:00
christian added a new dependency 2026-07-08 15:15:42 +00:00
#8 Capacity model from members.yaml
christian added a new dependency 2026-07-08 15:15:42 +00:00
#5 Lifecycle inference from the issue timeline
christian added a new dependency 2026-07-08 15:15:43 +00:00
#10 Monte Carlo milestone cones (p10/p50/p80)
christian added a new dependency 2026-07-08 15:15:43 +00:00
#12 Directive log append + consequence diff
christian added a new dependency 2026-07-08 15:15:43 +00:00
#13 Focus selection (Now/Next/Later + critical path)
christian commented 2026-07-09 05:21:04 +00:00
Author
Owner
Copy Link

Shipped — deterministic scheduler (topo + critical path -> dated plan), capacity-aware.

Shipped — deterministic scheduler (topo + critical path -> dated plan), capacity-aware.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deadline
hard
CommiTea: milestone has a hard deadline
est
1d
CommiTea estimate: 1 ideal-day(s)
est
2d
CommiTea estimate: 2 ideal-day(s)
est
3d
CommiTea estimate: 3 ideal-day(s)
est
5d
CommiTea estimate: 5 ideal-day(s)
est
8d
CommiTea estimate: 8 ideal-day(s)
p
1
CommiTea priority 1 (1 = most urgent)
p
2
CommiTea priority 2 (1 = most urgent)
p
3
CommiTea priority 3 (1 = most urgent)
p
4
CommiTea priority 4 (1 = most urgent)
No Label
est
5d
p
1
Milestone
No items
No Milestone P2 — Scheduler + Monte Carlo
Projects
Clear projects
No project
Assignees
Clear assignees
christian
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#10 Monte Carlo milestone cones (p10/p50/p80)
christian/commitea
#12 Directive log append + consequence diff
christian/commitea
#13 Focus selection (Now/Next/Later + critical path)
christian/commitea
Depends on
#5 Lifecycle inference from the issue timeline
christian/commitea
#8 Capacity model from members.yaml
christian/commitea
Reference: christian/commitea#9
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?