Gate: rule-fulfilled

Each rule of this spec is marked in the code by a comment carrying its code (// ABCDX-B01: …).

Property	Value
Judgment	an AI or a person answers the question below, through anchors judge
Confronts	spec
Blocking by default — new project	yes
Blocking by default — existing project	no — informs
Review	its targets are marked to review (anchors review)

The question

Each rule of this spec is marked in the code by a comment carrying its code (// ABCDX-B01: …). Read the rule and the snippet it marks and answer: does the snippet DO what the rule describes? Fail it when the comment sits on code that does something else, when the rule describes a case the snippet does not handle, or when the mark is in a generic place (top of the file, an import) instead of the snippet that decides. The question is about what the code RUNS, not about what the comment claims. When failing it, PROPOSE the fix as a patch. BEFORE ANSWERING, check whether this unit declares @TBD for the piece this question asks about (@TBD: code, @TBD: code,test, …). If it does, the code does NOT exist yet by a recorded decision, and there is nothing to confront: answer waived, naming the absence (“the spec declares @TBD for this piece and it does not exist in the repository”). Do NOT answer pass — pass is a statement ABOUT the code, and without the code it states what nobody verified; the stamp stays in the map looking like real verification. Also check that the @TBD is TRUE: if the piece already exists in the repository, the marker is stale, the judgment is due as usual, and the stale declaration is a finding — while it stays there, every gate that reads it waives what it should demand.

Declaring it

gates:
  - name: rule-fulfilled
    on: [spec]
    measures: judgment