Status scaffold – nothing here is drafted · Life living · Reader you, about to design the system and record the decisions

How to design the system and record the decisions¶

an architecture description, the zones and their boundaries, and one recorded decision per choice that was genuinely open

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: 8th. 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]

platform/docs/spec/02_solution_design/ — 00_overview, 01_building_blocks, three zone documents, 05_crosscutting, 05a_data_model, 06_runtime, 07_deployment.
platform/docs/spec/04_workflows/ — fourteen workflows, each interrogated.
platform/docs/adr/ — the decision series.
platform/docs/architecture/ — zone crossings, drift detection, observability, CI verification identity, zone runtime.
redmoor_docs/deep_dives/ — ten dated research notes. The README line "Not decisions — those graduate to ADRs" is the rule worth lifting.
redmoor_docs/README.md — the specification move, and the reason for it.