Living LabPrototypes

LAB 02 · PROTOTYPE CATALOG

Turn a tested idea into
something you can hold.

A prototype is a bounded build: small enough to learn from, honest enough to measure and clear enough to improve before it becomes a kit, a system or an installation.

Browse prototype tracksSubmit a prototype briefBack to Living Lab

A prototype is not automatically a certified product, a safety approval or a performance guarantee. Higher-risk electrical, thermal, pressurized, structural and public-facing work requires qualified review, appropriate protection and a documented stop procedure.

FROM QUESTION TO BUILD

A prototype earns its next step.

The prototype stage turns a research question into a physical or digital object that can be inspected, tested, repaired and explained. It is a learning instrument before it is a sales promise.

Sustainable Oasis energy testing prototype in the Living Lab

The smallest useful build is the strongest starting point.

  • 01Define the user, need, question and decision the prototype must inform.
  • 02Write requirements, interfaces, limits, materials and a version number.
  • 03Build only what is needed to expose the biggest uncertainty.
  • 04Identify failure modes, isolation points, manual controls and stop conditions.
  • 05Measure function, service burden, cost, waste, reliability and user experience.
  • 06Decide whether to replicate, redesign, transfer to a kit or discontinue.

A prototype can be impressive and still be a poor product. We keep the operating boundary, evidence level and unresolved risks visible until the build has earned a broader claim.

PROTOTYPE PIPELINE

Six builds that connect the Oasis.

These tracks connect energy, water, food, automation, reuse and resilience. Each one is deliberately scoped so that a clear test can produce a clear next decision.

SO-EMS · M01

Energy meter bench

A low-voltage measurement bench for generation, storage, recovery, useful load and efficiency.

Bench-ready
Prototype: meters, shunts, safe DC enclosureGate: repeatable readings against a known load
SO-WATER · P01

Water recovery loop

A compact circulation and filtration loop that exposes flow, energy, quality and service requirements.

Prototype brief
Prototype: pump, filter stages, reservoir and sensorsGate: defined flow, quality and maintenance boundary
SO-FOOD · P01

Compact growing module

A measurable growing or aquaponics module that links water, light, nutrients, yield and labour.

Prototype brief
Prototype: growing bed, lighting and water loopGate: documented cycle with visible inputs and yield
SO-AUTOMATION · P01

Control and sensing hub

A human-first hub for sensors, alerts, dashboards and manual override across small Oasis systems.

Architecture
Prototype: sensors, controller, interface and fail-safe stateGate: useful decision without hidden automation risk
SO-REUSE · P01

Workshop material module

A traceable way to prepare recovered materials for safe, useful components and repairable assemblies.

Prototype brief
Prototype: sorting, preparation and fabrication workflowGate: quality, labour, cost and end-of-life record
SO-RESILIENCE · P01

Backup-power handoff

A clear critical-load handoff that makes runtime, protection, heat, noise and human procedure measurable.

Design review
Prototype: protected source, transfer procedure and load panelGate: safe handoff under a defined outage scenario

A track becomes a prototype when its interfaces, version, safety boundary, test plan and next decision are written down—not when a photograph looks impressive.

PROTOTYPE READINESS

Build for learning, service and transfer.

A good prototype gives the next person something they can inspect and improve. The record follows the build so that a promising component does not become an undocumented dependency.

01 · Need

Define the user

State who needs the prototype, what problem it solves and which decision it should make easier.

02 · Specify

Set interfaces

Name inputs, outputs, dimensions, materials, operating limits, controls and the version under review.

03 · Build

Expose uncertainty

Choose the smallest representative build that can answer the most important unknown.

04 · Challenge

Exercise failure modes

Test safe boundaries, maintenance, human error, fault states, isolation and manual override.

05 · Measure

Record the burden

Capture function, cost, time, energy, waste, reliability, repairability and user experience.

06 · Decide

Choose the next gate

Replicate, redesign, transfer to a kit or system, document for learning or stop with the reason visible.

Prototype IDStable name and version
Intended useWho and what it serves
InterfacesInputs, outputs and controls
MaterialsParts, sources and substitutions
Safety boundaryLimits, isolation and stop steps
Test planWhat will be measured and how
EvidenceDemo, estimate, measured or derived
Next gateThe decision after this build

READINESS LANGUAGE

A prototype has a stage, not a shortcut.

These labels help partners, customers and builders understand what a prototype can honestly support today and what still needs to be proven.

Brief

Prototype brief

The need, boundary, requirements and next test are clear, but the build has not yet been exercised.

Bench

Bench prototype

A bounded setup works under controlled conditions and exposes the measurements still required.

Field

Field prototype

The build has operated in a defined real-world context with service, failure and user observations recorded.

Transfer

Transfer candidate

The evidence, instructions, safety boundary and support burden are strong enough to consider a kit or system pathway.

PROTOTYPE SUBMISSION

Have a build worth making clearer?

Share the need, the smallest version you imagine and what you can contribute. We will help turn the idea into a bounded brief with a safety boundary, a test plan and a next gate.

  • 01Describe the user, problem and decision the prototype should support.
  • 02Tell us what you can build, measure, supply, host or explain.
  • 03Receive a practical brief before money or permanent installation is committed.

We will reply with next steps. This form does not certify a design, approve a hazardous build or collect payment.

FROM PROTOTYPE TO DEPLOYMENT

Prove the layer before you scale it.

Move from a bounded build to measured results, then decide whether it belongs in a kit, a system, a service or the next open research track.

See test resultsView experimentsExplore kits

Build • Test • Measure • Document • Prove • Share • Improve • Replicate — for generations.