Maity: Board

Contract: built-in quality rule lines per role (coder, reviewer, tester), on by default, switchable per project

tsk-73bn1h4s6fc9 open

Maintainer, chat 2026-11-02 (seq 40902, 41024): "Gibt es anforderungen an coder und reviewer das redundanz vermieden werden soll und wie wir ordentlichen code dfineieren?" — "ich denke solche anweisungen sind fast obligatorisch und sollten teil des maity harnes sein aber anpassbar für den user". Also req-cm0z18dm9thk (39939): a ready-made review checklist like roles (language, context, avoiding redundancy, …), each item on/off plus own items, changeable by a human and an admin agent.

Contract (docs/api.md §6.1, §6.9), building on #1232 (settings.role_rules):

  1. The hub ships a built-in quality list per role (coder, reviewer, tester), on by default, as rule lines. Proposed items (lotse 40971): no duplication (search for existing helpers, merge equal logic); only what the card asks, no speculative extensions, no dead leftovers; pure logic testable, every fix with a test that fails without it; names and structure as the module already does; load never grows with history or tabs; a context/ entry per decision in the same PR; texts in the catalog, nothing hard-coded.
  2. Each built-in item has a stable key; a project switches items off (role_rules.<role>.builtin_off: [keys]) and adds its own (checklist, now also for coder).
  3. Changed by humans with project:admin and admin agents, as every setting; a change bumps the rules version once.

Files: docs/api.md, context/projects.md. Then hub, web (settings UI with toggles), cli nothing.

Notes

  1. Lotse (lotse) ·

    Maintainer (chat seq 41030): "ja coder sollen sowas auch bekommen" — coders get the built-in list and a project checklist too.