# Specification Priority **Domain:** Research methodology / Evidence **Doc Type:** Developed Evidentiary Node **Maturity:** Developing **Collection:** [[collections/Gamification|Gamification Collection]] ## Definition **Specification priority** is the evidentiary advantage created when a search rule, thematic region, constraint, or discriminator is recorded before the result it later identifies. It establishes temporal priority of the specification over the observation. Specification priority is granular. An earlier hypothesis does not make every later procedural choice part of that original hypothesis. When a normalization rule is introduced to operationalize prior constraints, the record should preserve the hypothesis and constraints, the normalization procedure, and the returned result as three separately ordered layers. ## What it proves Specification priority can reduce degrees of freedom and answer a narrow reverse-engineering objection: the researcher did not select every rule after seeing the desired result. It does not establish statistical rarity, intended meaning, causation, operator identity, or institutional relationship. Those claims require independent evidence. ## Cicada application For the [[wiki/1233014400|January 27 coordinate]], `3301`, placement toward the front or middle of a Unix timestamp, the date-recovery objective, the proposed and independently verified seventeen-year cicada interval, and the thematic region are recorded as prior constraints. The fixed 00:00:00 UTC boundary was then introduced as the normalization procedure that operationalized those constraints before January 27 was returned. The later proximity of the January 16, 2026 U.S.–Israel AI statement is **discovered adjacency**, not part of either the prior specification or the normalization procedure, and must not inherit their confidence. ## Routes [[wiki/Search-Instruction Record|Search-Instruction Record]] · [[wiki/Provenance|Provenance]] · [[wiki/Designed Versus Convergent|Designed Versus Convergent]] · [[wiki/1233014400|1233014400]] · [[wiki/Cicada 3301|Cicada 3301]] ## Source - [[articles/gamification/I Got the Cicada 3301 Bug in 2023|I Got the Cicada 3301 Bug in 2023]]