> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/the-worked-examples/e5.2-nothing-generated-is-edited-by-hand.md).

# E5.2 — Nothing generated is edited by hand

In Progressa, a builder changes a label on MoEYS's form for approving an institution's new name, directly on the platform, to meet the demonstration.

**Subtopic:** 5.2 — Nothing generated is edited by hand

**Public anchor:** None of its own: the SDD method's own rule that nothing generated is edited by hand, and its read-back, stated in plain words

**Simulated case:** This is a simulated case for Progressa, a fictional country; every institution, name, date and figure in it is invented.

**What it shows.** The slides of the script of 5.2 that carry Progressa's example: 'Progressa: a label on MoEYS's form'; 'A hand edit shown up'; 'Write it into the contract'.

**Form of this example.** Taken as it stands from the script of 5.2 in the script bundle of module 5: the slides that carry Progressa's example, each with what the slide shows and what the narrator says over it. The method's step names no country; the example is filled for Progressa.

## Progressa: a label on MoEYS's form

> *Slide 5 — Title: 'Progressa: a label on MoEYS's form'. Body, four text rows: 'The form on which the minister approves a new name.' 'A label changed by hand on the platform, the evening before a demonstration.' 'The read-back: this form, edited by hand.' 'The label corrected in the goal's screens and the model; generated again; read back again.'*

In Progressa, a builder changes a label on MoEYS's form for approving an institution's new name, directly on the platform, to meet the demonstration. The read-back lists that form as edited by hand. The head of MoEYS's ICT unit asks for the change to be made properly. The label is corrected in the goal's screens and in the model, the application is generated again, and the read-back is run once more. It passes only when every file shows in step.

## A hand edit shown up

> *Slide 6 — Title: 'A hand edit shown up'. Demonstration segment, storyboard until recorded (section 4.9). Text-only stand-in until the recording exists: 'A label changed on the platform.' 'Read-back: the form, edited by hand.' 'The label corrected in the model; generated again.' 'Read-back: every file in step.'*

The demonstration shows the same steps on a generated application. A label is changed by hand on the platform, the read-back runs and names the form, the correction is made in the model, and the read-back runs again. It passes when the first run names the edited file and the second shows every file in step. Until the application is generated, this is a storyboard.

## Write it into the contract

> *Slide 7 — Title: 'Write it into the contract'. Body, three text rows: 'No generated file is edited by hand.' 'The read-back is run before every acceptance, and its list is handed over.' 'A file edited by hand is a defect, corrected in the description.'*

Put the rule into the supplier's contract, together with its evidence. No generated file may be edited by hand on the platform. The read-back is run before every acceptance, and its list is handed over with the delivery. A file marked as edited by hand is a defect, and it is corrected in the description, not argued about at the acceptance meeting.

**What to look for before you accept it.** Correct the accepted document, not the platform, and generate the application again. The read-back shows any file that someone changed by hand.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/the-worked-examples/e5.2-nothing-generated-is-edited-by-hand.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.