**Comments** (Basecamp comments, Zammad internal notes): load `sascha-internal-communication-style` and write the German text in that style. End every comment with one empty line and the AI marker in italics, exactly:
```md
<Kommentartext>
*✨unterstützt durch KI✨*
```
Show the comment in the proposal exactly as it will be posted, marker included.
Use the Sally MCP tools (`search_appointments`, `get_recordings`, `get_summary`, `get_transcription`; read each tool's schema for its arguments). List Sascha's ~5 most recent recordings (title, date) and let the user pick; default to the newest.
Fetch the full transcription and Sally's summary. Sally's summary and task suggestions are raw material; the transcript is authoritative. For a long transcript, hand extraction to a subagent if the harness offers one: ask for goals, decisions, next steps, action items (task / owner / deadline), open questions, risks, links, in German, one line each.
**Done when** you hold the transcript-grounded notes and the meeting date, title and participants.
### 2. Settle the project
Match the recording title against the Sally search terms in `meeting-runden.md`. On a match, propose that round's filing project and let the user confirm in one word. Otherwise ask, offering a shortlist from `basecamp projects list --json` (names matching participants or keywords) plus free text.
**Done when** the user has confirmed a project and you hold its numeric ID.
### 3. Draft and clarify
Fill `assets/template.md`. Keep every header, emoji and section exactly; write German in the meeting's tone.
- **Header block:** from recording metadata. Protokoll = the assistant unless a note-taker is named. Bezug = the chosen project. Every header line keeps its two trailing spaces (Markdown hard break); without them Basecamp collapses the header into one line.
- **Ziel:** from the opening minutes, the stated purpose.
- **Kurzfazit:** 3–5 sentences covering the three bullets (Erkenntnis / Entscheidung / offener Punkt).
- **Entscheidungen:** only what was actually agreed, with context and scope; leave the list minimal when nothing was decided.
- **Nächste Schritte** (higher-level follow-ups) vs. **To-dos** (concrete assigned actions): each item lives in exactly one of the two.
Speech-to-text garbles names and jargon: mark every doubt as `[unklar: …]` while drafting, then ask the user about all of them in one batch and apply the answers.
**Done when** the draft holds zero `[unklar]` markers.
### 4. Post the document
Posting is the expected next action; go straight ahead without a "should I post?" gate. Fixes after posting happen by updating the document.
1. Find the `Meetings` folder in the project (`basecamp files list --in <project> --json`); create it if missing.
2. Create the document `YYYY-MM-DD – <Meetingtitel>` (meeting date, never today's) in that folder with `--no-subscribe`. Pass the long Markdown from a temp file in the scratchpad.
3. Read it back and keep its URL.
**Done when** the document is readable in Basecamp and you have its URL.
### 5. Propose, approve, create
Draft one to-do per item in "📌 To-dos" and "➡️ Nächste Schritte" (skip when both are empty), following `it-basecamp-regeln.md`:
- **Title:** verb first, actionable.
- **Description:** why it matters, definition of done, dependency, link to the summary document.
- **Owner:** exactly one, resolved to a Basecamp person ID via the OKF profiles or `basecamp people list`.
- **Due date:** always one. A deadline named in the meeting is resolved against the meeting date; otherwise propose a date and label it `Vorschlag`.
- **List:** the best existing list. In 👥 IT one of the six rule lists. Where no list fits, say so and propose the closest one; list creation is reserved for the Friday close.
Add, under the same approval, a proposal "als OKF-Decision anlegen?" for each decision whose reach goes beyond this meeting.
Present everything as one numbered list (title, owner, due date, list, description). The user approves as a batch, drops items by number, or edits single items. Act on an explicit answer only.
Create the approved to-dos (`basecamp todos create … --assignee <id> --due <date> --list <id> --in <project> --json`). Write approved decisions as `type: Decision` concepts in `/home/sascha.koenig/p/PM/.okf/decisions/` with `status: draft`, source `sally://recording/<id>`, and a link to the summary document; validate the bundle with the `validate` skill.
**Done when** every approved item exists and you report: document URL, to-do URLs, OKF files, and any ID mismatches from the sources-of-truth check.
## Guardrails
- Every decision, owner and deadline in the document traces back to the transcript.
- The project is always confirmed by the user, even when a round profile suggests it.
- Every to-do carries context; a bare title is incomplete.
- To-dos and OKF decisions wait for explicit approval; the summary document does not.
## Template refresh
`assets/template.md` is a local copy of the Basecamp document "📝 Meeting-Zusammenfassung" (project 👥 IT- und Projektabstimmung CZ/DE `47617617`, document `10159592734`). Refresh it only on request by re-fetching that document.