Everything, in order

Install it, write three files, run a job by hand, then give it a cron line.

Three primitives, in the order to reach for them, and the test for which one you are writing.

Steps, state, replay, and the one rule that makes carrying on after a pause safe.

A job stops, sends its question to whoever should answer it, and carries on when they do.

The loop, what a tool is, and what an agent may change about itself.

Putting an agent on Telegram, and writing a way in that chloe does not ship.

A job picks its own model in one line, and a call goes out by key or by subscription.

Two different things, kept apart, and four places where each one beats the last.

Code is tested, words are scored, and reaching for the wrong one wastes an afternoon.

What a run writes down, where state lives, and the login in front of all of it.

What is baked in for a single person, and the four changes that are cheap now and expensive later.

What the package publishes, and why the list is short on purpose.

Everything an agent, a job, a tool or a channel is written with.

What a model can be handed. Each one is bound by an agent.

When a job runs, written the way it is said.

How a run is marked: what it did, and what it said.

Saying whether one thing came out right, for a job's own test file.

An agent on Telegram, bound in its own channels folder.

Every setting, its default and what it does, out of the schema the code reads.