BeanCave — your green coffee¶
Artisan does / TilauScope adds
Artisan does — stores the coffee as free text in each roast file. Two roasts of the same bag are two unrelated strings, and nothing knows how much of that bag is left.
TilauScope adds — BeanCave: a record per green coffee, with an identity that every roast of it points back to. That identity is what makes the rest possible — stock that goes down as you roast, a roast plan that learns from previous roasts of this coffee, and a history you can read.
BeanCave is where a TilauScope setup begins. It opens from TilauScope → BeanCave, and the first time it opens it runs the first-time setup wizard.
The five tabs¶
| Tab | What it is for |
|---|---|
| Green Beans | The catalogue and the bean records. This chapter. |
| Roast Viewer | Reading back a finished roast — curve, statistics, tasting. See After the roast. |
| Roasting plan | Generating a roast plan and its PDF. |
| Stockage | How your coffee is keeping: water activity, conditioning, sack labels — see Sacks, stock and conservation. |
| File Management | Roast files: auditing incomplete ones, linking them to a coffee, exports. |
The catalogue¶
The Green Beans tab is a readable list, not a spreadsheet: each coffee on a few compact lines with its stock, its origin and its freshness.
Search — Search name, country, farm… filters as you type.
In stock — Hide out-of-stock beans narrows the list to what you can actually roast today. A coffee you have finished stays in the database, with its history intact, without cluttering the list.
Each entry carries badges that answer the questions asked when choosing what to roast: whether it is a blend, how old the harvest is — Harvest is 2 years old — and whether it is out of stock. Where sack labels are used, the labels attached to that coffee are shown too.
Note
An empty list after filtering says so — No bean matches the current filter. — rather than looking like an empty database.
The bean record¶
A record opens to be read, not to be edited. It is laid out in zones, and each zone has its own ✎ Edit dialog — so correcting an altitude does not mean re-opening a form with forty fields in it.
| Zone | What it holds |
|---|---|
| Essentials | Name, origin, crop year, stock — as stat tiles. |
| Provenance | Farm, supplier, altitude. |
| Characteristics | Type, category, process, species, varieties, density, humidity. |
| Sensory & notes | SCA score, flavour notes, roasting memo. |
| Sacks | The physical bags of this coffee, and their labels — see Sacks, stock and conservation. |
| Roasts | Every roast of this coffee. |
Each zone's edit button states what it covers — Edit name, origin, year and stock, Edit farm, supplier and altitude — so there is no guessing which dialog holds which field. Editing a zone changes only that zone: Only this section is changed. Save writes the record immediately.
Weighing and measuring from the record¶
Stock accepts a live weight: with a scale configured, clicking the ⚖ reading captures the exact figure instead of a typed approximation — With a scale configured, click the ⚖ reading to capture the exact weight.
Density can be measured the same way, from a fixed-volume container, with Measure. If no scale is set up, the dialog says so plainly — No scale configured — rather than offering a button that does nothing.
Water activity can be measured directly from the record with an AquaGauge. What the value means for storage is in Sacks, stock and conservation.
Flavour notes are entered on the flavour wheel rather than typed as free text, which keeps the vocabulary consistent from one coffee to the next.
Hardware
Live weighing needs an Acaia scale; density measurement needs a scale configured as scale 1 in Artisan; water activity needs an AquaGauge. Everything else on the record is typed.
Adding a coffee¶
Add New Bean asks how you want to start: From current fields, which pre-fills from what you have already typed, or Blank bean, which starts fresh. A full expert form follows, with required fields named up front — Fill the required fields (*): name, country, category, process, species, varieties — and the reassurance that matters when a bag has just arrived: Fill what you know — everything can be refined later from the sheet.
Blends are declared as such, with their components and ratios.
The guided way in
For a bag that has just arrived, the + New sack assistant is the better route: it walks through registering a new coffee, restocking an existing one, or opening a new crop year, and reviews everything before saving. The expert form exists for when you know exactly what you are entering. See Sacks, stock and conservation for the assistant in full.
Filling a record from the supplier's page¶
Rather than copying a dozen fields by hand, paste the supplier's URL — Enter URL of supplier here... — and TilauScope fills the record from that page, blends and component ratios included. The result is presented for review before anything is saved.
Note
This needs an AI provider configured — see Configuration. Extraction reads a web page written for humans, so check the result: it is a first draft to correct, not an authority.
The roast history of a coffee¶
The Roasts zone lists every roast of this coffee, with the total weight roasted computed for you. This is the same history the roast plan learns from, which is why keeping records attached to the right coffee matters: a roast filed against the wrong bag teaches the plan the wrong lesson.
A roast opens into the Roast Viewer — curve, key events, statistics and tasting. See After the roast for what it shows and how to read it.
Sharing and printing¶
A bean record can be exported as a landscape image sized for social networks, and so can a roast — green coffee, roast level, key figures and the curve on one card (see After the roast for the roast card).
Labels for beans, roasts and sacks print from here, each carrying a QR code that opens the corresponding record. The 📷 SCAN button reads those codes with the webcam; a phone camera works too — see Labels and QR for printing and scanning in full.
Note
Printing and scanning are optional throughout. A setup that never prints a label never sees a prompt about one.
Roast files¶
The File Management tab works on the roast files themselves: browsing the roast directory, auditing profiles with missing information, linking one to a green coffee and completing its fields one file at a time. A file is only rewritten when you press Record.
This is where a roast saved without its finishing details — after a back-to-back relaunch, for instance — is completed.
Exports live here too: roast data as CSV, a format prepared for analysis by a language model, and diagnostic logs.
Next¶
- What to configure so all of this works: see Configuration.
- Tracking bags and keeping condition: see Sacks, stock and conservation.
- Printing and scanning labels: see Labels and QR.
- Generating a plan for a coffee: see The roast plan.
- Roasting it: see Preparing a roast.