What it will not tell you it can do

A list of honest limits is worth more than a list of features, and it is far cheaper to verify.

It is not autonomous by default.

Nothing runs on its own unless a person switches it on. Automatic enrichment stays off, because turning it on begins spending while nobody is watching — and that stays an owner’s decision.

It does not act consequentially without asking.

Reading is allowed. Anything that changes something outside waits for an explicit yes, and work running unattended can hold fewer rights than a person sitting in front of it.

Good retrieval cannot rescue thin material.

A careful system over weak material still produces weak evidence, which is why so much attention goes to what is allowed in before any of it is celebrated.

The map is extracted, not verified truth.

Its connections are inferred and tied back to evidence — inspectable and disputable, but not the same thing as facts a person has personally checked.

Self‑hosting creates real responsibility.

The machine is yours, and so is the recovery problem. Backups make recovery possible; they do not make it automatic.

Every figure in this book is a snapshot.

Numbers describe one installation on one day. They demonstrate behaviour, not a fixed specification, and they have moved since.

These limits are not disclaimers added at the end. They are the reason the rest of this book is worth reading — a description of a system that claimed no boundaries would be describing something else.