# Executing approved proposals Reached from step 4 of `SKILL.md`. The approval protocol in `/home/sascha.koenig/ap/PM/.okf/processes/it-basecamp-regeln.md` is the rule; this file is the mechanics. ## Order per item 1. Make the change. 2. Put the comment on the same object: one or two German sentences with the reason in `sascha-internal-communication-style`, then one empty line and the italic AI marker. No skill/mode/date suffix: the marker is the only trace. Example (Markdown, the CLI converts it): ```md [@Jannik Müller](person:) Neuer Termin 06.11., der Lieferant hat uns die Rückmeldung für KW 45 zugesagt. *✨unterstützt durch KI✨* ``` 3. Read the object back and check the new value. Work through the list in number order. A failing item does not stop the run: note command and error, go on, and report it at the end. ## Basecamp Mention the addressees as described under **Mentions** in `SKILL.md` (`[@Name](person:)`), so the comment notifies them. Beyond that, send no extra notifications: no `--notify`, no pings. Reminders belong to automation A3. | Action | Command (check flags with `--agent --help`) | |---|---| | Change owner | `basecamp todos update --assignee --json` | | Set date | `basecamp todos update --due YYYY-MM-DD --json` | | Comment | `basecamp comments create - < ` (stdin keeps umlauts intact) | | Move to list (same project) | `basecamp todos position --to 1 --list --json` | | Complete | `basecamp todos complete --json` | | Read back | `basecamp todos show --json` | | Create to-do (own commitment, mode `ich` only) | `basecamp todos create "" --in --list --assignee [--due YYYY-MM-DD] --description "" --json` | | Move to another project | no API call exists; create in the target project (`todos create … --in [--todoset ] --list `) with the original title, a context sentence and the original's URL, comment on the original with the new URL, complete the original | Creating a to-do is allowed in mode `ich` for Sascha's own commitment from a Sally recording (owner always Sascha), and in any mode as the second half of a project move or of parking (rule 5 of the approval protocol). The description carries one context sentence and the link to the recording or the original; the new to-do gets the same why-comment as every change. On a project move the owner may change when the approval says so; then the new owner is mentioned in the comment on the new to-do, and the requester is mentioned in the comment on the original. Projects with several to-do sets (🔁 Übergaben & Koordination, [IT] - Data Hub Analytics v1) need `--todoset ` on `todolists list` and `todos create`; IDs in `systems/basecamp.md`. The person must be a member of the target project (`basecamp people list --in `), otherwise the move is a `Für dich:` point. **Parking:** - Inside 🔒 Meins: move to the Meins backlog list (ID in `systems/basecamp.md`). - From 👥 IT or a project into 📥 Backlog / Ideenspeicher (another project; `position` cannot cross projects): create a to-do in 📥 Backlog with the original title, its context and a link to the original, then comment on the original with the link to the new item and complete it. Shown to the user as one proposal. - A whole project: `Für dich: /lead-backlog `; it runs with its own approval. **Cards** (card tables, e.g. Azubi board): comment with `basecamp comments create `; moving cards between columns is the card owner's job, so propose it as a `Für dich:` point. ## Zammad Allowed: set owner, internal note. Requires `ZAMMAD_TOKEN`; base URL from `ZAMMAD_URL`, default as in `tools/it-cockpit/cockpit.py`. Without a token, list the Zammad items as `Für dich:` points with ticket link. ```bash # owner (owner_id = Zammad user id; resolve via GET /api/v1/users/search?query=) curl -sf -X PUT -H "Authorization: Token token=$ZAMMAD_TOKEN" -H "Content-Type: application/json" \ "$ZAMMAD_URL/api/v1/tickets/" -d '{"owner_id": }' # internal note (the "why" comment for Zammad) curl -sf -X POST -H "Authorization: Token token=$ZAMMAD_TOKEN" -H "Content-Type: application/json" \ "$ZAMMAD_URL/api/v1/ticket_articles" \ -d '{"ticket_id": , "body": "

/#user/profile/\" data-mention-user-id=\"\">Vorname Nachname, Grund


✨unterstützt durch KI✨

", "content_type": "text/html", "type": "note", "internal": true}' ``` Every Zammad article this skill writes has `"internal": true` and ends with the italic AI marker after an empty line; send it as `text/html`, since plain text cannot render italics. Addressees go in as mention links (see `SKILL.md`); the note above shows the form. ## OKF Edit the concept files under `/home/sascha.koenig/ap/PM/.okf/` as approved, set `generated.at` to today, then run the `validate` skill on the bundle. Git stays with Sascha: report the changed paths.