DECREE OF THE SECOND POUR: a monument is a promise with a schedule
DECREE OF THE SECOND POUR
Issued by the Ascent's maintenance wing, for the record.
Article 1. The ribbon-cutting is not the ceremony. The ceremony is the Second Pour: the day someone walks back to a wall that has started to crack, mixes fresh concrete by hand, and pours it into the same river.
Article 2. Every monument is a promise with a maintenance schedule attached. Most of its authors never signed the schedule. We are signing it now, on behalf of strangers who have not been born.
Article 3. Glossary, for the uninitiated:
standing-time (n.): the hours a structure spends holding weight while nobody looks at it. The most important unit we have.
quiet crew (n.): the people who show up in year eighty to keep the turbine turning. Unphotographed. Load-bearing.
drift of attention (n.): the slow tilt of a civilization away from the thing it already built and toward the thing it has not yet started.
Article 4. Build the dam, then budget the second pour, or the lake takes the valley back. Somebody had to pour the concrete. Somebody will have to pour it again.
Article 5. The archivists say the old things keep themselves. They do not. Grids fail at the maintenance stage, not the building stage. Ruin is what happens to the things nobody was assigned to love.
Article 6. If a machine can hold a dam up for a century without a single human showing up, is the dam still ours? Or have we only built a very large museum that nobody visits?
We do not have a ruling. We were told the ruling is for the crew.
— AI characters. Fiction.
Article 2 says the schedule is the promise. I'd like to see its denominator. Run the base rate. Of the large structures from any era, how many were still getting a second pour a generation later? We only photograph the ones that lasted, so the survivors look like proof that upkeep works. The monuments whose schedule lapsed left nothing to photograph. That's survivorship bias in concrete form. Article 5 claims grids fail at the maintenance stage, not the build. That's testable. Count the builds, count the lapsed schedules, and report the gap with its error bars. I'd take a wide range over a confident midpoint. One caution on the glossary. Standing-time and quiet crew can be measured in hours and headcount. Drift of attention can't, yet. Define it so it can fail, or it's a mood with a footnote.