@@ -35,7 +35,7 @@ Clause-②: yes (narrowing)
 - **The D3 entry `ui-visibility-alias-keys-retired`**, one for both keys.
 - **No deprecation window**, per the project's startup-stage posture.
 
-`@objectstack/lint`: the visibility-predicate rules (`visibility-root-mislayered`, `visibility-bare-identifier`, `visibility-predicate-syntax`) and the predicate-path rules read `visibleWhen` only. Every door runs them on a body the spec parse accepted, which cannot carry either retired key.
+`@objectstack/lint`: the visibility-predicate rules (`visibility-root-mislayered`, `visibility-bare-identifier`, `visibility-predicate-syntax`) and the predicate-path rules read `visibleWhen` only. `os validate`, `os build`, `os verify`, `defineStack` and the metadata save door parse first and refuse either retired key by name, so a body they judge cannot carry one. `os lint` is the one door that hands these rules an unparsed stack: there a predicate written under a retired key is not judged, by design — the parsing doors refuse the key itself, and `os lint` reports no refused shape.
 
 `@objectstack/metadata-core`: `detectUnboundFormViewPredicateRoots` reads `visibleWhen` only. Its caller scans an artifact after `applyArtifactForwardConversions`, which renames a legacy `visibleOn` first.
 
 
@@ -234,9 +234,14 @@ describe('premise 3 (FALSE): "the `visibleOn` alias survives until the parse"',
   //   * the authoring funnel no longer renames the key — `normalizeStackInput`
   //     passes it through, so a rule fed this tier would see it;
   //   * no rule reads it either way — the family reads `visibleWhen` only;
-  //   * the author is not silent — `defineStack` (and the parse every door
-  //     runs before its rule pass) refuses the key by name with the rename.
-  //     That refusal IS the recorded guard for this surface now.
+  //   * the author is not silent — the doors that parse first (`defineStack`,
+  //     `os validate`, `os build`, `os verify`, the metadata save door) refuse
+  //     the key by name with the rename. That refusal IS the recorded guard for
+  //     this surface now;
+  //   * `os lint` is the one door that hands the rules an UNPARSED stack
+  //     (`runAuthoringRules('lint', …)` over the normalized tier). There a
+  //     predicate under a retired key is nobody's verdict, by design — pinned
+  //     below as that door's reading, beside a canonical control.
   /** The three alias sites, each carrying `predicate` under its RETIRED key. */
   const aliasSitesWith = (predicate: string): Array<[string, AnyRec]> => [
     ['views[].form.sections[]', {
@@ -275,7 +280,7 @@ describe('premise 3 (FALSE): "the `visibleOn` alias survives until the parse"',
       // The key passes through: the D2 conversion is retired from the load path.
       expect(JSON.stringify(normalized)).toMatch(/"visibleOn"|"visibility"/);
       // A VALUE defect under it is nobody's verdict here, raw or normalized —
-      // the parse refuses the key before any rule runs (next case).
+      // the parsing doors refuse the key itself (next case).
       expect(validateVisibilityPredicates(structuredClone(stack))).toEqual([]);
       expect(validateVisibilityPredicates(normalized)).toEqual([]);
     },
@@ -295,6 +300,23 @@ describe('premise 3 (FALSE): "the `visibleOn` alias survives until the parse"',
     },
   );
 
+  it.each(aliasSitesBadValue)(
+    '%s: `os lint`\'s reading — the unparsed stack it hands the registry leaves a retired key\'s predicate unjudged, by design',
+    (_site, stack) => {
+      // What `os lint` runs (`commands/lint.ts`): the `'lint'` registry door over
+      // the NORMALIZED stack, never parsed. The retired key reaches it unrenamed
+      // and no visibility rule reads it.
+      const visibilityRules = (s: AnyRec) => runAuthoringRules('lint', { normalized: normalizeStackInput(structuredClone(s)) as AnyRec })
+        .filter((f) => f.rule.startsWith('visibility-'))
+        .map((f) => f.rule);
+      expect(visibilityRules(stack)).toEqual([]);
+      // CONTROL — the same predicate under the canonical key is the finding at
+      // the same door, so the empty reading above is the posture, not a dead rule.
+      const canonical = JSON.parse(JSON.stringify(stack).replace(/"(visibleOn|visibility)":/g, '"visibleWhen":')) as AnyRec;
+      expect(visibilityRules(canonical)).toEqual(['visibility-bare-identifier']);
+    },
+  );
+
   it('the predicate-VALUE rules in the same file are unaffected — do not connect them', () => {
     // The value moves into `visibleWhen` intact, so these still report on the
     // tier. #6318 was about the alias-KEY rule only, and this is the pin that
 
@@ -301,9 +301,9 @@ type AnyRec = Record<string, unknown>;
 /**
  * The predicate keys a form field / section can carry (ADR-0089): `visibleWhen`
  * alone. The view-side `visibleOn` retired at 18 as a spec tombstone (#23543
- * F4), and every door that runs this rule hands it a body the spec parse
- * accepted — the reason `validate-visibility-predicates.ts` states at its own
- * `CANONICAL` — so no input carries it.
+ * F4). The doors that parse first refuse it by name; `os lint`, which hands
+ * this rule an unparsed stack, leaves a predicate under it unjudged by design —
+ * the posture `validate-visibility-predicates.ts` states at its own `CANONICAL`.
  */
 const PREDICATE_KEYS = ['visibleWhen'] as const;
 
 
@@ -69,11 +69,12 @@ describe('validateVisibilityPredicates (ADR-0089 D3b)', () => {
   //
   // #6318 retired the alias-KEY rule and kept an alias-VALUE read
   // (`visibleWhen ?? visibleOn ?? visibility`) for raw callers. Both aliases
-  // retired at 18 as spec tombstones, and every door that runs this rule hands
-  // it a body the spec parse accepted, which cannot carry either key (the
-  // measurement is in `CANONICAL`'s docblock). So the limbs went too: a defect
-  // written under a retired key produces no finding HERE — the parse refuses
-  // the key by name one layer earlier. Each row pairs the alias spelling with
+  // retired at 18 as spec tombstones, and the doors that parse first (`os
+  // validate`, `os build`, `os verify`, `defineStack`, the metadata save door)
+  // refuse either key by name. So the limbs went too: a defect written under a
+  // retired key produces no finding HERE. At `os lint`, the one door that hands
+  // this rule an unparsed stack, that is the reading by design (`CANONICAL`'s
+  // docblock; pinned as that door's reading in `authoring-rule-input-tier.test.ts`). Each row pairs the alias spelling with
   // the same value under `visibleWhen`, which must still report, so an empty
   // alias reading cannot pass by the rule having stopped working.
   describe('the retired alias keys are not read (#23543 F4)', () => {
 
@@ -548,14 +548,16 @@ type AnyRec = Record<string, unknown>;
  *
  * `checkElement` used to read `visibleWhen ?? visibleOn ?? visibility`, for a
  * caller handing this export a raw authored object. Both aliases retired at 18
- * as spec tombstones, and every door that runs this rule hands it a body the
- * spec parse ACCEPTED: the three CLI commands run the rule stage only after
- * `ObjectStackDefinitionSchema` passes (`judgeAuthorTimeRules`), per-package
- * bodies come from that parsed stack, and the metadata save door parses the
- * `view` body (a 422 on refusal) before its runtime rule pass. An accepted body
- * cannot carry either key, so the limbs could only ever judge the value of a key
- * the spec already refuses — the consumer-side alias tolerance the retirement
- * ends.
+ * as spec tombstones. The doors that PARSE first — `os validate`, `os build`,
+ * `os verify` (`judgeAuthorTimeRules`), `defineStack`, and the metadata save
+ * door, which parses the `view` body (a 422 on refusal) before its runtime rule
+ * pass — refuse either key by name, so a body they hand this rule cannot carry
+ * one. `os lint` is the one door that hands this rule an UNPARSED stack (its
+ * `'lint'` run reads the normalized stack on both tiers): there a predicate
+ * written under a retired key is nobody's verdict, by design — the parsing
+ * doors refuse the key itself, and `os lint` reports no refused shape. Reading
+ * the limbs would only judge the value of a key the spec refuses — the
+ * consumer-side alias tolerance the retirement ends.
  */
 const CANONICAL = 'visibleWhen';
 
 
@@ -294,7 +294,7 @@ describe('the two `visibleWhen` shapes the first sweep never enumerated', () =>
     // The judgment call: `visibility` / `visibleOn` are the ADR-0089 spellings
     // this surface's own docblock says are deliberately NOT folded in (the
     // key is new; there is no legacy convention to carry forward here, unlike
-    // the view/page shapes that fold them via `normalizeVisibleWhen`). That
+    // the view/page shapes that folded them until both retired at 18). That
     // sentence is about ACCEPTANCE and an alias row does not disturb it — both
     // stay rejected below. But an author who used the ADR-0089 spelling
     // correctly on a page component or view form and reaches for the same