Status scaffold – nothing here is drafted · Life living · Reader you, about to build the machine the agents run on

How to build the machine the agents run on¶

a development box, a session multiplexer, and a network, each chosen from a requirement rather than from preference

The worked example throughout is the example system.

What is in this folder¶


This guide	What the process is, why it is shaped this way, and what good output looks like. Written for you
`prompt.md`	The instruction set to paste into an agent session. Written for the agent
`templates/`	Skeletons for every file the process produces. Copy the directory

Read this once. Use the prompt every time.

Draft order: 9th. See PLAN.md section 10.

[the artefact, and what it is for. If it is a document written to open a conversation rather than close one, say so here]

[figures, dated, re-read from source. Or "not measured" said plainly]

[the sections, as a map, with what happens in each]

Agent … · You …

[what to do]

Worked example.

[the actual thing, on the example system]

Agent … · Participant … · You …

These are yours to run, on the agent's output. Do not ask the agent whether its own work was good.

[the gaps, the proxies, the principles still unmet]

redmoor_infra/docs/devbox.md — the specification, the sizing evidence, the containment argument, the rejected alternatives, and the price correction.
redmoor_infra/ansible/group_vars/devbox.yml — the multiplexer version and pinning, the service definition, the memory ceiling, the network configuration.
redmoor_docs/deep_dives/20260815_CI_Cost_And_Remote_Development.md — the research behind it.