Plain English for the wiki text written since 2026-09-15 Shorter sentences and common words in the pages which changed after story 1240. Headings, keys, code and links stay as they were. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BMPbYLKJQXaj22EoiKBWCR
docs: a user task which names nobody takes the names of a later report Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013W9gz28Fcj7ktuiY1j5hS9
docs: the report which creates a user task says who sees it Organizing user tasks, Security and Migrating from version 1 now say that the assignee, the candidates and the excluded users are set by the report which creates the task, that only the cockpit changes the assignee and candidate users afterwards, and that admittedUsers is read from every report. Handing work to others means ending the task and entering it again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013W9gz28Fcj7ktuiY1j5hS9
Security: an own guiHttpSecurity keeps the renewal filter Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013W9gz28Fcj7ktuiY1j5hS9
Security, Configuration: a login is renewed while it is used Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013W9gz28Fcj7ktuiY1j5hS9
docs(wiki): a live update reaches only the browsers it concerns Security gets a section on who gets which live update: the rule of the lists, the memory of what a tab shows, the reload, and a stream which ends with its login. Configuration lists the two new keys of gui-sse, and Architecture says how the filter reads MongoDB once per tick. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NKS6QGVrHPLN1gPhyW6cw9
An admission holds against an exclusion Stephan decided that a user named in admittedUsers sees the task even when the same task excludes them. Four eyes do not suffer from that: the first pair of eyes should never be handed the second task at all, and if the task did reach them, the workflow module's own security keeps the form shut. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
A user task may name who else sees it The access rule of the cockpit gains a fourth reason. A workflow module writes admittedUsers on a user task, and whoever stands there reaches the task without being a candidate and keeps reaching it after their groups change. Security says where the field sits among the others and that only the main list carries it. Reporting workflows and user tasks says how a details provider fills it and who decides what an admitted reader sees. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Take back what story 258 wrote, its way is not the one we take The rule that a task you opened stays visible is not built in the cockpit any more. A workflow module will name who else may see a task, so there is no collection here, no setting on four levels and no gap to warn about. Story 260 carries it, and the pages come back with it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say where the rule stops, and what a module cannot tell The rule holds the list and what the cockpit stored. The form behind it belongs to the workflow module, which decides for itself what it shows. And it decides blind: a module cannot tell that it is asked because of an earlier view, so a request its own API would refuse can still reach a form. The cockpit hands over no reason and the module cannot ask. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
A task you worked on stays yours Says what somebody still sees after the group which brought them a task is taken away, which keys switch it off, and that the upgrade changes what users see without anybody configuring it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
A single task is answered by the rule of its list The gap this page named is closed for the user task and the workflow module: fetching one by its id, marking it as read, claiming and assigning all answer by the rule of the list they hang below, and report an entity the list would not show as unknown. The live update stream stays as it was and stays named here. The page about building a cockpit of your own describes the shape a controller has now: it answers one question with a visibility, and the list, the search, the page of a single entity and every action on one follow that answer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say where a provider of your own asks, and why it should cache The delivered provider reads the user out of the token and asks nobody, which is what its name says. An application which needs current roles replaces the bean and reaches the identity manager itself, and then it needs a cache: a day per user, emptied nightly, and emptiable by hand when a change has to be seen at once. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Drop the note about version 0.4.0 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say what llatcup filters, and what decides ended tasks Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say who asks for the user tasks of a case, and what for Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say that other ways of signing in are being worked on Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Add the second use of a hierarchy, where roles stay in the identity provider Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say that only the widening is per request, and where it lives Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say when the identity provider is asked, and when a group change arrives Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2
Say how a workflow module is connected and what it reports Connecting a workflow module holds the dependency, the smallest configuration and the two transports. Reporting workflows and user tasks holds the provider methods and the business data behind a list column. Templates holds the five files and where each of them is looked for. Running the Business Cockpit holds the jar, the database and what the first start asks for, and Security holds the token, the proxy and who sees which case. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019HSy3LqLy3SDHdP4ojgZb2