An open protocol for aid apps
Each app is a thread. The protocol is the rope.
An open format that lets aid apps publish and read the same data: collection points, needs, capacities and deliveries.
Conformance is measured, never declared.
The thesis
«Crecemos juntos: no competimos, nos alimentamos.»
Cabuya is the fibre you tie things with. A single thread holds nothing; twisted together, they carry what no one of them could. That is not a metaphor about collaboration in general — it is a description of what happens when two applications can read each other’s data.
Every app that joins keeps its own product, its own users and its own decisions. What it gains is that its records stop being trapped inside it, and that it can read everyone else’s without asking.
That is what the protocol is for. Whether it happens depends on the teams who adopt it, and none of it is achieved yet.
How it works
Four steps, and none of them need us
Nothing here requires an account, an approval, or a conversation with anyone. The protocol is a document; the validator is a program you can run yourself.
- 01
Publish a manifest
One JSON file at a known path that says who you are, what you publish, and under which licence.
- 02
Export a feed
Your places, in the shared schema. A static file at a stable URL is enough — no API required.
- 03
Run the validator
It fetches what you published and reports what it found. Every finding locates the problem and states the correction.
- 04
Open a registry entry
A pull request. The measurement happens on our side and is visible to anyone who looks.
Conformance
A ladder, not a gate
Every level is a membership class. You are in the network at L0, and each rung up makes more of it useful to you — but stopping is a position, not a failure.
Two classes never climb past L1: apps whose records are irreducibly personal, and apps that simply choose not to publish. Both are listed, and both are respected members.
The network
Who is in the registry
The registry lists applications, records what was measured, and does nothing else. It is not a directory of partners and it does not rank anyone.
| Application | Publishes | Entry state |
|---|---|---|
| ayuda.corag.app | place | Proposed |
| pereiraayuda.com | place | Proposed |
| pereiraresponde.co | place | Proposed |
| co.crafter.run | place | Proposed |
These entries were opened on each team’s behalf from the public analysis, and are waiting for that team to confirm them. Nobody here has claimed conformance, and none of these are endorsements.
Measured conformance states appear here when the validator starts running against live feeds on a schedule.
The long horizon
Ambition, not roadmapWhere this could go
- 1
An emergency network
Apps built during one emergency can read each other, so the next one starts with infrastructure instead of a spreadsheet.
- 2
An interoperability standard
The schema outlives the emergency that produced it, and becomes the ordinary way aid data is published.
- 3
A regional ecosystem
Another city, another country, adopts the same document without asking anyone — because it is CC0 and there is nobody to ask.
The specification is public. So is everything behind it.
The normative text, the schemas, the validator and the decisions that produced them are all in the repository, under an open licence, today.