# 06 — Safety, heartbeats, budgets, and staying in control

The home lab runs agents that can spend money and touch files. This lesson is
about staying in control — the most useful habit to learn.

## Heartbeat

A **heartbeat** is a regular check-in. On each heartbeat, an agent:

1. picks up assigned work,
2. works on it (may use tools, write files, call models),
3. reports results back,
4. gets tracked (cost, started/finished).

List heartbeats (read-only):

```
cd /mnt/datapool/hermes_workspace/projects/paperclip-learning
./scripts/status.sh heartbeats
```

Heartbeats are "the clock" of the company — they decide how often work gets
done. A paused agent with no heartbeat does nothing, which is a good way to
safely stop work.

## Budget = a spending cap

An agent has a **budget** — a limit on what it may spend (model calls / tools).
This is your safety net against runaway cost. Check costs:

```
./scripts/status.sh budget
```

(If your company shows $0 budget or no spend, that's normal for a fresh lab.)

## Approval gates = the pause button

Admins (you) approve before important work ships. That's the manual control: an
agent can do a *lot*, but the boss decides what's accepted. When in doubt,
**leave approvals pending** until you want them done.

## Staying safe with the learning company

This project is practice, so a few ground rules:

- **Prefer read-only commands** (`status.sh`, `doctor`, `list`, `get`, `dashboard`).
- **Label anything you create** TEST so it's obvious and clean-up-able.
- **Pause rather than delete** when unsure — pausing a hire is reversible and stops it doing anything.
- **Never create a company/agent in a way that duplicates** what the workgroup project already built (ndyinc, Wind Sculpture Agent). We're learning *how*, not making copies.
- Use `scripts/practice-run.sh` for hands-on runs — it's built to be safe and logged.

## The habit that keeps you safe

**Before running anything that changes state, ask: "What will this change, and
how do I undo it?"** If you can't answer, use `--help` or ask Hermes. That single
habit protects a home lab better than any policy.

## Try it

Run the read-only snapshot and look at budget + heartbeats:

```
./scripts/status.sh budget
./scripts/status.sh heartbeats
```

Then move to `docs/07-your-own-org.md`.
