Officially sourced
A manufacturer or authorized retailer published the specification. Espresso Receipt verified the record and date.
ESPRESSO RECEIPT TEST LAB / PROTOCOL 1.0.0
We do not call a spec sheet a test.
Official records tell us what a product claims to be. The Test Lab is how a physical U.S. unit earns an observed label—through declared conditions, repeated measurements, raw data, limitations, and independent review.
INDEPENDENT PRODUCT RUNS00
NO CLAIMUNTIL THE RUN PASSES
- Catalog records
- 29
- Foundation queue
- 08
- Observed coverage
- 0.0%
- Raw release
- EMPTY / VALID
THE LINE WE WILL NOT BLUR
Four labels. Four different claims.
Editorial interpretation
A fit or workflow judgment grounded in cited product architecture. It is not a physical measurement.
Modeled
A disclosed formula produced the value from visible assumptions. The output changes when the assumptions change.
Independently observed
A resolved physical unit completed the public protocol. Conditions, repetitions, instruments, raw data, and limitations travel with the value.
PROTOCOL LANES / 1.0.0
Every result must survive the whole bench.
A machine and grinder do not run identical modules. Both must clear identity, physical fit, real workflow, sound and energy, and reset. Product-specific lanes then test the mechanism that matters.
IDMACHINE + GRINDER Resolve the exact unit
Record model, public SKU, revision, region, voltage, acquisition channel, and a non-public serial fingerprint before a result can attach to a catalog record.
- Minimum
- 1 inspection
- Published output
- Unit identity and revision boundary
FITMACHINE + GRINDER Measure the working footprint
Measure closed dimensions, operating clearance, access paths, cable or hose reach, and the space needed for normal loading, filling, and cleaning.
- Minimum
- 3 runs
- Published output
- Closed and operating dimensions
FLOWMACHINE + GRINDER Time the real workflow
Record a repeatable start-to-finish task from a cold, reset station, including the touches the product requires rather than timing one isolated mechanism.
- Minimum
- 5 runs
- Published output
- Median task time and observed interruptions
BREWMACHINE Test brew repeatability
Use a fixed coffee, grinder, basket, dose, yield, preparation sequence, and instrumented brew path to compare consecutive extractions without turning temperature into a universal taste score.
- Minimum
- 10 runs
- Published output
- Temperature and beverage-mass spread
MILKMACHINE Test steam and recovery
Heat a fixed mass of refrigerated milk to the same stop temperature, recording elapsed time, recovery, and required operator steps across repeated cycles.
- Minimum
- 5 runs
- Published output
- Steam time, recovery, and workflow notes
DOSEGRINDER Test dose delivery
Run a documented seasoning and purge procedure, then measure input, output, elapsed time, and exchange across consecutive doses.
- Minimum
- 10 runs
- Published output
- Dose variance, exchange, and grind time
CTRLGRINDER Map useful adjustment
Measure particle-distribution movement and shot-flow response across documented adjustment points while keeping coffee, dose, preparation, machine, and target yield fixed.
- Minimum
- 10 runs
- Published output
- Adjustment response and usable espresso window
LOADMACHINE + GRINDER Record sound and energy
Measure equivalent sound level at a fixed distance and energy used during the declared task. Report the room floor and test duration with every value.
- Minimum
- 5 runs
- Published output
- Task dBA and energy use
RESETMACHINE + GRINDER Reset the station
Complete routine contact-point cleaning from a used state, record access, consumables, elapsed time, retained mess, and any model-specific manual boundary.
- Minimum
- 5 runs
- Published output
- Reset time, consumables, and access notes
FOUNDATION QUEUE / NOT YET TESTED
The first questions going onto the bench.
Queue placement is an editorial research decision, not a favorable result, purchase confirmation, or affiliate ranking. Every card below still carries only its source-verified catalog record.
RecordResearch questionStatus
01Breville / machineBambinoHow quickly does the complete brew path become repeatable, and how much working depth does the compact body actually require? QUEUED02Gaggia / machineClassic Pro E24What repeatability and two-drink workflow does the single-boiler architecture deliver under one declared preparation protocol? QUEUED03Profitec / machineGOHow do warm-up, temperature recovery, steam switching, and reset time behave across repeated home sessions? QUEUED04Breville / machineBarista ProWhat does the integrated workflow save in touches and time, and where does grinder adjustment constrain repeatability? QUEUED05Baratza / grinderEncore ESPHow much shot-flow movement does one documented adjustment create, and how repeatable is dose delivery? QUEUED06MiiCoffee / grinderDF54What are the observed dose exchange, task time, sound, and adjustment response after a published purge procedure? QUEUED07MiiCoffee / grinderDF64 IIHow repeatable is the single-dose workflow, and how does adjustment response compare across a declared espresso window? QUEUED08Eureka / grinderMignon SpecialitàHow do timed dosing, retention, sound, and fine adjustment behave across consecutive espresso sessions? QUEUEDPUBLICATION GATE / FAIL CLOSED
A result is rejected if any required piece is missing.
Interrupted and conflicting runs can remain in the internal run log. They cannot become a public observed claim until the record is complete.
Compare this with the current software testing boundary →- 01
Exact retail unitPublic SKU, revision, U.S. voltage, acquisition path, and protected serial fingerprint.
- 02
Complete required modulesNo favorable subset can stand in for the declared product protocol.
- 03
Calibrated instrumentsInstrument identity, purpose, and calibration check precede the run.
- 04
Minimum repetitionsConditions and run order remain attached to every statistic.
- 05
Raw data + limitationsSummaries never sever the path to the underlying record.
- 06
Two-person reviewCorrections supersede; they do not silently rewrite history.
MACHINE-READABLE BY DEFAULT
Empty data is more trustworthy than invented data.
The public endpoint already exposes the schema, protocol modules, coverage, queue, and validated record array. Today that array is empty. When a physical test passes, the same endpoint becomes its durable release surface.