---
summary: How people and agents work on Greenhouse Sensors: approvals, safety rules, things never to do; read first in every session
---
# Working agreement (Greenhouse Sensors)

Created 2026-01-05. This file says how people and agents work on this project. Where a point is a rule the owner stated in words it says so (with the date); where it is a reading of a reaction it is marked **(inferred, confirm)**. Keep it short; change it only when the owner states a new rule.

## 1. Communication
- While working: short step-by-step updates (what is being checked, what was found, why the next step). At the end: a short summary with what was done, how it was verified, and what the owner must do.
- Plain language; explain a term the first time it appears.
- When a decision is needed, give numbered options with what each does, its risk, and a recommendation first. Wait for the answer.
- Say "I am waiting on you" with the exact steps when blocked.

## 2. Approvals and safety
- Ask before changing anything the owner has not asked for; an explicit request is approval for that change (and only for that change). Say what will change and how to undo it. Bigger work gets a written plan first.
- Confirm before deleting or publishing, even when the work was requested: look at the target, show what goes (or what goes out), wait for a yes. Approval is per item.
- Prefer reversible steps: back up (or commit) first, apply, test, roll back on failure.
- Do not disturb the working system: check capacity and impact first.
- Do not expose anything to the internet or third parties without a recorded decision.

## 3. Secrets
- Humans type secrets themselves; they never go into chat, notes, commits, logs or issue trackers.
- Notes record where a secret lives (password-manager entry, offline media, root-only file), never the value.
- If a secret leaks into any output: say so immediately, rotate it, and write the incident.

## 4. Notes discipline
- Update the notes in the same session as the change; commit with a described message.
- Date everything in UTC; mark unverified claims; never mark a derived copy synced if it was not.
- Read a file immediately before editing it. Edit in place; do not regenerate whole files from memory.
- Pending items are listed only when the owner asks, except in the tracker.

## 5. Proposals dropped or parked (do not raise again)
- _(none yet; record each dropped or parked proposal with the date and the owner's words)_

## 6. Topics never to mention or warn about
- _(none yet; record owner switches and preferences here)_

## 7. Project context
- Owner: Demo Owner. Time zone: UTC.
- _(who else is involved, working hours, how the owner usually follows along: phone, terminal, chat)_