Function page template

Copy the block below into a new file src/content/docs/en/<module>/<slug>.md. Leave a section empty if there is nothing yet — don’t delete the heading, so the next person sees what is missing.

See a completed page: Repair / Rework.

---
title: "<Function name exactly as in the menu>"
description: "<One sentence: what the function does>"
module: MES
status: draft
flow: mes/<slug>
brd: "<BRD file name or empty>"
owner: "FC project BA"
---

## Links

| Layer | Where |
| --- | --- |
| Standard flow | <flow site link> |
| BRD (official basis) | `<file name>` — repo `clt-fine-chemical`, folder `<…>` |
| UI prototype | <link> |

## 1. Purpose & scope

<What problem, how the function solves it.>

**In scope:** …

**Out of scope:** …

## 2. Roles

| Role | Work |
| --- | --- |

## 3. Main flow

| # | Step |
| --- | --- |

## 4. Status lifecycle

| From | To | Condition | Done by |
| --- | --- | --- | --- |

## 5. Business rules

| Code | Rule |
| --- | --- |
| BR-XX-01 | |

## 6. Fields, validation & messages

| Label on screen | Type | Rule |
| --- | --- | --- |

| Situation | Message (verbatim) |
| --- | --- |

## 7. Dev notes

<APIs, tables, edge cases, where the real system differs from the design. State source + date.>

## 8. Test notes

| Code | Precondition | Action | Expected result | FR / BR |
| --- | --- | --- | --- | --- |

## 9. Settled decisions

| Code | Decision | Status |
| --- | --- | --- |

## 10. Open questions

| Question | Ask whom | Blocking level |
| --- | --- | --- |

Blocking level: High = Dev cannot settle the design or data · Medium = one branch/one rule · Low = label, display.