You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/current-work.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,10 @@ Current implementation focus: harden the model-driven planning layer now that th
53
53
- once planner contracts, runtime handlers, and tests no longer depend on `schedule_blocks`, drop the table and its remaining migration/test scaffolding
54
54
- Expand Postgres integration coverage for ambiguous scheduling cases, clarification flows, and outbound reply loops.
55
55
- Preserve safe scheduling and rescheduling over explicit state boundaries in mutation mode.
56
+
- TODO: fix scheduler handling for explicit narrow time blocks so requests like `11:05` to `11:09` preserve the requested duration instead of defaulting to the profile focus block.
57
+
- TODO: remove `schedule_blocks` once planner/runtime contracts, repositories, migrations, and tests are fully task-first.
58
+
- TODO: fix multi-task schedule proposal generation so newly proposed inserts are considered during the same batch and Atlas cannot emit overlapping new blocks when scheduling more than one open task.
59
+
- TODO: when a user asks for an explicit time that is already in the past, clarify that the requested time has already passed instead of silently placing it in the past or rolling it forward.
"Use weekOffset=0 for Friday or this Friday, weekOffset=1 for next Friday, and weekOffset=2 for next next Friday.",
57
57
"For time-only phrases like at 3pm, leave dayReference, weekday, and weekOffset null.",
58
58
"Use explicitHour and minute for exact times.",
59
+
"When the user gives an explicit time block like '11:05 to 11:09' or 'from 2pm to 2:30pm', also set endExplicitHour and endMinute so Atlas preserves that exact duration.",
59
60
"Use preferredWindow only for broad phrases like morning, afternoon, or evening, and leave explicitHour null in those cases.",
60
61
"If the user gives a soft but usable preference like 'morning but not too early', infer a sensible time instead of asking for an exact hour. For example, 10:30am is a valid interpretation.",
61
62
"Do not ask for an exact time when the user has already given a usable broad window or delegated slot choice to Atlas.",
"today from 11:05 to 11:09 -> dayReference='today', explicitHour=11, minute=5, endExplicitHour=11, endMinute=9.",
92
94
"If context.referenceTime is Wednesday, March 18, 2026 in America/Los_Angeles, then Friday at 10am -> dayReference='weekday', weekday='friday', weekOffset=0, explicitHour=10, minute=0.",
93
95
"If context.referenceTime is Wednesday, March 18, 2026 in America/Los_Angeles, then next Friday at 10am -> dayReference='weekday', weekday='friday', weekOffset=1, explicitHour=10, minute=0.",
94
96
"If the user says 'journal is done' and the provided task context includes one journaling task alias, emit exactly one complete_task action for that existing task alias.",
0 commit comments