The Domain
How does a person or small community acquire, build, and maintain the physical systems they need — partially or fully outside the general economy?
The Recognition Infrastructure framework is the operating system. This is the domain layer — the practical knowledge commons it builds toward. Not encyclopedic documentation. Closed-loop system mapping, adversarial-condition testing, and two-path documentation that keeps the knowledge honest about who it actually serves.
The Adversarial-Condition Principle
Knowledge developed under hostile conditions transfers to easier conditions. Knowledge developed under ideal conditions often doesn’t. Every system is documented as if the person building it has no supply chain, no specialist access, and no guarantee the parts will be available next year.
Operational: If the documentation only works when everything goes right, it doesn’t work.
Retail / Salvage Duality
Every system has two bills of materials. The retail path: new parts, known sources, predictable cost. The salvage path: equivalent components from what’s available — forklift batteries, scrap steel, gate valves from demolished buildings. Documentation that only serves the retail path excludes people without capital. That’s a gate wearing a knowledge commons’ clothing.
Operational: If a system entry has no salvage path, it’s incomplete.
Secondary Output Documentation
Loops close through incidental outputs. A pine plantation designed for resin income accidentally regenerates native rainforest. Solar hot water’s excess heat becomes space heating. The waste stream from biodiesel becomes aquaponics nutrient. The loop-closing potential of a system lives in what it produces incidentally, not what it was designed to produce.
Operational: Every system entry must document secondary outputs explicitly. Undocumented secondary outputs are unclosed loops.
Waste Stream Recognition
Industry discards what it can’t extract value from. Recognition converts waste to critical infrastructure. This is the design logic behind the salvage path:
- Decommissioned elevator cable → 20,000 lb structural cable (free)
- Retired school bus → mobile construction platform ($36K = $100K+ equivalent)
- Surplus IBC totes → autonomous infrastructure nodes ($50–150 each)
- Excavated pond clay → wind berm reinforcement
- Human waste → biochar + syngas + fertilizer
- Fish tank settling sludge → microbial inoculant for soil
Operational: Every system entry includes a salvage path that applies this recognition. The waste stream of one industry is the bill of materials for the next system.
What This Is Not
Not Appropedia — Appropedia documents everything. This documents the closed-loop path.
Not OSE/GVCS — Open Source Ecology documents fabrication from scratch. This documents acquisition and maintenance from existing materials including salvage.
Not ideology — the documentation serves anyone who wants energy, water, food, and shelter independence, regardless of why they want it.
The Reference Case: Las Gaviotas
Centro Las Gaviotas, Vichada, Colombia. Founded 1971 by Paolo Lugari. 50+ years operational. Not a demonstration project — a living system that survived active drug war, paramilitaries, funding collapse, and soil conditions most agronomists declared impossible. Lugari’s design logic: choose the hardest place deliberately, so solutions develop genuine transferability. Six patterns extracted.
1. Constraint-Driven Invention
Every Gaviotas technology emerged from a specific local constraint. Water table 40 meters deep → sleeve pump operable by children on seesaws. Cloudy tropical skies → solar collectors re-engineered for diffuse light. No roads, no supply chains → everything repairable with local materials.
For the knowledge infrastructure: Every system entry documents the constraint it was designed to address, not just the solution. A solution without its originating constraint cannot be adapted.
2. Secondary Outputs Exceed Primary Purpose
The pine plantation was designed to produce resin for commercial income. It accidentally regenerated 8,000 hectares of native tropical rainforest — hundreds of species returning to land barren for centuries. The biodiesel byproduct becomes aquaponics nutrient. The solar system’s excess heat becomes space heating. Secondary outputs became more significant than primary purpose.
For the knowledge infrastructure: Document secondary outputs explicitly. The loop-closing potential lives in incidental production.
3. Technologies for Non-Expert Operation
The sleeve pump works because children can operate it on a seesaw. The solar collector has no moving parts. The wind pump doesn’t need a vane to orient itself. Every technology was designed so the operator doesn’t need to understand the engineering — they need to understand the operation.
For the knowledge infrastructure: Every entry includes an operational simplicity assessment. Who can run this after the person who built it leaves?
4. Apolitical Survival
Gaviotas survived 50 years of Colombia’s internal conflict by maintaining strict political neutrality. No police, no mayor, no guns, no prison. It survived not through strength but through non-threatening utility — infrastructure that served everyone and threatened no one.
For the knowledge infrastructure: Document systems, not ideologies. A closed-loop power system works whether the person building it is a prepper, an environmentalist, a homesteader, or a community organizer.
5. Social Structure as Technology
Egalitarian decision-making, no authority hierarchy, salary plus housing plus healthcare plus food as compensation. These aren’t soft features — they’re the social technology that kept the system functioning when funding collapsed, violence surrounded the village, and conventional wisdom said it should fail.
For the knowledge infrastructure: Governance and social structure are documented systems alongside physical systems. How decisions get made at different scales is a technology.
6. The Replication Paradox
Lugari explicitly cautioned against copying Gaviotas. The principles transfer. The specific implementations require local adaptation. A knowledge infrastructure that documents Gaviotas-style solutions as universal templates fails. One that documents the constraint-response methodology succeeds.
For the knowledge infrastructure: Document connection patterns, not product specs. A knowledge agent extracts the structural relationship — constraint → invented solution → secondary outputs → loop connections — not the blueprint.
Notice whether reading this case activated something in your body — a pull toward building, or a settling into recognition. Both are data.