Key idea: If the author states (a) a fixed unit structure and (b) deliberate obscurity and (c) a time-bounded corpus, then a reader is justified in testing non-local reading strategies—i.e., reading across the corpus to locate repeated structure—so long as the reader preserves uncertainty and avoids “event pinning.”
The protocol is anchored to explicit method statements, summarized as claim IDs: C-## from the César claims page and H-## from the Henry II claims page.
Primary anchors:
César: letter-to-cesar.html#p033 (100-unit structure, joined obscurely, 3797 bound), #p009 (obscure/perplexed sentences), #p030 (place/time aligned to celestial figures).
Henry II: henry-ii-epistle.html#h006 (astronomical calculation), #h007 (rhyme easy, sense difficult), #h019 (could date each quatrain, refuses), #h021 (avoid calumniators).
Nostradamus states that he composed “books” containing one hundred quatrains, “joined obscurely.” A fixed unit structure is a prerequisite for any protocol that compares repeated positions across units.
Claim refs: C-13, C-06
Anchor: letter-to-cesar.html#p033, #p009
He describes “cloudy figures” and “perplexing sentences,” and (in Henry II) says he could assign the time-numbering to each quatrain, but refuses. This implies the surface text is not designed for single-pass, local reading alone.
Claim refs: C-06, H-03, H-04
Anchors: letter-to-cesar.html#p009,
henry-ii-epistle.html#h007,
henry-ii-epistle.html#h019
The César letter sets an outer bound (“to the year 3797”) and repeatedly connects composition to astronomical revolutions and calculation. A bounded corpus invites structural tests across the whole set.
Claim refs: C-02, C-14, H-02
Anchors: letter-to-cesar.html#p033,
letter-to-cesar.html#p004,
henry-ii-epistle.html#h006
He describes aligning locations and time with celestial configurations. If time information is partially withheld, one legitimate reader move is to test whether relative position (e.g., quatrain number across units) behaves like an indexing surface.
Claim refs: C-10, H-02
Anchor: letter-to-cesar.html#p030, henry-ii-epistle.html#h006
Definition: “Horizontal reading” means comparing quatrains at the same ordinal position across multiple centuries (e.g., I:12, II:12, III:12…), treating the ordinal as a structural index rather than as a guarantee of shared topic.
Accept the author’s declared unit: 100 quatrains per “book”. Treat quatrain number as an index you can test across books.
Do not “solve” by naming modern events. The goal is to detect repeatable structure: motifs, rhetorical moves, recurring oppositions, repeated staging, and recurring semantic clusters.
Assume the text was engineered to resist single-quatrain decoding. Therefore, your default move is comparison: same index across books → detect shared scaffolding.
Select one quatrain number N. Collect I:N, II:N, III:N… as far as your edition allows. Read them as a bundle, not individually.
Bundle size rules: minimum 5 items; prefer 8–10+ where available; document missing entries.
For each bundle, record: repeated terms/roots, repeated agents (king/people/sect/temple/sea/etc.), repeated actions (fall/return/burn/flee/unite/divide), repeated settings (city/sea/mountain), and repeated temporal cues (night/day, seasons, calendar hints).
Do not record “what it really means.” Record what recurs.
Henry II explicitly says he could assign time-numbering per quatrain but does not. That makes it legitimate to test whether ordinal position behaves like a stable skeleton for comparison.
Your output should preserve ambiguity: show the bundle, show the repeats, show the unresolved. This aligns with the author’s stated concealment posture and avoids “single correct reading” claims.
Example output format (recommended):
Bundle N=12
• Terms recurring: X, Y, Z
• Agents recurring: A, B
• Actions recurring: fall/return, unite/divide
• Settings recurring: city/sea
• Notes: missing II:12 in edition; uncertain synonyms flagged
A pattern is not “this predicts X.” A pattern is a repeatable structural behavior under a consistent method.
In other words: the method must succeed as structure research, not as prophecy confirmation.
The letters justify concealment and indexing tests; they do not license certainty about modern correspondences. The project remains a research presentation of method.
If you propose a time key (e.g., your 2020 start hypothesis), present it as a tested model: define inputs, define transformations, show reproducibility, show where it fails.
The letters justify a methodological posture: structured units, deliberate obscurity, astronomical calculation, time-bounding, and withheld keys. That supports exploration of cross-unit reading—nothing more.