# Furkastrasse FPS – user-approved protocol rules

This reference captures the correction from the user after the first Furkastrasse FPS 29 generation.

## Core lesson

For Furkastrasse **Fachplanersitzungen (FPS)**, do not produce a generic management-summary/ampel/risk protocol. The project already has a running protocol series. Use the established Furkastrasse FPS protocol structure and the latest user-optimized DOCX as the style reference.

## Mandatory structure

1. Genehmigung Protokoll
2. Infos von Bauherrn / BauKo-Sitzung
3. Stand der Planung / offene Sachfragen
   - Architekt
   - Holzbau
   - Bauingenieur
   - Haustechnik
   - Elektroingenieur
4. Stand der Ausschreibungen
5. Termine
6. PQM, Q-Schwerpunkte Fachplaner
7. Pendenzen- und Beschlussliste
8. Infos an Bauherren / BauKo-Sitzung
9. Abwesenheit / Stv.
10. Nächste Sitzung

## User-approved reference

Latest edited reference document:

```text
~/jarvis_memory/work/projects/furkastrasse/meetings/2026-07-01_fachplanersitzung_29/artifacts/260701_Furkastrasse_Protokoll_29_Fachplanersitzung_user_optimiert.docx
```

Use it for future Furkastrasse FPS wording/layout when available.

## Client-facing protocol source rule

Do **not** mention in the final FPS protocol:

- Transkript / Teams-Transkript
- Videoaufnahme / MP4
- Audioaufnahme
- Whisper / AutoProtocol / KI
- Protokollbasis / Quelle der Erstellung

Do not list transcript or video as Beilage. These are internal working/source artifacts only. They may be archived in `jarvis_memory` and used for traceability, but must not appear in the protocol that the user sends onward.

## Workflow checklist

1. Download/read MP4, Teams transcript, and prior protocol context if provided.
2. Use MP4/transcript as internal truth source.
3. Draft the FPS table in the established Furkastrasse order.
4. Remove smalltalk and non-technical remarks.
5. Remove all source/protocol-basis references from the client-facing DOCX.
6. Generate PDF from final DOCX.
7. Verify by searching exported text for forbidden source words: `Transkript`, `Video`, `MP4`, `Audio`, `Protokollbasis`, `AutoProtocol`, `Whisper`.
8. Archive internal sources separately in project memory.

## Pitfall to avoid

A polished protocol that contains the right technical content can still be wrong if it uses the wrong *protocol genre*. Furkastrasse FPS is a formal continuing FPS protocol, not a leadership/management status report.