Replanning is bounded, idempotent and never weakens its intent

majordomus://adr/adr-0192proposed idd-planchatgpt-project

it references

put_in_force adr-0053
put_in_force adr-0191
put_in_force I3246
put_in_force I3247
put_in_force I3248
put_in_force I3249
put_in_force I3250
put_in_force what-idd-is-not (knowledge)
put_in_force .ai/repo/policy.yaml
put_in_force project.every-wait-is-bounded@2

referenced by

Nothing in the layer names it. Backlinks are derived, so an empty list is an answer rather than an omission.

192. Replanning is bounded, idempotent and never weakens its intent

Context

Re-evaluating an intent must not file a new issue each time, loop forever, or quietly lower the bar (2026-10-08, 10-11, 10-16).

A drafted work item's identity is derived from (intent, criterion, gap kind); a replan reuses done work and supersedes through existing transitions; a policy-declared budget of drafts without a newly satisfied criterion ends in human_needed; a draft narrowing a criterion is refused without a recorded decision.

Alternatives rejected

Work until satisfied
An LLM noticing the same gap and filing a new issue
Rewriting history on replan

Consequences

One budget field in policy.yaml; no runtime or scheduler; /proceed (ADR 0177 (on an unlanded branch)) inherits the bound.

Sources

Promoted on 2026-10-18 from the owner's ChatGPT project (workspace chatgpt-majordomus, issue I3100). The owner has not accepted it; it is proposed for the owner's decision.

chatgpt-majordomus:c196#3
chatgpt-majordomus:c196#6
chatgpt-majordomus:c205#2
chatgpt-majordomus:c221#2
chatgpt-majordomus:c270#8

Where this comes from

canonical file: .ai/repo/adrs/0192-replanning-is-bounded-idempotent-and-never-weakens-its-intent.md
identity: adr-0192
also served as: MCP resource majordomus://adr/adr-0192 · majordomus entity show adr/adr-0192 · GET /api/v1/entity?uri=majordomus://adr/adr-0192
in the Cockpit: /cockpit/objects/adr/adr-0192

This page is generated from the file above by scripts/generate-site-data; editing the page changes nothing, editing the file changes every surface. The relations above are edges of docs/generated/graph.json, which the executable writes from the same index.