From cfa4328ddb8d31c1ad471d105883cc9c689ea0f6 Mon Sep 17 00:00:00 2001 From: Nessar Date: Mon, 19 Oct 2026 00:26:31 +0200 Subject: [PATCH] docs(context): define planning stage and indicative wait 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 --- CONTEXT.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CONTEXT.md b/CONTEXT.md index 953db94..b5e30df 100644 --- a/CONTEXT.md +++ b/CONTEXT.md @@ -157,6 +157,14 @@ A deterministic explanation derived from the final displayed plan. It identifies **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. +**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**: 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.