The Roastery Lab · Platform
One system, three depths
The coffee-intelligence platform behind the roastery.
Pacific Roots is the platform's first customer: the same tools that track a home brew scale up to run production. One domain model, one evidence language, one progression of work — device-local today, cloud-ready by design.
Taste · the consumer
Understand and improve your own coffee — no professional hardware needed.
For · Home brewers, learners, everyday coffee lovers
Craft · the industry
Connect real curves, profiles, sensory results, and controlled iteration.
For · Advanced home roasters, working roasters, micro-roasteries
Ops · full platform
Run production, quality, experiments, governance, and publication as one system.
For · Pacific Roots and commercial roastery teams
The depths share one domain model and one progression of work — they don't need identical screens. A Field brew and a Lab production batch are the same kind of object, seen at different resolutions.
Each instrument runs on real data the moment its capture connects — and says so plainly until then.
- T0 · AnchorsAvailable nowEvent anchors, weights, cupping, notes — the whole Field workspace runs here.Manual event log + cupping (works today)
- T1 · CurvesUnlocks with captureBean-temp / environment-temp streams and rate-of-rise — the curve diagnostics.Thermocouple BT+ET log (Artisan)
- T2 · ControlsUnlocks with captureLogged gas, airflow, and drum changes drawn under the curve.Logged gas/airflow/drum changes
- T3 · OutcomesUnlocks with captureColor meter, refractometer, and green-lot tools — measured outcomes.Color meter · refractometer · green tools
Every value on the platform declares what kind of evidence it is. A target is never dressed up as a measurement; a model is never shown as a cupping result.
Directly recorded by an instrument.
Manually recorded event or sensory judgment.
Intended specification.
Calculated from measured or observed sources.
Algorithmic estimate or simulation.
A proposed action — propose-only, never applied automatically.
A human-authorized decision.
Approved for external use.
Plus Tagged sample — demonstration data, never a Pacific Roots production batch. When capture connects, a sample instrument flips to measured, in the open.
Observation · Nightfall develops hardest (18.5%) while Coastal Fog keeps the most mass (11.6% loss) — the spread is the house style: same drum, different intents.
Evidence · First crack order: Coastal 8:02 → Summit 8:22 → Nightfall 8:58. Drop temps 402° / 412° / 427°.
Confidence · High on the numbers (production sheets); the comparison itself is descriptive, not a recommendation.
The seven reference profiles are approved house targets, transcribed from the production sheets — design intent, not a record of measured batches.
AI is a co-roaster analyst, not an autopilot. It cannot change a production profile. It must cite data, state uncertainty, and log every recommendation. Humans approve. Always.
Illustrative note · PR-SUMMIT-0001 reference
CONFIDENCE: MEDIUM
- Observation
- Batch closely matched the Summit Blend reference through first crack with minor lag during Maillard.
- Evidence
- — BT deviation < 8°F through 8:00
- — First crack at 8:22
- — Drop at 9:47
- Hypothesis
- Heat application was controlled and suitable for the target espresso profile.
- Suggested action
- Cup at days 6, 8, and 10 off roast before changing the production profile.
Illustrative — how the analyst would read a roast against the Summit reference profile. Real production batches log their own notes.
The governance rules
- Propose-only — no silent changes to production recipes
- Every recommendation cites source data
- Confidence and uncertainty stated
- Metric definitions version-controlled
- All recommendations logged
The output contract: Observation → Evidence → Hypothesis → Suggested action → Expected effect → Confidence. Human sensory judgment stays central — the analyst proposes, the roaster decides, the log remembers.
The operating layer
Powered internally by RoastOS
RoastOS is the canonical backend where the roastery's truth lives: production records, versioned profiles, capture streams, QC gates, experiments, and the audit history behind every approval. The public site is a governed projection of it — never a mirror of the raw database.
Device-local today, cloud-ready by design
Your data stays yours
The Workbench runs entirely on your device — no account, nothing sent anywhere. The storage layer sits behind a clean seam, so cloud sync, accounts, and teams can attach later without changing a single workflow. Upgrading will change where records live, not how the work feels.