Food and care
Community kitchens, preservation records, care rotas, access maps, shelter navigation, transport exchange, and skill-sharing systems.
Prototype · test · document · transfer
BUILD LABS
A Build Lab takes one brittle dependency and returns a working, inspectable alternative. It is not a panel, a pitch deck, or a promise waiting for funding.
The build ethic
IF ANOTHER PERSON CANNOT INSPECT IT, TEST IT, REPAIR IT, AND LEAVE IT, THE LAB IS NOT DONE.
Begin with a real dependency. Work beside the people who live with it. Build small enough to test. Publish the failure. Remove the founder as a required component.
NEED BEFORE NOVELTY.
PROOF BEFORE PROMOTION.
TRANSFER BEFORE SCALE.
Lab tracks
BUILD WHERE CONTINUITY BREAKS.
Every track ends with a usable artifact and a restoration or replication test.
Communication
Offline-first directories, local notice systems, accessible formats, printed contact trees, and inspectable communication tools.
Distributed memory
Replicated archives, teaching kits, translation sets, provenance manifests, checksums, and clean restoration exercises.
Repair and fabrication
Parts maps, tool libraries, maintenance guides, repair sessions, open drawings, and locally reproducible components.
Work and exchange
Worker cooperatives, shared procurement, transparent contribution agreements, mutual-credit experiments, and democratic production rules.
Councils and services
Public agendas, rotating roles, appeal paths, accessible decisions, service prototypes, and explicit Exit from every governing arrangement.
Definition of done
THE ARTIFACT MUST SURVIVE ITS MAKERS.
A demo is not resilience until someone else can use it.
Need verified
The people affected recognize the dependency and can challenge the problem statement.
Artifact working
A real object, process, agreement, service, lesson, dataset, or tool exists beyond a slide or intention.
Failure recorded
Known limits, unsuccessful tests, missing dependencies, maintenance burden, and unresolved questions remain visible.
Transfer tested
Someone outside the core team can inspect, use, restore, teach, or reproduce it from the record.
Power bounded
Roles rotate. Accounts are visible. Decisions can be challenged. People can leave without losing ownership of their labor or identity.
Build Labs are open, lawful, and nonviolent. Do not use this instrument for targeting, sabotage, weapon construction, clandestine operations, stolen access, or harmful infrastructure interference.
DO NOT PREPARE FOR THE END.
PREPARE TO BE THE BEGINNING.
The Lab lifecycle
NAME THE BREAK. BUILD THE SEED. PUT IT IN OTHER HANDS.
A Lab is temporary. The capacity must become durable somewhere else.
Name the dependency
Preserve the evidence, affected people, current owner, failure mode, and why the dependency matters.
Confirm the need
People living with the problem can challenge the description, priorities, access assumptions, and intended result.
Bound the seed
Choose the smallest useful artifact that can be built, inspected, tested, and honestly maintained.
Expose every dependency
Name materials, skills, permissions, costs, platforms, maintenance, accessibility, and what still belongs to another owner.
Test one failure
Use a safe bounded case from absence, outage, scarcity, error, capture, or exclusion. Preserve what broke.
Transfer outside the makers
A person outside the core team uses, inspects, repairs, or reproduces the artifact from the record.
Write the guide and Ark unit
Turn the work into a teachable path, independent copies, restoration plan, correction route, and review date.
Close, continue, or retire
Name maintenance custody, next test, unresolved debt, or the evidence that the Lab should stop.
The founder-absence test
IF THE FOUNDER MUST REMAIN, THE DEPENDENCY SURVIVED WEARING YOUR LOGO.
Remove the original builder from the next test. Ask another person to find the source, understand the record, run the bounded task, report the failure, and locate the correction path. If they cannot, return to the build.
A Lab closes or changes direction when the need is not confirmed, affected people reject the result, critical dependencies remain hidden, maintenance has no custodian, or transfer repeatedly fails. Ending a weak build honestly protects the next one.
NEED BEFORE NOVELTY.
PROOF BEFORE PROMOTION.
TRANSFER BEFORE SCALE.
RETIREMENT BEFORE PRETENSE.
From prototype to proof
SHOW THE BUILD. SHOW THE TEST. SHOW THE FAILURE.
A prototype does not become verified through confidence. Submit bounded evidence, limitations, inspection steps, and the privacy-safe record humans can challenge.
Submit a Build Lab artifact