RESTLESS
GitHub0

Intelligence is abundant.
Organisation is not.

Ten standalone technical arguments about failure, attention, context, authority, and the machinery required to turn intelligence into dependable work.

01

3 September 2026 · 18 min read

Intelligence scales. Organisations still have to exist.

Stronger models will not dissolve companies into one universal agent. They make stable responsibility, memory, and authority more important.
02

3 September 2026 · 18 min read

Human-in-the-loop runs out of human.

Continuous approvals do not preserve control at scale. They exhaust the attention required for real judgement.
03

3 September 2026 · 17 min read

Failure is a capability.

Reliable agent systems do not prevent every failure. They make attempts replaceable while preserving responsibility, evidence, and the path forward.
04

3 September 2026 · 19 min read

Context management is management.

The hard part is not fitting more history into a prompt. It is deciding what each worker should know, trust, ignore, and carry forward.
05

3 September 2026 · 16 min read

Stable structure beats intermittent brilliance.

A company cannot depend on every model call being exceptional. It needs identity, memory, and responsibility that survive ordinary variance.
06

3 September 2026 · 20 min read

The agents could work. The context could not travel.

Multi-agent systems often fail at the handoff, not the task. Restless’s own runs show how duplicated, missing, and falsely shared context corrupts good work.
07

3 September 2026 · 19 min read

A critic that thinks like the worker is barely a critic.

Adding a reviewer does not create independent evidence. Useful criticism requires a different responsibility, a different frame, or a different way of seeing the result.
08

3 September 2026 · 18 min read

One plan is not a strategy.

Productive autonomy requires the freedom to branch, test competing approaches, abandon weak plans, and recruit different skills as reality changes.
09

3 September 2026 · 21 min read

The runtime is a subsystem, not your laptop.

Giving an agent shell access is easy. Giving a company a controllable, persistent, replaceable place to work is an architectural decision.
10

3 September 2026 · 22 min read

Receipts scale where rules cannot.

Complex work cannot be made safe by encoding every good decision in advance. A few hard boundaries plus durable receipts preserve both flexibility and accountability.