nessar/vac-optimizer
1
0 Fork 0
Code Issues 5 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

docs(context): define planning stage and indicative wait

Browse Source 
Both terms are user-visible in the calculation overlay that #300
revises: the stage line names the planning stage, and the remaining
time comes from the indicative wait.

Refs #300.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
nessarandClaude Opus 5.5 committed 2026-10-19 00:26:31 +02:00
1 parent 7fc3457b63
commit cfa4328ddb
1 file changed
+8
Download Patch File Download Diff File Expand all files Collapse all files
CONTEXT.md
+8
View File
@@ -157,6 +157,14 @@ A deterministic explanation derived from the final displayed plan. It identifies
**Incomplete calculation**: **Incomplete calculation**:
A calculation stopped by user cancellation or another interruption before it completed the planning objective order. On user cancellation it exposes its best available valid plan as partial, if one exists, and never implies that the obligations conflict. A calculation stopped by user cancellation or another interruption before it completed the planning objective order. On user cancellation it exposes its best available valid plan as partial, if one exists, and never implies that the obligations conflict.
**Planning stage**:
One reported step of a calculation: preparation, validation, obligations, one stage per active preference rule in rule order, expiry, then dates. Stages describe what the calculation is doing, not how far it has progressed.
_Avoid_: phase, quality stage
**Indicative wait**:
The estimated duration of a calculation, shown as a range before Calculate and as an approximate remaining time during it. It is a rough guide refined by the device's own completed calculations, never a deadline.
_Avoid_: ETA, timeout, deadline
**Planning objective order**: **Planning objective order**:
The lexicographic quality order applied after joint obligation feasibility, with active preference rules, including optimization rules, sharing the user-defined rule priority. A lower criterion never degrades a higher one. The lexicographic quality order applied after joint obligation feasibility, with active preference rules, including optimization rules, sharing the user-defined rule priority. A lower criterion never degrades a higher one.