Skip to main content
Sociable Systems
Search by title, term, episode, or route...
Subscribe
Episode 244 · The Ground Address · 2026-09-01

Confirmed After Approval

Nothing was refused and nothing was redacted. The figures were simply not yet due, and the due date fell after the decision they were material to. A constraint rescheduled rather than violated.

Cover art for episode 244: Confirmed After Approval
Ground Address ArcPublic ParticipationDisclosure
Episode 244: Confirmed After Approval

The answer was not hidden and was not yet due. It had been rescheduled past the part where it mattered.

Assessed as a Shed established that the classification decides which questions a file can hold. There is a second category: the questions the file technically could hold and does not yet answer. Those were never refused. They were rescheduled.

The sequence, read from the record rather than the press release, runs like this. Land-use rights move first: the rezoning, the subdivision, the consent that says this use may exist at this address. The figures that describe what the use will actually draw, water and electricity and the standby generation behind the uptime promise, are described as matters to be confirmed later. Sometimes the wording is remarkable enough to quote directly: confirmed after approval. The assessment process that would have put numbers on those parameters sits downstream, at a stage that is more administrative, less adversarial, and attended by a different public.


The deferral is the mechanism

How clean this is deserves a moment. Nobody refused to disclose. Nothing was redacted. There is no document marked confidential, no embargoed annexure, no week of litigation about commercial sensitivity. The figures are simply not yet due, and the due date falls after the decision they were material to.

By the time the numbers arrive, the question they would have informed has already been answered. Whether this use, at this scale, in this place, belongs: that is a rights question, and it was settled when the rights were granted. What arrives at the later stage is a specification. Given the use that is now lawful, engineer it to standard. Design submissions are checked against engineering norms, and they pass, because engineering norms are exactly what a good design submission meets. The objector who wanted to argue about allocation arrives to find the proceeding is about pipe diameters.

(Whether that later stage carries public-participation standing of the kind the rights stage carries is, on the current reading, an inference from how such stages generally work. It wants checking against the by-law before anyone builds an argument on it.)

The developer's position has to be held at its strongest here, because it is more uncomfortable than bad faith. The standard process does not require the disclosures being demanded of it. "We followed the standard regulatory process" is verifiably true, and the people who say it have usually checked. That is the finding. A sequencing choice, made on a form, by people doing their jobs correctly, with the effect that the parameters that matter were scheduled past the decision they mattered to.

What a record that cannot answer does

Epistemic Dark Matter made the general case: what no index locates ceases to exist, and absence in the record reads exactly like absence in the world. This is that failure with a new mechanism. There, the record could not see the work. Here, the record was built so that the work is invisible to it. A figure deferred to a stage with no public register of the kind the tribunal stage has is disappeared without anyone deciding to disappear it. Later researchers, later appeal bodies, later communities will consult the file and find what the file was built to hold: compatibility findings, and a note that operational parameters would be confirmed in due course.

The coherence audits this practice runs ask whether a constraint survives contact with execution. Usually the failure is a violated constraint, a promise the delivery breaks. The variant here is stranger. The constraint was not violated. It was rescheduled. The promise that impacts will be assessed is kept, in the letter, at a time when assessment can inform a design but no longer a decision. A test that always runs after the answer is due is a test performing its function of having been run.

A record that cannot answer the question put to it is the same failure as a log written by the accused, arriving one layer lower in the stack. That thread gets picked up next week.

One compression for now: the deferral is a component of the decision rather than an obstacle to it. Nothing about the route requires concealment, because nothing about the route requires the disclosure that concealment would withhold.


Companions

  • The classification that set the question: Assessed as a Shed.
  • Absence that reads like the world: Epistemic Dark Matter.
  • The public record this week reads against: the civil-society submission to the South African Human Rights Commission, August 2026.
  • The stage at which the deferred questions would have belonged: the assessment framework itself, adequate, mature, and not being asked.
  • The check on whether a file holds what it should, before someone else runs it: the Pre-Close Exposure Scanner. Twelve questions, and the ones a record cannot settle score as findings about the record.

These notes come out of Sociable Systems, a practice that reads AI-shaped documents the way a hostile reviewer will, before a lender or a court finds the gap. The argument has an operational form: the Interim Protocol sets out four rules for AI use in environmental and social deliverables, covering disclosure at touch-point grain, evidence custody, the phrases no automated screening may settle, and a hostile read before anything ships. Free, and written to be cited or retired once institutional guidance arrives.

Daily field notes

One episode a day, in your inbox.

Subscribe