> 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/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks.md).

# Module 5 — Generate the service on a low-code platform and connect the blocks

Generation on the platform; no hand edits; the platform's traps; identity and registries; the registration contract and the data interface; payments and information mediation.

**Written for:** the team that has the service specified and built (Architect register). **Videos:** 7.

**What it teaches.** Generation on the platform; no hand edits; the platform's traps; identity and registries; the registration contract and the data interface; payments and information mediation; the proof on the running system.

**What you can do afterwards.** Read what is generated, why nothing is edited by hand, and how the service uses identity, registries, payments and information mediation.

**What it uses of the worked example.** The two applications as they will be generated on the low-code platform, with the ministry reading the register across the data interface.

## Subtopics

| #                                                                                                                                                                                                                    | Subtopic                                                                   | Class         | Demonstration | Single message                                                                                                       |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | ------------- | ------------- | -------------------------------------------------------------------------------------------------------------------- |
| [5.1](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.1-from-one-file-to-a-running-application.md)                                   | From one file to a running application                                     | Core          | Yes           | The kit turns the model into the platform's forms, lists, menus and workflow, and installs them.                     |
| [5.2](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.2-nothing-generated-is-edited-by-hand.md)                                      | Nothing generated is edited by hand                                        | Core          | Yes           | A correction goes into the description and the application is generated again; a program shows any hand edit.        |
| [5.3](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.3-the-platforms-traps-caught-before-deployment.md)                             | The platform's traps, caught before deployment                             | Core          | —             | What is known to fail on the platform is checked before anything is installed.                                       |
| [5.4](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.4-identity-and-registries-use-the-block-do-not-rebuild-it.md)                  | Identity and registries: use the block, do not rebuild it                  | Core          | Yes           | The service takes a person's identity and an institution's record from the body that keeps them.                     |
| [5.5](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.5-the-services-contract-with-the-registration-block-and-its-data-interface.md) | The service's contract with the registration block, and its data interface | Core          | Yes           | The contract another system reads is produced from the description, not written beside it.                           |
| [5.6](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.6-payments-and-information-mediation-as-named-crossings.md)                    | Payments and information mediation as named crossings                      | Supplementary | —             | A payment or a call across the data exchange is a crossing the architecture names, not a block the service rebuilds. |
| [5.7](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.7-proof-on-the-running-system-a-task-a-person-finishes.md)                     | Proof on the running system: a task a person finishes                      | Core          | Yes           | The last check is a person finishing a real task on the running service, and the record that they did.               |

**Self-check.** [Four questions on what a manager decides](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/self-check-module-5.md), with the answer the module gives to each.

{% hint style="info" %}
The reference pages hold what every module uses: [the twelve documents](/experience-digital-transformation/building-block/the-twelve-documents.md), [the blank instruments](/experience-digital-transformation/building-block/the-blank-instruments.md), [the worked examples](/experience-digital-transformation/building-block/the-worked-examples.md), [the frameworks and standards](/experience-digital-transformation/building-block/frameworks-and-standards.md), [the public sources](/experience-digital-transformation/building-block/the-public-sources.md), [the standings of the method's standards](/experience-digital-transformation/building-block/the-standings-of-the-methods-standards.md), [the glossary](/experience-digital-transformation/building-block/glossary.md) and [the figures](/experience-digital-transformation/building-block/figures.md).
{% endhint %}


---

# 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/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks.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.