DSC-BRAIN USER GUIDE · HOW IT WORKS

Journals, reminders and the grow record

The four journal layers, frozen snapshots, typed actions and custom actions, photos on disk, reminders anchored to entries, retention, export and the archive written on retire.

  verified for 9.0.0 · firmware train 8.2.0.0

  last verified 2026-09-17 · mirrored 2026-09-15

Four layers, read-time roll-up

Plant → tent (4×8, 2×4) → room → DSC-Core (the facility). Each is its own table on the Pi; a tent view rolls up its plants at read time, nothing is copied. The grow log is a separate operational stream: settings changes, lamp roll-ons, rule firings, shots, soil tests.

Frozen snapshots

Every entry stores a snapshot of the sensor state at write time. Built-in actions always snapshot; a custom action can opt out. That snapshot is what Trends and Compare read, so history survives later calibration changes.

Actions

Built-in: Note, Water, Feed, Flush, Transplant, Defoliate, Train, Top / prune, Flip to flower, Pest / issue, Harvest, plus Weigh-in, Dry check, Jar up, Burp, Source water test, Reservoir mix, IPM scout, Sanitation, Quarantine check and Procedure, each with typed fields (litres, EC, pH, weights, counts). A Water or Feed entry that carries both input and runoff EC or pH shows the shift on its line (for example runoff EC +0.6 vs input). The composer offers typed actions on plant scope; tent entries from the dry, cure and procedure tools are typed by the brain. The dashboard has no editor for custom actions on this release.

Photos

Attached after the entry saves. Stored on the Pi under the media root with content-hash names (a duplicate is stored once), downscaled on the Pi, counted in the storage card, pruned with the journal. Photos show on plant, tent, room and facility entries alike. Twin clips (the director's tour, GIF exports) are stored as recorded, never downscaled, up to 24 MB each. Tent cameras add their own: a daily photo, and the frame on stage changes, critical alerts, harvests and flips (see Cameras — viewing frames and timelapses).

Reminders

A reminder is a cadence anchored to the last matching entry in the matching scope, not to a clock. Logging the entry resets it; snooze moves the card and never counts as done; nothing actuates. Add one from the Reminders card on a plant's or tent's journal on Logs (Water, Feed, Flush, Note, and the tent routines such as IPM scout, Burp or Sanitation). Due reminders are REMINDER cards on Alerts.

Runs: harvest closes the tent's run

When the last growing plant in a tent is harvested (a Harvest entry on each plant seated in it), the tent journal gets a closing entry with a frozen snapshot and the camera's frame, and the run is closed. Everything after it belongs to the next run. On Logs, a tent opens on This run; Whole history shows every run. A harvest that leaves other plants growing keeps the run open. Nothing is deleted or archived by a close.

Settings changes are journaled

Every settings write becomes a Core entry tagged with its domain, so who changed what, when is answerable from Logs › Settings changes and the Developer card.

Retention, export, archive

  • Per-journal retention days (0 = indefinite) with a preview-then-confirm prune.
  • Export as JSON, CSV or a ZIP with media.
  • Archive: retiring or harvesting a plant writes a grow-record bundle before its journal is subject to retention. A download-before-delete confirm guards deletes.

DSC-Brain user guide · Journals, reminders and the grow record · this page is edited on the site; the Notion original was retired after the mirror