Iterative Refinement Is The Default Mode

A 2026-07-23 surfacing pass over the same four in-scope reflections ran under an explicit external output policy — hard ≥3-distinct-reflection threshold, wikilink evidence citations, slug-format constraints, and a search-before-create discipline that the prior passes had applied as internal heuristics rather than external rules. The mapping reproduced unchanged: each of the four reflections still lands on this page plus Fix The Source Not The Symptom, Principle From The Iteration, and Principle After Iteration. No new pattern cleared the ≥3-citation bar from this cycle's input. Two of the six surfaced reflections were duplicates of prior entries (the margin-debug slug appeared twice; the source-over-symptom slug appeared twice), which collapsed to the same four distinct reflection slugs already cited above.

the corpus-elevation shape. The assistant proposed a profile note about the Highrise→Hydrolyze typo (redirected to the canonical record), then proposed writing the principle itself into Hermes memory (redirected to Gbrain); only on the third pass did the rule get stated as an operating principle with an explicit override clause. The reflection itself notes the rule was "a preference that has shown up again and again across the corpus" — the same iterative mode applied at the level of corpus accumulation rather than artifact refinement. Many small corrections across earlier sessions accumulating into one named rule on 2026-07-08.

At the corpus level, the equivalent move is: when the same shape of correction has accumulated across multiple sessions, codify the principle explicitly, with an override clause, rather than letting the next session re-derive it from scratch. The override clause is what converts the rule from dogma into a working default — see Fix The Source Not The Symptom for the canonical instance and the accompanying override-clause original for why the escape hatch is load-bearing.