Public knowledge catalogue · Allen Wade
Communication is a right. The pathway to it can still be broken.
We have more communication technology than ever before. Yet updates, accounts, authentication, software licences, payments and disconnected systems can leave the intended human result unavailable.
A message delivered is not necessarily communication completed. Did the intended person actually achieve the intended result?
Ecothesis documents how communication pathways become functionally unavailable while individual technologies still appear to work—and provides language for identifying where the result was lost.
- 21
- public records
- 5
- knowledge areas
- 2026
- first edition
The communication paradox
More ways to communicate. More places for communication to fail.
Communication produces a result
Modern communication is how people contact others, receive information, prove identity, access services, manage payments, submit forms and act on appointments. Delivery alone does not prove completion.
The pathway carries the outcome
A practical result may depend on devices, accounts, prompts, licences, payment methods, permissions, interfaces and authorised support. When one required transition fails, the technology can remain while communication disappears.
Communication slop obscures the action
Communication slop is the accumulation of messages, prompts, interfaces and administrative requirements that obscures the next meaningful action and separates the person from the intended result.
Ecothesis asks the question individual systems rarely answer: did the person actually achieve the intended human result?
Article 19 of the Universal Declaration of Human Rights recognises the freedom to seek, receive and impart information and ideas through any media. Read Article 19 at the United Nations Human Rights Office →
Problems people are trying to solve
Everything says connected—so why does nothing happen?
When devices, applications and accounts appear operational but the intended action still fails, examine the communication pathway between them.
Read the practical guide →Test one everyday outcome with the Functional Availability Check
02Why does a device work in one app but not another?
03Why does account recovery still require my old phone number?
04Why do messages only appear when I open the app?
05The device still works—but did an update remove the way you used it?
Catalogue edition 01
Knowledge records
Each record answers one practical question, names the mechanism and states the limit of the claim.
Foundation
A working device does not prove access
Can a device work correctly while the activity it was meant to enable remains unavailable?
Read record →ECK-002Technical availability is not functional availability
What is the difference between a system performing a function and an outcome being available in practice?
Read record →ECK-003The outcome is the unit of assessment
What should be assessed when technology is meant to support an everyday activity?
Read record →ECK-021The right to communicate depends on a functioning pathway
What practical infrastructure must remain available for a person to seek, receive or impart information through modern communication systems?
Read record →Diagnosis
The system works for the installer
Why can a successful demonstration fail to predict ordinary use?
Read record →ECK-008Map the complete pathway
How can a complex technology outcome be examined without reducing it to a device list?
Read record →ECK-009Find where the outcome is lost
How do you distinguish the visible symptom from the connection that actually failed?
Read record →ECK-010Abstract one level above the fault
How can field observations become transferable knowledge without turning into unsupported theory?
Read record →ECK-017The Functional Availability Check
What five questions test whether an everyday activity is actually available in practice?
Read record →Orchestration
Reduce the pathway, not the person’s choice
When does reducing interaction steps improve functional availability?
Read record →ECK-012Configure for real conditions of use
Why should configuration be tested where and when an activity actually occurs?
Read record →ECK-013The support network is part of the system
How can support involvement be designed without creating accidental dependence on one person?
Read record →Continuity
Outcome Drift
How can a previously successful technology outcome disappear while most of the system remains present?
Read record →ECK-015Proportionate continuity
How much recovery planning does an everyday technology outcome need?
Read record →ECK-016Documentation can be functional infrastructure
When does documentation become part of the working communication environment?
Read record →Field pattern
Small failures can remove large outcomes
Why can a minor physical or digital change have a disproportionate effect?
Read record →ECK-005Authentication is a chain, not a password
Why can an active account become practically inaccessible even when the person knows some credentials?
Read record →ECK-006The interface is part of the barrier
Can a device contain every required feature and still present an unusable pathway?
Read record →ECK-018The Authentication Barrier
When can security arrangements remove practical access to an otherwise active service?
Read record →ECK-019The Silent Phone
How can communication be delivered to a working phone without being functionally received?
Read record →ECK-020A reset does not remove every relationship
Why can a connected device remain bound to an unseen account, application or platform after it has been reset?
Read record →