How can people retain meaningful control over intelligent infrastructure and rely on it when conditions are imperfect?
01 / The work
Two lines. One shared requirement.
Communication and records are not enough if people lose the ability to decide about them. That is the relationship the programme seeks to understand.
Line of work
A
Offline communication.
Studying how to transmit messages without the internet, and how people coordinate when technical tools fail.
Radio, transmission, local storage and coordination practices. The capabilities of each implementation need to be tested.
Line of work
B
Records and integrity.
Studying what makes a record inspectable and trustworthy in a disconnected setting, how it is preserved and who has the authority to keep it.
Integrity, detectable changes, synchronisation and local custody. Retaining data does not guarantee knowledge of everything that happened.
These lines are described in the public programme. Field observation and community listening bring questions that a technical solution alone can overlook. Sources and context ↗
A record is not the whole event.
“Sent”, “received” and “attended to” are different claims. They should not become interchangeable simply because an interface can display them.
In Pacchanta, the team received a message and heard a bell. They also encountered difficulties in knowing which case had been attended to and who was taking responsibility. A later inspection identified another limit: the node’s clock did not provide trustworthy timestamps. [1]
The question that remains
What evidence supports each claim, what conditions does that evidence require, and what must remain unknown?
State the question, the conditions and what would count as an answer. A programme aspiration is not yet a tested hypothesis.
Separate what is known from what is proposed.
Read the existing work, make assumptions explicit and do not mistake a change in vocabulary for a new contribution.
Choose a test that could contradict us.
Depending on the question, the work may require formal analysis, computational experiments, technical tests or field research with the appropriate authorisations.
Leave a result that others can examine.
Separate data, interpretation and limitations. Document failures too, and recognise the actual contributions of the people who did the work.
Where the work stands
The programme has deposited documents and a documented demonstration. These do not amount to validation of a service or confirmation of a future scientific contribution. Individual studies require their own definition, review and agreements.
Did it work, did it fail, or can we not yet tell?
The fieldwork gives a reason to look beyond the arrival of a message. The programme proposes studying it:
The question
If a single failure can affect both an infrastructure and the records that describe its operation, what can locally available information establish?
A service working is one outcome. Being able to establish that from locally available information is another. The proposed investigation would distinguish three conclusions:
Possible conclusion
Established success
The locally available information is sufficient to conclude that the service worked.
Possible conclusion
Established failure
The locally available information is sufficient to conclude that the service failed.
Possible conclusion
Unresolved outcome
The locally available information cannot distinguish between the two.
Understanding these limits would help people decide what to observe and retain, when to seek an additional check, and when the honest answer is that we do not yet know. The field report motivates attention to communication and records; it does not demonstrate this shared-failure mechanism or supply its probabilities. No novelty, result or funding is established by this page.
The limits are part of the research.
Read the publications for their purpose and scope, not as a list of equivalent results.