--- name: baumanagement-pl-project-jourfixe description: "Baumanagement-PL-Projekt-Jourfixe: interne Teamleiter/Projektleiter-Jourfixe transkribieren, protokollieren, ERNE-CI-DOCX/PDF erzeugen und projektbezogen in jarvis_memory ablegen." version: 1.0.0 author: Hermes Agent license: MIT metadata: hermes: tags: [baumanagement, pl-jourfix, projekt-jourfix, erne, autoprotocol, transcription, protocol, knowledge-vault] --- # Baumanagement-PL-Projekt-Jourfixe Use this skill whenever the user sends or references an **internes Baumanagement PL-Projekt-Jourfix**, **Teamleiter/Projektleiter-Jourfix**, **PL Jourfix**, **Projekt-Jourfix**, Teams recording, audio/video file, transcript, or context document and asks for transcription, protocol generation, project memory, or later retrieval. This is the dedicated workflow for recurring ERNE-style project leadership meetings, e.g. Teamleiter + Projektleiter discussing project status, risks, deadlines, costs, entrepreneurs, quality, safety, claims, and next steps. ## Relationship to other skills - Also load `pl-project-jourfix-protocols` for content rules, management summary, ampels, decisions, risks, and pendenzen discipline. - Also load `document-productivity-workflows` and its ERNE formatting reference when producing DOCX/PDF files in ERNE CI. - Load `knowledge-vault-workflows` when archiving or retrieving project knowledge. - If the meeting is a Fachplaner/FPS meeting rather than an internal PL/Baumanagement meeting, use `fps-autoprotocol` instead or alongside this skill. ## Primary outputs For a normal PL-Projekt-Jourfix request, produce and verify: 1. Raw transcription or diarized transcript when generated locally. 2. Bereinigtes Transkript as `.docx` and, if useful, `.pdf`. 3. Senior-Baumanagement protocol as `.docx` and `.pdf`. 4. Internal Markdown copies for the project knowledge vault. 5. Project archive entry under `~/jarvis_memory/work/projects//meetings/...`. If the user says **nur transkribieren**, produce only the transcript; do not infer pendenzen, decisions, or management summary. ## Source priority 1. Meeting audio/transcript = truth source for what was actually discussed. 2. User-provided participant mapping and project context = identity/role support. 3. Existing project note `~/jarvis_memory/work/projects//project.md` = vocabulary and background only. 4. Project document directory `~/jarvis_memory/work/projects//documents/` = contract, protocol, schedule, PQM/QS, address, and other project context for meeting preparation, risk radar, and legal/contractual support. 5. General ERNE knowledge `~/jarvis_memory/work/erne_wissen/documents/` = SIA/QS/Nachtrag/Kennwert background; use it as general context, not as proof of project-specific obligations. 6. Prior protocols/context documents = structure and issue continuity, not proof of what was said in the current meeting. Never invent names, deadlines, responsibilities, decisions, costs, or technical facts. Use `Unklar`, `nicht explizit festgelegt`, or `[unklar]` where needed. For Google-Drive sourced ERNE project context imports and document directories, use `references/erne-drive-project-context-ingest.md`. It defines the local `documents/README.md`, `document_index.csv`, `source_files/`, `extracted_text/`, and `ERNE_DOCUMENT_CONTEXT.md` pattern. ## Project vault structure Use this stable structure for future retrieval: ```text ~/jarvis_memory/work/projects//project.md ~/jarvis_memory/work/projects//meetings/README.md ~/jarvis_memory/work/projects//meetings/YYYY-MM-DD_/meeting.md ~/jarvis_memory/work/projects//meetings/YYYY-MM-DD_/artifacts/ ``` Examples: ```text ~/jarvis_memory/work/projects/furkastrasse/meetings/2026-06-25_interner_baumanagement_pl_jourfix/meeting.md ~/jarvis_memory/work/projects/furkastrasse/meetings/2026-06-25_interner_baumanagement_pl_jourfix/artifacts/ ``` ### `meeting.md` content Each archived meeting note must include: - YAML frontmatter: `type`, `project`, `project_number`, `meeting_type`, `date`, `participants`, `tags`, `source`. - Artifact table with relative links to DOCX/PDF/Markdown/transcript/context files. - Short context paragraph. - Management Summary. - Ampelstatus. - Entscheide. - Risiken/Chancen. - Pendenzenliste. - Retrieval hints for later user questions. ### `project.md` updates When a new meeting is archived, update the project file with: - a `Sitzungs-/Protokollablage` section if missing; - an entry in `Abgelegte Sitzungen` with date, meeting type, vault path, and key topics; - only concise durable project facts, not full raw transcript. ## Furkastrasse Webcam integration for internal BM/PL-Jourfix For project **Furkastrasse**, internal BM/PL-Jourfix protocols must include the latest locally archived Baustellen-Webcam screenshot as a current construction-status evidence block. Automation in place: ```text Cron: Furkastrasse Webcam Archivierung werktags 10:30/15:00 Schedule: 30 10,15 * * 1-5 Script: ~/.hermes/scripts/furkastrasse_webcam_capture.py Archive: ~/jarvis_memory/work/projects/furkastrasse/webcam/YYYY/MM/ Index: ~/jarvis_memory/work/projects/furkastrasse/webcam/index.jsonl Latest metadata: ~/jarvis_memory/work/projects/furkastrasse/webcam/latest.json ``` When producing a **Furkastrasse internes BM/PL-Jourfix-Protokoll**: 1. Insert the most current suitable screenshot into the protocol, normally the **previous workday 15:00** image if available; otherwise use the latest archived image and state the timestamp. 2. Add a text block directly below the webcam image titled for example: `Aktueller Stand Baustelle / Webcam-Vergleich`. 3. Compare **maximum three images** with vision: - the image used in the last previous Furkastrasse internal BM/PL-Jourfix protocol; - one representative image around the middle of the period since that protocol; - the current image, preferably previous workday 15:00. 4. If a Jourfix was skipped, compare from the last actually created Furkastrasse internal BM/PL-Jourfix protocol, but still never analyse more than the three selected images above. 5. Write concise observations on: - visible construction progress / Baufortschritt; - changes in excavation, concrete works, formwork, crane/logistics, material storage, access routes, temporary works, weather protection, visible trades/activity; - auffällige Veränderungen gegenüber den Vergleichsbildern; - Arbeitssicherheit / PSA only where visually supportable: helmets, high-vis clothing, neck protection where visible, work at height, fall protection, edge protection, access/egress, excavation safety, traffic routes, housekeeping/material storage, compliance indicators for Bauarbeitenverordnung/SUVA. 6. Be explicit about image limitations: webcam distance, occlusion by trees/masking, timestamp, weather/light, and that PSA/SUVA compliance cannot be conclusively certified from the webcam alone. 7. Do not invent violations. Phrase safety concerns as `sichtbar`, `nicht beurteilbar`, `auffällig`, or `vor Ort zu prüfen` depending on evidence. Archive the selected image paths and the short vision comparison note in the meeting artifact folder so the next protocol can identify which image was used previously. ## Processing workflow For the proven Furkastrasse Google-Drive package workflow (MP4 + Teams transcript DOCX + previous protocol context), see `references/furkastrasse-pl-jourfix-drive-workflow.md`. Use it when the user names a Drive folder such as `260701 Projekt Jour fixe`. ### 1. Locate and load context - Identify project from user message, file name, or transcript terms. - Read `~/jarvis_memory/work/projects//project.md` if present. - Read any user-supplied context document/template. - Locate ERNE CI layout template if required, e.g. a previous Mönchaltorf ERNE-CD/CI DOCX. ### 2. Transcribe For long audio/video, use the local AutoProtocol/WhisperX path where available: - Extract audio if needed with `ffmpeg`. - Transcribe with WhisperX, German language, diarization when HF token is available. - Save raw transcript `.json` and `.txt` in an output directory. - Keep speaker IDs if mapping is not certain. ### 3. Clean transcript Create a `bereinigtes Transkript`: - chronological order; - time + speaker + fachliche Aussage; - remove join/leave chatter, filler-only turns, greetings, jokes, repeated confirmations; - preserve technical statements, dates, costs, responsibilities, risks, decisions, contradictions; - mark uncertain recognition as `[unklar]`. ### 4. Create protocol Use a thematic, non-chronological 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 Typical PL/Baumanagement clusters: - Rückblick Projektteam / Bauherrschaft / Kommunikation - Projektstand und Termine - Nachträge / Baukostenindex / Controlling / BAKUS - Vergaben / Unternehmer / Subunternehmer / Werkverträge - Fertigbäder / Sanika / Nasszellen - Montage- und Logistikkonzept / Baustelle / Wetterschutz / Kran / Gerüst - Qualität / PQM / Abdichtungsdokumentation / Revisionsunterlagen / Garantiescheine - Schadenfall Nachbarschaft / Versicherung / Gutachter / Beweissicherung - Sicherheit und Gesundheit / Arbeitssicherheit - Abwesenheiten / Ressourcen / Organisation ## ERNE CI formatting When the user asks for ERNE-CI/CD layout or references a prior ERNE document: - Start from the provided/known ERNE DOCX template so header/footer relationships are preserved. - Keep ERNE logo top-left, design graphic top-right, and footer with page numbering / `www.erne.net`. - Use Arial, ERNE blue `#365294`, ERNE beige `#E2D3C4` or light beige striping. - Margins that worked: top `~2.35 cm`, bottom `~1.85 cm`, header/footer distance `~0.85 cm`. - Use full-width tables with blue header rows and alternating light rows. - Ampel/status cells should include coloured dot indicators: - `● Grün` - `● Gelb` - `● Rot` - combined status e.g. `● ● Gelb / Rot` - Generate PDF from the final DOCX via LibreOffice/headless. - Verify visually: page 1, ampels/status table, pendenzen/risks page, and final page. ## Archiving workflow After verified files are produced: 1. Create `~/jarvis_memory/work/projects//meetings/YYYY-MM-DD_/`. 2. Copy final DOCX/PDF and internal Markdown/transcript/context into `artifacts/`. 3. Write `meeting.md` with summary, ampels, decisions, risks, pendenzen, and artifact links. 4. Update `meetings/README.md` index. 5. Patch `project.md` with a concise meeting entry and any stable durable project facts. 6. Do not store raw large audio/video in `jarvis_memory` unless the user explicitly requests it; store pointers or derived text artifacts instead. ## Verification checklist Before reporting completion: - DOCX reopens and contains expected tables/sections. - PDF has expected page count, A4 page size, text extractability, and key terms (`Pendenzen`, `Entscheide`, project name). - Visual QA confirms no clipped tables, header/footer overlap, or overfilled pages. - Project archive note exists and links to copied artifacts. - Project index and project.md were updated. ## Retrieval rule When the user later asks project questions such as “was war bei Sanika offen?”, “welche Pendenzen hatten wir?”, “was ist Stand Nachbarschaden?”, or “was haben wir im letzten PL-Jourfix entschieden?”, first inspect: ```text ~/jarvis_memory/work/projects//project.md ~/jarvis_memory/work/projects//meetings/README.md ~/jarvis_memory/work/projects//meetings/**/meeting.md ``` Use the original archived artifacts only when the meeting note is insufficient or the user asks for exact wording/source detail.