01
Village Infrastructure Planning
Some things only make sense when several households share them, and deciding which is the whole planning question.
The test is whether the thing has a high fixed cost and low marginal use. A kiln, a mill, a forge, a press, a wood-fired oven, a large workshop, a water supply: each is expensive to build and idle most of the time, which is exactly what makes it worth sharing. A shovel is not.
Position by frequency and by nuisance. Anything used daily should be central and reachable in bad weather; anything noisy, smelly or dirty belongs downwind and downhill.
Then the part that decides whether shared infrastructure survives: who maintains it, who pays, and how a decision about it is made. Shared assets fail on governance far more often than on engineering, and every enduring example, common grazing, irrigation systems, village mills, had explicit rules about use and upkeep.
Plan the corridors before the buildings. Where water, paths and services run is much harder to change than what sits beside them.
02
Roads, Paths & Access
Access is what makes everything else usable, and a track that fails in the wet is a place that's cut off exactly when it matters.
Almost all road failure is water. Water on a surface softens it, water flowing along it scours it, and water underneath it destroys the base. So the whole craft is drainage: a crowned or cross-sloped surface that sheds to the sides, ditches that carry it away, and culverts wherever it needs to cross.
Gradient matters in both directions. Too steep and vehicles struggle and water runs fast enough to cut; too flat and it doesn't drain. Where a slope is unavoidable, cross-drains at intervals take water off before it gains enough speed to do damage.
Build from the bottom. A good base of coarse material, well compacted, with finer material above, carries load and drains. Surfacing over soft ground without a base produces a track that fails in the first wet season, repeatedly.
Design for the worst vehicle and the worst weather, not the ordinary one. The delivery, the fire truck and the ambulance are the ones that matter.
03
Storage & Distribution
Paul's scope for this, and it stands as written: village-scale networks for water, power and goods.
Storage does one thing above all: it decouples supply from demand. Water in a tank, grain in a granary, power in a battery or a raised weight, fuel in a store, all let production and consumption happen at different times, and that's what makes an intermittent supply usable.
Size storage against the longest gap instead of the average, because the average conceals the interval that actually breaks you, and that's true equally of water, food and fuel.
Distribute from storage, not from production. A system where use draws directly on generation is a system where every fluctuation is felt; one that draws on a store is smooth and forgiving.
Losses in distribution are quiet and cumulative. Leaking pipes, uninsulated hot runs, undersized cable, spillage and spoilage in handling all take a percentage every time, and the total is frequently larger than any single failure.
This subject overlaps water management and power generation deliberately, and the overlap is a crossover and not a problem: what belongs here is the network view, several users, shared assets, and what happens when one part is short.
04
Heating & Ventilation
Moving heat and air through a building is a network problem, and both halves have to be designed together.
Heat moves by conduction through materials, by convection in moving air, and by radiation directly to what it strikes. A fire warms mainly by radiation, so it heats what it can see; a masonry mass warms by radiation and slow conduction; warm air rises and stratifies, which is why heat collects at ceilings and floors stay cold.
Traditional systems used mass deliberately: heavy stoves and masonry heaters absorb the heat of a fast hot fire and release it slowly for many hours, which is far more efficient and more comfortable than a fire that heats only while it burns.
Ventilation has to be deliberate. Combustion needs air, and a sealed room with a fire in it will draw combustion air from wherever it can, which in the worst case is back down the flue, bringing exhaust gases with it. That's the mechanism behind carbon monoxide incidents, and it becomes more likely as buildings are sealed for efficiency.
Occupants produce moisture continuously, and it must be able to leave. Without controlled ventilation it condenses inside the fabric, causing rot and mould in exactly the buildings that were insulated to be better.
05
Communications & Signalling
Getting information from one place to another without infrastructure is an old problem with well-tested answers.
Sound carries and is directional and weather-dependent: bells, horns and whistles were the standard means of summoning and warning, and a small number of agreed patterns carry a surprising amount of meaning. Three of anything remains the recognised distress signal in most places.
Visual signalling carries further and needs line of sight: flags, lights, smoke, mirrors and shapes on the ground. It's why signal stations sat on hills and why a ground signal for aircraft has to be large, geometric and high-contrast.
The design work is the code, not the medium. A prearranged set of simple signals that everyone knows is worth more than a sophisticated channel nobody has agreed how to use, and the agreement has to exist before it's needed.
Radio remains the most useful modern option that doesn't depend on infrastructure, and it depends on power and on people knowing the frequency and the schedule. A listening watch at agreed times is the arrangement that makes it work.
06
Electrical Wiring & Distribution
Getting power from where it's made to where it's used, safely, and this is the one part of the subject where the rules are not advisory.
Voltage drop is the fundamental constraint. The same power at lower voltage means higher current, and higher current means more loss as heat in the cable. So low-voltage systems need much heavier cable over any distance, and undersized cable is simultaneously a waste and a fire risk.
Protection is the safety layer, and it protects the cable in place of the appliance. Every circuit needs a device that disconnects before the cable can overheat, sized to the cable, and earthing that gives fault current a path so that device operates.
Layout matters for reliability. Separate circuits for separate purposes means a fault takes out one thing instead of everything, and it makes fault-finding possible. Label everything, because an unlabelled board is a hazard to whoever works on it next.
⚠ Fixed electrical work is regulated nearly everywhere and it is regulated because it kills people. Generating your own power changes nothing about that. This is a place where the correct answer is a qualified person, and it overlaps with the crossover to power generation and not duplicating it.
07
Redundancy & Failure Planning
The discipline that turns a set of systems into a resilient place, and it's mostly a way of thinking in place of a set of equipment.
Ask of everything important: what happens when this fails, how would I know, and what do I do then. Most systems have never had that question asked of them, and the answers are frequently uncomfortable.
Find the single points of failure, and particularly the shared dependencies underneath apparently separate systems. Two water sources that share one pump are one source. Three arrangements that all need power are one arrangement. The most common single point of failure in a household is one person who knows how everything works.
Prefer graceful degradation to binary failure. A system that keeps working at reduced capacity buys time; one that stops entirely does not. Manual override on anything automated, and a way to run without the clever part, is what provides it.
Then rehearse. A plan that's never been tested is a hypothesis, and running a system on its backup deliberately, while nothing is wrong, is how you find out that the backup needed something you don't have.