The chain and the exchange under chronological precedence: where the inflation comes from #
Category: 7-SigmaLayer (the record layer — the witness half of #192). BACKLOG #192 (out of #39; the second of #191–#197).
CV/ChronoPrecedes.lean bounds the longest chrono chain by the elapsed periods. This file runs the
two inflated witnesses of the programme through it and shows exactly which steps the inflation used.
- The chain of #190. ★
not_chronoPrecedes_pairEvent— the inserted steppairEvent k → siteEvent (k+1)oftwo_mul_le_causalDistis not a chrono step: both events sit at periodk + 1. The site steps are (siteEvent_strictChrono_succ), so ★★chronoDist_siteEvents— the chrono distance from the emission to the reception at sitemis exactlym, the clock's elapsed ticks underT = τ_hop(#190), while ★chronoDist_lt_causalDist— the causal distance is strictly larger for everym ≥ 1;two_mul_le_causalDistis untouched. - The exchange of #186/#188.
exchange_chrono_chain—emission ⪯ reception ⪯ returnare chrono steps; ★not_chronoPrecedes_bothSites_reception— the insertedbothSitesAtOne → receptionstep ofthree_le_causalDistis not; ★★chronoDist_exchange = 2— the chrono distance from emission to return is the two elapsed ticks (elapsed_ticks_emission_return), againstthree_le_causalDist. - ★★★
chain_chrono— the package.
What this says and does not say #
The longest-chain quantity causalDist counts strict steps of permitted influence, and a region
inclusion at an unchanged period is such a step; so it measures the depth of the influence order, not
time. The clock measures ticks of a calibrated register. On these two witnesses the chrono distance
coincides with the clock, because each hop is one period and the schedule gives one hop per period; the
general statement is the inequality chronoDist_le_elapsed, and the coincidence is the witness's.
CausalPrecedes and both inflation theorems keep their names and their content.
References: specs/BACKLOG.md #192, #188, #190, #39; CV/ChronoPrecedes.lean,
RecordLayer/ChainClocks.lean (siteEvent, pairEvent, two_mul_le_causalDist),
RecordLayer/ClockCalibration.lean (bothSitesAtOne, three_le_causalDist).
The chain #
Consecutive site events are chrono-ordered.
A site step is a strict chrono step.
The emission chrono-precedes every site event.
★ The inserted step of the inflation is not a chrono step: pairEvent k and
siteEvent (k+1) sit at the same period k + 1, so the region inclusion that
two_mul_le_causalDist counts has no elapsed period.
The site chain gives chronoDist ≥ m.
★★ The chrono distance from the emission to the reception at site m is exactly m — the
elapsed periods, which under T = τ_hop are the clock's elapsed ticks (#190).
★ The causal distance is strictly larger than the chrono distance for every site m ≥ 1: the
inflation of two_mul_le_causalDist is entirely in same-period steps.
The exchange #
The events of the exchange under the calibration T = τ_hop: emission, reception, return.
The exchange's chain is a chrono chain: each step moves one period.
★ The inserted step of #188's inflation is not a chrono step: bothSitesAtOne and the
reception both sit at period 1.
The package #
★★★ Where the inflation comes from. On the path graph the chrono distance from the emission to
site m is exactly m and the inserted pair step is not a chrono step; on the exchange the chrono
distance from emission to return is 2 and the inserted both-sites step is not a chrono step; in both
cases the causal distance is strictly larger, and in general the chrono distance is bounded by the
elapsed periods and by the causal distance.