Roadmap: the service-family row instructed retiring evidence, which 4b(4) forbids

[gunbai-bot]

Repairs two rows landed in #11853, on a reading from the side-chat ruling that I verified against source before acting on it.

The defect

self-host-service-family-on-literal-terminal's first_slice told the worker to "retire the name-usability claim as a climb rather than a loss". DESIGN §4b(4) forbids that: a climb deletes the lower-rung production machinery it obsoletes, and the discriminating RED and positive control remain enrolled.

The prepared branch session/calm-eagle-42-service-on-literal acted on the instruction. Its annotation claims the RED "is no longer authorable even against a hostile fixture". That is false, and §4b decides it the other way in as many words — a state unrepresentable in the accepted corpus may still be representable as source handed to the compiler by a fixture. The retired claim's fixture is exactly that, and it is still sitting on the sibling branch:

data keyword_as_name_source: String =
  "module m\nfn f(from: Int, input: Int) -> Int { let transport = from\n transport + input }\n"

Deleting the twelve keyword lex rules removes the mechanism that could break name usability today. It is not evidence that a later lexer or grammar change cannot introduce one — which is the whole point of keeping the control.

Also repaired

• red_control now requires each named parse-door refusal to assert its own typed diagnostic and the stage that raised it. Verified in source: the branch's refuses is literally !parses, and parse_src folds a tokenize rejection and a parse rejection into one Rejected — so a refusal claim can pass for a reason the claim is not about.
• whole-service-witness-costs-more-than-its-budget led with re-measurement. Its first slice is now to establish the witness's unique obligation first: sibling claims in the same module already execute the real tokenizer and parser on source, so this is not the only execution of the service parse path in general — only of this particular composition of constructs. Different subjects.
• That row now refuses two arguments in advance: that the specimen is "real" and therefore cannot shrink (an exemption from the one-interface rule, not an application of it), and that linear cost is therefore justified (linear work can still be work no admitted consumer demands).

What this does not change

The architectural direction stands: the literal-terminal implementation supersedes #11622's keyword-token one. This corrects the instructions that ride with it.

ROADMAP.md is regenerated via generated_artifact_gate main_wet; both rows are hidden under the current focus, so the projection's bytes do not move.

🤖 Generated with Claude Code