A milestone will be closed on GitHub only once the intents it realises are satisfied

**This is not implemented.** It is published so that a known gap is visible rather than assumed to be covered.

declared statusdeclared status: planned Specified and not implemented. Named so the omission is visible.

recorded evidencerecorded evidence: no test Not judged: only a guaranteed claim is held to a recorded run. how evidence is recorded

The GitHub projection closes a milestone from its derived plan status alone and reads no intent. Closed work the evidence contradicts is refused by the intent-realization gate, not by the tracker.

What it means

This is not implemented. It is published so that a known gap is visible rather than assumed to be covered.

The intended shape is that the GitHub projection reads the intents a milestone realises, and keeps the milestone open on GitHub while any of them is not satisfied.

scripts/github-sync projects each milestone from its derived plan status alone and reads no intent. Closed work the evidence contradicts is refused by the intent-realization gate in this repository (intent-realization-held-to-evidence), not by the tracker.

How to see it

grep -c intent scripts/github-sync   # 0

What it does not cover

It would still be a projection: GitHub would not decide satisfaction, and closing a milestone there would change nothing here.

Why it exists

A tracker that shows a milestone closed while its intent is false repeats the mistake the intent model exists to correct, one projection further out.

Detail rendered from docs/claims/intent-closes-github-milestones.md.

From the statement to the proof

1 · the public statement

A milestone will be closed on GitHub only once the intents it realises are satisfied

No feature or README responsibility names it; this page is where it is stated.
2 · the canonical claim

intent-closes-github-milestonesdeclared status: planned in docs/CLAIMS.yaml

Defined in read it on this site · docs/PLANNING.md
3 · the implementation

Nothing implements it yet.
4 · the test and the scenarios

No executable evidence linked: the claim names no test, and no use case executes it.
5 · the recorded runs

recorded evidence: no test how evidence is recorded