LAB 03 · TEST RESULTS

Measure what matters.
Publish the boundary.

A result becomes useful when its setup, measurement method, uncertainty, limitations and next decision are visible to someone who was not in the room.

Browse result records Submit a result Back to Living Lab

A result belongs to a defined setup. It is not automatically a product rating, a safety approval or a guarantee for another site. Higher-risk tests require qualified review, appropriate protection and a documented stop procedure.

RESULTS WITH CONTEXT

A number without a setup is not evidence.

Test results connect a measured observation to the conditions that produced it. That makes comparison possible, keeps uncertainty visible and prevents a single impressive number from becoming an unsafe promise.

Sustainable Oasis water testing setup in the Living Lab

Every result answers six questions.

01What was tested: the system, version, scope and operating boundary.
02How was it measured: instrument, method, units, timestamps and calibration.
03What changed: baseline, inputs, outputs, conditions and uncertainty.
04What failed: limits, maintenance, human factors, anomalies and missing data.
05Can someone repeat it: procedure, raw record, calculations and materials.
06What follows: replicate, redesign, transfer, keep observing or stop.

Measured does not automatically mean safe, profitable or transferable. It means one defined setup produced one documented observation that can support the next decision.

RESULT RECORDS

The result is more than pass or fail.

These records show the evidence stage and the next gap. Some are ready for a measured record; others intentionally remain a baseline or a plan until the data exists.

SO-EMS · 001

Low-voltage meter bench

A repeatable bench for tracking generation, storage, recovery, useful load and efficiency under a defined DC setup.

Record ready

Visible: instrument list, load profile and unitsNext: publish raw readings and uncertainty

SO-EMS · 002

Solar-to-storage profile

A baseline for matching generation, storage capacity, charge losses and useful runtime across small loads.

Pilot scope

Visible: load definition and comparison methodNext: capture a full charge and discharge window

SO-WATER · 001

Water recovery loop

A defined circulation and filtration scenario that connects flow, pump energy, quality, maintenance and service intervals.

Baseline planned

Visible: flow, head, filter stages and boundaryNext: record litres, watt-hours and quality checks

SO-FOOD · 001

Compact growing loop

A pilot record for water, light, nutrients, labour, yield and waste in a small growing or aquaponics module.

Data pending

Visible: crop cycle, inputs and observation scheduleNext: complete one documented cycle

SO-AUTOMATION · 001

Control and sensing hub

An observation record for alerts, dashboards, sensor quality and manual override across a small Oasis system.

Demonstration record

Visible: decision map, sensor states and fallbackNext: exercise a fault and recovery sequence

SO-RESILIENCE · 001

Critical-load handoff

A planned result record for safe transfer, runtime, heat, noise and human procedure during a defined outage scenario.

Test planned

Visible: load list, surge watts and protection planNext: run a supervised handoff test

The statuses above do not claim that every measurement is complete. They tell the reader what is prepared, what is observed and what still needs data before a conclusion can be trusted.

RESULT RECORD

Publish the record, not only the headline.

A useful result lets another person inspect the setup, understand the calculation and see what the result does not prove. The record is the bridge between a test and a responsible decision.

01 · Setup

Scope and baseline

Name the system, version, operating boundary, baseline and conditions that make the result meaningful.

02 · Instrument

Method and units

List instruments, calibration, sampling, units, timestamps and the person or process collecting the data.

03 · Raw data

Keep observations visible

Preserve readings, photos, logs, anomalies, maintenance, downtime and missing values before summarizing.

04 · Calculate

Show the path

Separate measured values from estimates and derived figures. State assumptions, formulas and uncertainty.

05 · Limit

State what failed

Describe boundaries, confounders, safety limits, human factors and conditions that were not tested.

06 · Decide

Choose the next gate

Replicate, redesign, transfer, continue observing or stop—and make the reason visible.

Result IDStable record and version

SetupSystem, boundary and baseline

Inputs / outputsWhat entered and left?

Data windowWhen and how long?

InstrumentationHow was it measured?

UncertaintyWhat could change the reading?

LimitationsWhat the result does not prove

DecisionWhat happens next?

RESULT LANGUAGE

Every label tells the reader what is known.

Precise language protects trust. It keeps a measured observation separate from a calculation, a field note or a claim that the current record cannot support.

Measured

Measured value

A reading captured with a defined instrument, setup, timestamp, unit and stated uncertainty.

Derived

Derived result

A calculation from recorded data with assumptions, formulas and limitations made visible.

Observed

Observed condition

A qualitative observation or user report that guides the next test without pretending to be a measurement.

Not proven

Boundary statement

The conditions, safety questions, transfer claims or performance conclusions this record does not establish.

PUBLISH A RESULT

Have a result worth making reproducible?

Share the setup, the data status and the next decision. We will help turn a promising observation into a bounded result record that another person can inspect and improve.

01Identify the system, version, baseline and conditions.
02Tell us what was measured, observed, estimated or derived.
03State the limitations and the next test before making a broader claim.

FROM RESULT TO DECISION

Evidence earns the next step.

Follow a result back to its experiment, forward to a prototype or across to open R&D. Only then decide whether a kit, system or service is ready to carry the work further.

View experiments View prototypes Open R&D

Measure what matters.Publish the boundary.