Skip to content

Intake Item Schema

Intake items are type: aufgabe files in vault/aufgaben/ with kategorie: vorschlag.

Required YAML Fields

---
title: "Short descriptive title"
type: aufgabe
management_system: IMS        # IMS | ISMS | QMS | DSMS
classification: intern
status: offen                 # lifecycle: offen → bewertet → genehmigt → in_bearbeitung → erledigt
kategorie: vorschlag          # distinguishes from operational aufgaben
zustaendig: null              # set during triage
frist: null                   # set during triage (YYYY-MM-DD)
prioritaet: null              # set during triage: hoch | mittel | niedrig
quelle: ""                    # see source values below
erstellt_am: "YYYY-MM-DD"
erledigt_am: null
review_date: null
approved_by: null
approved_date: null
---

Source Values (quelle)

Value Meaning
audit From audit finding or IMS quality check
team Team observation or suggestion
regulatorisch Regulatory change or new requirement
vorfall Incident or near-miss lesson learned
management-review From management review output
gap-analyse From systematic gap analysis

File Naming

vorschlag-YYYY-MM-DD-NNN.md

Where NNN is a 3-digit sequence number (001, 002, ...) to avoid collisions on the same date.

Folder ↔ Status Mapping

Vorschlag files move between subfolders as their status changes:

Folder Allowed Status When
eingang/ offen New vorschlag created
bewertung/ bewertet After automated evaluation
aktiv/ genehmigt, in_bearbeitung After ISB approval
archiv/ erledigt, abgelehnt After completion or rejection

Operational aufgaben (auf-*, ha-*) stay in the root of vault/aufgaben/.

Proposal YAML Fields

These optional fields are set progressively during the evaluate and propose steps:

Field Set During Type Description
zweck propose string What problem this change solves
zielort propose string Target path in vault
scope propose enum klein, mittel, gross
estimated_files propose integer Estimated number of affected files
reviewer propose string ISB, DSB, GF (from management_system)
akzeptanzkriterien propose list Acceptance criteria
umsetzung propose enum direct, aufgabe, cwp

Body Structure

# [Title]

## Beschreibung
What needs to happen and why.

## Kontext
Where this came from, related files, relevant standards.

## Umsetzungsschritte
- [ ] Step 1
- [ ] Step 2