PlantForge

Research Snapshot / v0.2.0-dev

What are we trying to learn right now?

01 / Vision

Plant care should not depend on perfect memory.

Plant care today is reactive. People are asked to monitor soil moisture, weather, watering schedules, fertilizer timing, and visible signs of stress, then combine those signals into a correct decision.

PlantForge explores an AI-first approach that predicts needs before plants become stressed. The goal is not a denser dashboard. It is a quieter relationship with plant care, where the system converts context into a small number of timely, trustworthy actions.

02 / Friction Inversion

Move the burden from memory into the system.

PlantForge treats plant care as an experience-design problem. Instead of adding reminders to a workflow that already demands too much interpretation, it asks what the software can remove.

PlantForge continuously reduces cognitive load through prediction, context, and recommendation. Monitoring is an input to the system, not a responsibility passed back to the user.

03 / Core Principles

Quiet intelligence over constant attention.

04 / Architecture

Signals become context, then action.

The architecture separates sensing, local coordination, intelligence, and experience. Hardware can evolve without changing the product promise.

Architecture placeholder. Future versions will expose data contracts, transport protocols, local inference boundaries, and service responsibilities.

05 / System Components

A platform, not a sensor.

06 / Prototype Build

Build the smallest system that can test the hypothesis.

The v0.1 build is an observation rig, not an automated watering product. Its job is to collect a trustworthy moisture signal, pair it with environmental context, and create enough history to test whether prediction can remove decisions.

Prices checked July 25, 2026. Purchase links use Adafruit when the exact part is available there. Other links go to the manufacturer. These are not affiliate links. Availability and pricing can change.

07 / PlantOS Code

Code now. Connect hardware later.

PlantOS begins as a simulation-first software core. Virtual sensors let us define trustworthy data, recommendation behavior, and experience boundaries before the first probe arrives.

// Virtual today. Physical later.
const scenario = {
  ...DEFAULT_SIMULATOR_SCENARIO,
  seed: 42,
  durationHours: 72
};

const run = simulate(scenario);

for (const observation of run.observations) {
  process.stdout.write(`${JSON.stringify(observation)}\n`);
}

cd plantos
npm.cmd install
npm.cmd run simulate -- --hours 72 --seed 42
npm.cmd run typecheck
npm.cmd test

07A / Interface Design

Design the calm before the hardware arrives.

PlantOS Touch UI v0.1 turns the coded display preview into a reusable Figma component system. The purpose is to validate the experience, touch targets, and decision hierarchy while the system still runs on deterministic research data.

The Friction Inversion Design Loop keeps the product brief, component choices, rendered interface, and review evidence in agreement. It is the working method for material PlantOS interface changes.

Open touch-screen preview

07B / Figma Handoff

One vocabulary from design to PlantOS.

This space defines the Figma file structure and import boundary for PlantOS Touch UI v0.1. Variables can enter Figma through the existing token-import pattern. Components and editable screens remain a deliberate design-library build.

Recommended variable namespaces: color/base, color/surface, color/text, color/status, space, radius, and size/touch/min. The minimum touch-size value is 44.

Open Figma handoff spec

07C / Pre-hardware Sprint

Prove the product before the parts arrive.

The first PlantForge sprint builds software evidence, design decisions, and installation discipline before sensor noise can obscure the work.

07D / Display Emulator

Rehearse the decision before it reaches a person.

This interactive prototype turns deterministic PlantOS scenarios into the calm, explainable display we are building toward. It is a research model, not a connected plant dashboard.

Open touch-screen preview

08 / Friction Inversion Cycle

PlantForge is the first live methodology test.

The FI Cycle tracks more than what PlantForge removes. It records where the work moves, who carries it, which signals reveal new pressure, and when the system must be rebalanced.

09 / Research Timeline

Evidence before automation.

10 / Architecture Decision Records

Decisions remain visible and revisable.

11 / Roadmap

From first principles to quiet automation.

12 / The Cultivation Log

The engineering notebook inside the whitepaper.

The Living Whitepaper explains what PlantForge is. The Cultivation Log documents how PlantForge became what it is.

Future Hooks

Designed to become a live system record.