Skip to content

Status scaffold – nothing here is drafted · Life living · Reader you, about to get from an information architecture to a handover specification

How to get from an information architecture to a handover specification

an IA built by interview, a design system derived from it, working prototypes, and a handover specification a build can be run from

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: 4th. See PLAN.md section 10.

Context

What you are producing

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

What you need before you start

What it costs

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

Who does what
You the operator
The agent
The participant

The shape of the work

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

1 · Set up

1.1 · [step]

Agent … · You …

[what to do]

Worked example.

[the actual thing, on the example system]

2 · [the process]

2.1 · [step]

Agent … · Participant … · You …

Evaluating the quality

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

What's not solved yet

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

Source material

  • platform/docs/ux/ia_method.md — the loop, the habits, the anti-patterns.
  • platform/docs/ux/ — the area deep dives and the master map.
  • platform/docs/DESIGN.md — the chain, the six places, and the landing note admitting fourteen of its own citations resolved to nothing for a month.
  • platform/docs/design/design-handover-spec.md — the shape every handover is written against.
  • platform/docs/design/README.md — the delivered areas, and the redirect exception.
  • platform/docs/design/console-*.md — the flat files that predate the spec, and the rule that a second handover must not land beside them.
  • platform/packages/design-tokens/, *-ui/, storybook/.
  • platform/tools/design-diff/ — the recovery tool, and why it should not need to exist.
  • redmoor_docs/prototypes/ — the working prototype the domain model came from.

Open

  • [what has to be decided before this can be drafted]