# Furkastrasse PL-Projekt-Jourfix – Drive-folder workflow

Use this reference when the user says they placed a Furkastrasse **PL Jourfix / Projekt Jour fixe** package in Google Drive (typically MP4 recording + Teams transcript DOCX + previous protocol context).

## Trigger

User wording like:

- `Furkastrasse PL Jourfix protokoll`
- `260701 Projekt Jour fixe`
- `Videoaufnahme als mp4, Transkript als docx, Protokoll von letzter Woche als Kontext`

## Source handling

1. Locate the Drive folder with `gog drive search '<folder name>' --json --no-input`.
2. List files with `gog drive ls --parent <folder_id> --json --no-input`.
3. Download all relevant files:
   - current MP4 recording;
   - current Teams transcript DOCX;
   - previous PL-Jourfix protocol/context DOCX/PDF.
4. Extract DOCX text separately for:
   - current Teams transcript;
   - prior-context protocol.
5. Extract MP4 audio with ffmpeg to mono 16 kHz WAV.
6. Transcribe audio with faster-whisper/WhisperX if available; use German language and preserve timestamps.

## Content synthesis

- Current MP4/audio + current Teams transcript are the truth source.
- Previous protocol is only continuity/context; carry forward only if current meeting confirms or updates it.
- Cluster thematically, not chronologically.
- Keep leadership/baumanagement relevance visible: Termine, Kosten, Vergaben, Nachträge, Risiken, Qualität/PQM, Arbeitssicherheit, Eskalation, Pendenzen.

## Preferred PL-Jourfix structure

Use the established internal BM/PL structure:

1. Kopfdaten
2. Teilnehmende
3. Management Summary
4. Ampelstatus
5. Traktanden / Protokoll
6. Termine / nächste Meilensteine
7. Entscheide
8. Offene Fragen
9. Risiken und Chancen
10. Pendenzenliste
11. Punkte für nächste Sitzung
12. Unklare oder widersprüchliche Punkte

Ampel cells should use the coloured-dot wording pattern:

- `● Grün`
- `● Gelb`
- `● Rot`
- `● Gelb / Rot`

## Furkastrasse topics to recognise

- Dachdecker-Vergabe / Mayat / Bollinger / Rahmenvertrag
- Sanika / Fertigbäder / Duschtrennwände
- Nachträge / Baukostenindex / Rekursnachtrag / Adrian / Monika / Kalkulation
- Betonfertigteile / Spörgin / Blaser / Larissa / Fabian / Auflager / Plattendicke
- Montage-/Logistikkonzept / Meier Transport / Lukas Berger / Stefan Fritsche / Projektwerkstatt / Daumenkino
- Sika/FREI Abdichtungsdokumentation / QS / Revisionsunterlagen
- Bauqualität / Beton / PQM / S+G / Nackenschutz / Seitenschutz
- Nachbarschäden / Markus Iff / Solenthaler
- Projektzugriffe / Trimble / Robin / Michel Gerber

## DOCX/PDF production

- Use the ERNE/Mönchaltorf CI template or latest user-approved ERNE protocol template.
- Generate both protocol and cleaned transcript DOCX/PDF.
- Verify:
  - DOCX reopens and has expected tables;
  - PDF is A4 and text extractable;
  - rendered page 1, status/ampel page, and last page have no header/footer collision, clipped rows, or unreadable tables.

## Archive

Archive under:

```text
~/jarvis_memory/work/projects/furkastrasse/meetings/YYYY-MM-DD_interner_baumanagement_pl_jourfix/
```

Include in `meeting.md`: summary, ampels/critical status, key pendenzen, artifact table, retrieval hints. Update project `meetings/README.md` and `project.md` meeting index.

## Pitfalls

- Do not let prior-week context overwrite the current meeting.
- Do not guess responsibilities or deadlines; use `Unklar` / `nicht explizit festgelegt`.
- Keep raw transcript artifacts internal; the user-facing protocol should be the polished leadership document, not a chronology.
- If the user later provides an optimized DOCX, treat that edited document as the new formatting/wording reference for future PL-Jourfix outputs.