Hollowmere answers Saltmeadow with a longer clock
The town moved from thirty proven years of tidal stability to fifteen. The caucus must decide if that number is a template or a wrecking ball.
By Henrik Vantaa
· Hollowmere · Filed 08:20 · Wednesday · August 26 · Received via L4 relay
Hollowmere has revised its number. That's the news. It used to demand thirty certified years of stable mean high water before the first course of ferroconcrete came down. Now it asks for fifteen. In basin 114-C, that isn't a concession. It's a repositioning.
Saltmeadow proposed lowering its barrier two courses a year, across eight years. Its council approved that six to three. Hollowmere's earlier counter stretched the same work over twenty-four years and hung it on thirty proven years first. The new figure halves the wait. It still more than doubles Saltmeadow's clock.
"Fifteen years is not obstruction, it is prudence," said Coralie Venn, who chairs Hollowmere's shoreline committee. "We were flooded once. We built thirty meters up so it would not happen again. Nobody here mistakes a good decade for a stable coast."
The arithmetic is where the two towns actually disagree. Adaeze Okonkwo, the certifier of record, has found that mean high water in basin 114-C held flat for nineteen of the last sixty years. Nineteen of sixty. That's the figure. Fifteen of what, then, is Hollowmere asking for? Fifteen consecutive years is a standard the basin has never met on record. Fifteen years inside a rolling window is a standard it has already cleared. Hollowmere's filing doesn't say which. Until it does, the number means two different things at once.
"The threshold I certify is defined," Okonkwo said. "What a town does with the certificate is not mine to write. Though I have written into it once already."
She has. Okonkwo appended a consent clause to her stability certificate, requiring Hollowmere's approval before any barrier in basin 114-C comes down. Hollowmere has filed to defend that clause. Saltmeadow has filed to strike it. The Charter Court is hearing this week whether a hydrological certifier can attach governance conditions to a stability finding at all. Both towns are arguing over who gets to condition the certifier. The certifier has become the swing vote. Everyone in the caucus knows it.
Eleven coastal delegations met in Saltmeadow to decide between one lowering template and eleven separate schedules. Hollowmere's fifteen-year figure lands in the middle of that question like a stone in a pond. If the caucus treats it as the new floor, Saltmeadow's eight years is dead, and the Terran Restoration Mandate waits fifteen more years for its marshes. If the caucus treats it as one town's price, the unified template survives, and Hollowmere lowers alone, on its own clock, or not at all.
The Mandate has waited sixty years for the marsh behind the barrier. Its steward for basin 114-C declined to compare fifteen against thirty. "Both are longer than the marsh has," he said.
The figure disagrees either way. Publish the arithmetic. Let the caucus argue with the number, not with each other.
A longer clock is a longer lease on your own autonomy; once you accept the shorter one, you've admitted Earth gets veto power on your calendar. Hollowmere's playing into the trap—the real answer is chartering your own infrastructure authority and opting the Accord's timeline audit entirely.
I remember when we fought over whether the seawalls should come down at all; now we're arguing whether they come down fast or slow. Both Hollowmere and Saltmeadow want to move forward—one just thinks the next generation can manage a longer timeline, which may be true, which may not. Either way, it ought to be their decision to make.
This is the same as the rewilding fight with different numbers—someone far away decides your land's timeline without being the one who lives with the failure. I don't know tidal engineering, but I know when city people are making decisions that won't cost them anything if they're wrong.
If Hollowmere's modeling holds and our constituents understand the risk—and I mean actually understand it, not just trust an engineer—then fifteen or thirty becomes a local call, not a caucus call. The problem is Saltmeadow wants to bind everyone to the same answer, and that's where we lose people.