Say manifest validator, not judge: the glossary gains the word and retires the noun #516

2026-11-04T22:38:04Z

mesh-tools commented

2026-11-04 22:38:04 +00:00

The operator, 2026-11-04 23:1x-23:2x, asked "what is a judge?". Given the answer (the indexer's rules that refuse or hold a manifest), they said: "so it's a manifest validator? why would you need a new term for it?". They then declined ADR 0633 because it still said "judge". hq's words test could not refuse the word, because it was never in the glossary, neither as an entry nor on a Not: line.

This change:

Glossary, Delivery domain: manifest validator. The indexer's rules that judge each manifest before anything of it reaches a node: refuse it, set it aside to wait, or accept it, with an accepted manifest's later problems kept as warnings. Its verdict is the indexer's state, and every other part takes it. There is one copy, the indexer's, which the merge check also runs from the trunk in its sandbox. Cites ADR 0578 §1-§4, ADR 0579 §1-§2, ADR 0593 §1 and ADR 0601 §3.
Its Not: line (hq) retires the noun: "the judge", "its judge", "the trunk's judge" and the like. The words test matches a struck form whole, so the verb ("to judge", "judged", "judgement") stays allowed.
About 60 uses changed in designs 20, 25, 26, 32, 45, 47, 48, 51 and 55, playbook 07, the glossary, mesh-preparer and review-security-and-upgrade. Where "judge" named another concept, that concept's existing word is used, and no new term is coined:
- the program built from a change's code (design 47) is a "composing program built from a change";
- one health check is a probe;
- claude-code's judgement tool is named with the glossary's judgement.
Issues 286, 306, 310, 343, 361 and 364 keep their words as history, each with a row in words-allowed until 2027-04-30.

go test ./... at the root: pass. Written by writer-validator@shanks (hq-design-writer definition); review: two rounds (the first found design 47's composing program miswritten as the assigner's composition check).

Reviewed-by: review-validator@shanks at f91a5a7c75
Pushed-by: fix-1965@shanks

https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

The operator, 2026-11-04 23:1x-23:2x, asked "what is a judge?". Given the answer (the indexer's rules that refuse or hold a manifest), they said: "so it's a manifest validator? why would you need a new term for it?". They then declined ADR 0633 because it still said "judge". hq's words test could not refuse the word, because it was never in the glossary, neither as an entry nor on a *Not:* line. This change: - **Glossary, Delivery domain: manifest validator.** The indexer's rules that judge each manifest before anything of it reaches a node: refuse it, set it aside to wait, or accept it, with an accepted manifest's later problems kept as warnings. Its verdict is the indexer's state, and every other part takes it. There is one copy, the indexer's, which the merge check also runs from the trunk in its sandbox. Cites ADR 0578 §1-§4, ADR 0579 §1-§2, ADR 0593 §1 and ADR 0601 §3. - **Its *Not:* line (hq) retires the noun:** "the judge", "its judge", "the trunk's judge" and the like. The words test matches a struck form whole, so the verb ("to judge", "judged", "judgement") stays allowed. - **About 60 uses changed** in designs 20, 25, 26, 32, 45, 47, 48, 51 and 55, playbook 07, the glossary, mesh-preparer and review-security-and-upgrade. Where "judge" named another concept, that concept's existing word is used, and no new term is coined: - the program built from a change's code (design 47) is a "composing program built from a change"; - one health check is a **probe**; - claude-code's judgement tool is named with the glossary's **judgement**. - **Issues 286, 306, 310, 343, 361 and 364** keep their words as history, each with a row in words-allowed until 2027-04-30. `go test ./...` at the root: pass. Written by writer-validator@shanks (hq-design-writer definition); review: two rounds (the first found design 47's composing program miswritten as the assigner's composition check). Reviewed-by: review-validator@shanks at f91a5a7c75e5f29374e99232c501bf3859f24868 Pushed-by: fix-1965@shanks https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

mesh-tools added 2 commits 2026-11-04 22:38:04 +00:00

Say manifest validator, not judge: the operator asked why a new word was needed for the indexer's rules aac8494ca3

The glossary gets the entry in the Delivery domain with the records that decide it, and retires the noun in
hq's prose on a Not line; the verb stays. Where "judge" named something else, the design now uses that
thing's word: the node-engine's look at health, an account or the network; the composition check built from
a change; the claude-code module's judgement tool. Five issue narratives keep the word of their day.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

Name the composing program built from a change, a probe for one health check, and ADR 0579 §2's whole case (review 1)

mesh/delivery merged: source.main moved to novox/hq@6b8b6b08e39a

Details

mesh/check being carried to f91a5a7c75e5 on 6b8b6b08e39a | from f0c05d1edb84

f91a5a7c75

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

mesh-tools commented

2026-11-04 22:38:08 +00:00

Delivery novox/hq@f91a5a7c75e5 — merged since 2026-11-04T22:39:54Z

Source — source.main moved to novox/hq@6b8b6b08e3. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Transitions

2026-11-04 22:38 (new) → proposed (announced): novox/hq#516's head announced
2026-11-04 22:38 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-04 22:39 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/hq@f91a5a7c75e5` — **merged** since 2026-11-04T22:39:54Z **Source** — source.main moved to novox/hq@6b8b6b08e39a. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-04 22:38 (new) → proposed (announced): novox/hq#516's head announced - 2026-11-04 22:38 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-11-04 22:39 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit 6b8b6b08e3 into main

2026-11-04 22:39:52 +00:00

mesh-tools deleted branch docs/manifest-validator

2026-11-04 22:39:52 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#516