Skip to content

Replace personal name with neutral user wording (NAME-NUTZER) #1582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mergify merged 2 commits into from
Oct 15, 2026
Merged

Replace personal name with neutral user wording (NAME-NUTZER) #1582

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e362452
Replace personal name with neutral user wording (NAME-NUTZER)
Cuarroc Oct 15, 2026
b8bfa32
docs: fix user decision anchor
Cuarroc Oct 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/projecta-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ per provider: `docs/setup/README.md`. Check your machine with
6. Approved adaptation may change method/order/slicing/owner/location, not
requirements. Record trigger/evidence, previous state, change, remaining
acceptance duties and next owner/step in the ticket/PLAN. Preserve granted
authorizations; new scope/cost/permissions belong to Elias. Blockers need
authorizations; new scope/cost/permissions belong to the user. Blockers need
cause/hypothesis, evidence, impact and next owner/step; continue independent
approved work without blind retries or invented work.

Expand Down
2 changes: 1 addition & 1 deletion .claude/skills/projecta-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ per provider: `docs/setup/README.md`. Check your machine with
6. Approved adaptation may change method/order/slicing/owner/location, not
requirements. Record trigger/evidence, previous state, change, remaining
acceptance duties and next owner/step in the ticket/PLAN. Preserve granted
authorizations; new scope/cost/permissions belong to Elias. Blockers need
authorizations; new scope/cost/permissions belong to the user. Blockers need
cause/hypothesis, evidence, impact and next owner/step; continue independent
approved work without blind retries or invented work.

Expand Down
118 changes: 59 additions & 59 deletions docs/PLAN.md
View file
Open in desktop

Large diffs are not rendered by default.

14 changes: 7 additions & 7 deletions docs/decisions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1984,19 +1984,19 @@ wall clock, linux + windows.
Leitstand), 2, 3, 4, 5, 6 (shell part), 8, 9, 11, 13. Criterion 14 (lead
number) moves to v2.1, reason in the table in
[the v2.0 subplan](plan/v2.0/plan.md#10-enger-schnitt-vom-15102026-v20-eng-kriterien-und-restpakete).
- **Source:** Elias in the Root chat on 2026-10-15 at about 02:55 CEST,
- **Source:** The user in the Root chat on 2026-10-15 at about 02:55 CEST,
answering card E1 (the narrow or the wide reading of the cut of 2026-10-11)
with "V2.0.0 eng". Root recorded it in the SRV-V2-NARROW-PLAN order.
- **Why:** the cut already moved the screens; the acceptance criteria must move
with them, or v2.0 can never be called done. The Core, the engine and the
provider paths are large and are not part of shell plus Leitstand.
- **Reverse when:** Elias asks for the wide reading, or a moved criterion turns
- **Reverse when:** The user asks for the wide reading, or a moved criterion turns
out to be needed for the release (then it comes back with its packages).
- **Not covered:** no package content change, no date, no release approval. A
major release still needs a fresh yes from Elias (AGENTS.md rule 10). The
major release still needs a fresh yes from the user (AGENTS.md rule 10). The
remaining packages are listed in the subplan, section "10.1 Restpakete v2.0 (eng)".

## 2026-10-15 - Elias answers seven questions (v2.0 eng)
## 2026-10-15 - The user answers seven questions (v2.0 eng)

- **What:** (1) Root may pass its per-job `PA_SEAM_ALLOW` approval through
`run-job.sh` (implemented by Root at 14:00; backup and approval-file path
Expand All @@ -2010,7 +2010,7 @@ wall clock, linux + windows.
to calm. (7) Root may change roles, prompts, settings and default skills of
other ProjectA agents after making a backup; Root's own configuration is
excluded.
- **Source:** Elias in Root chat on 2026-10-15 at about 13:45 CEST, verbatim:
- **Source:** The user in Root chat on 2026-10-15 at about 13:45 CEST, verbatim:
„1. Ja 2. empfehöung folgen 3. passt so 4. passt so 5. Empfehlung folgen
6. umstellbar zwischen ruhig und lebendig, eher aber ruhig 7. Ja darfst du
vollständig“.
Expand All @@ -2019,7 +2019,7 @@ wall clock, linux + windows.
while preserving a user choice; allow Root to maintain other agents' setup
with a backup and without self-editing. The seam approval is already
implemented and is recorded here as the decision that authorized it.
- **Reverse when:** Elias changes any of these choices; restore the prior
- **Reverse when:** The user changes any of these choices; restore the prior
setting or plan only with a new explicit decision. Agent configuration
changes must first be restored from the backup if reversing item 7.

Expand Down Expand Up @@ -2106,7 +2106,7 @@ Retire a UI/server only after replacement capture/answer/inspection parity,
real source data with receipts, mobile capture and a verified backup; no idea
may be lost. This contract itself starts, migrates, exposes or retires nothing.

## 2026-10-15 - Design-system decisions D1–D7 (Root by delegation, Elias may overrule)
## 2026-10-15 - Design-system decisions D1–D7 (Root by delegation, the user may overrule)

@chatgpt-codex-connector chatgpt-codex-connector Bot Oct 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Aktualisiere den eingehenden Link auf den umbenannten Anker

Durch die Umbenennung dieser Überschrift ändert sich ihr Markdown-Anker zu #2026-10-15---design-system-decisions-d1d7-root-by-delegation-the-user-may-overrule, aber docs/plan/v2.0/plan.md:881 verweist weiterhin auf den alten ...-elias-may-overrule-Anker. Dadurch führt der D1–D7-Link nicht mehr zum Entscheidungsabschnitt und der zu entfernende persönliche Name bleibt zudem in einer aktuellen Datei erhalten; bitte den eingehenden Link zusammen mit der Überschrift aktualisieren.

Useful? React with 👍 / 👎.


- **Authority / why:** the user's delegated design-detail choices, recorded by Root in `ds-entscheidungen-20261015.md` (15:55 CEST); one consistent system for the app and Fabrik. Packages: [v2 plan §10.3](plan/v2.0/plan.md#103-designsystem-feinschliff).
- **D1:** keep shipped Inter (OFL); move `@font-face` to `src/design/fonts.css` in DS-07; no Geist download.
Expand Down
4 changes: 2 additions & 2 deletions docs/development/prompting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Rekursives Prompting

Selektiv für komplexe Pläne, viele Abhängigkeiten, schwierige Diagnosen und anspruchsvolle Entwürfe mit prüfbaren Kriterien (Elias, 08.10.2026). Ziele, Anforderungen und Abnahme bleiben erhalten; nur nötige Teilfragen bilden. `docs/PLAN.md` bleibt einziger Plan; bei Widerspruch gilt `AGENTS.md`. Keine zusätzliche Runtime, Agenten oder Hintergrunddienste dafür starten.
Selektiv für komplexe Pläne, viele Abhängigkeiten, schwierige Diagnosen und anspruchsvolle Entwürfe mit prüfbaren Kriterien (Nutzer, 08.10.2026). Ziele, Anforderungen und Abnahme bleiben erhalten; nur nötige Teilfragen bilden. `docs/PLAN.md` bleibt einziger Plan; bei Widerspruch gilt `AGENTS.md`. Keine zusätzliche Runtime, Agenten oder Hintergrunddienste dafür starten.

## Ablauf

Expand Down Expand Up @@ -49,7 +49,7 @@ Ist nach dem Push Nacharbeit nötig (Review-Befund, rote Prüfung), gilt:
- **Begrenzter Fix auf demselben Branch.** Normaler Commit (kein Force-Push/Rebase), eigenes `prepush`, Push und Remote-Beleg; betroffene Kandidatenevidenz erneuern.
- Jeder Befund steht im PR-Text unter `### Nacharbeit` als `Datei:Zeile` mit Befehl und Exit-Code. Ein Befund ohne `Datei:Zeile` zählt als unbelegt.
- Die Runde behebt nur die genannten Befunde; Neues kommt in ein eigenes Paket.
- Die unabhängigen Reviewrunden bleiben nach AGENTS.md Regel 5 begrenzt: zweite nur bei hohem Befund, danach entscheidet Elias. Selbstprüfungsrunden erlauben keine zusätzliche Fremdreviewrunde oder neue Freigabe.
- Die unabhängigen Reviewrunden bleiben nach AGENTS.md Regel 5 begrenzt: zweite nur bei hohem Befund, danach entscheidet der Nutzer. Selbstprüfungsrunden erlauben keine zusätzliche Fremdreviewrunde oder neue Freigabe.
- FLOW-05 zählt die Fixrunden je PR.

## Vorlagen
Expand Down
Loading
Loading