U-A/U-B: Prozesskern mit Fachmodulen, versionierten Modellen, eingefrorenem Prozessplan, ProcessRunner (harte/weiche Abhängigkeiten), CasePricing, Loyalty nur im Tester

CaseActivities/CaseAutomation sind Fassaden über ProcessRunner. Verhaltensvergleich v0.11:
11 Abläufe und 198 Konstellationen gleich, beabsichtigte Abweichungen I-004/I-005 (F-001/F-002).
Volle Suite vor U-B: 785/785.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
LarsandClaude Opus 5.5 committed 2026-11-04 14:49:44 +01:00
1 parent 98df5e9e3b
commit 7e22e12cac
80 files changed
+4628 -445

No files matched your search

+30
View File
@@ -0,0 +1,30 @@
<?php
namespace App\Process\Modules;
use App\Process\CaseContext;
use App\Process\StepResult;
/**
* A module whose step the system may carry out by itself (docs/Prozessarchitektur/Architektur/02 §7): the runner asks
* whether it is due, checks its hard dependencies, then runs it through the existing actions. `run` must be idempotent:
* a second run of a step that is already carried out has no effect.
*/
interface RunsAutomatically
{
/** Whether the system may carry the step out now by itself (its mode is automatic and the step is still to do). */
public function due(CaseContext $case): bool;
/**
* What keeps the step from being carried out now (plain words; empty = it may run).
*
* @return list<string>
*/
public function blockers(CaseContext $case): array;
/** Carries the step out by calling the existing action(s). */
public function run(CaseContext $case): StepResult;
/** Whether the step speaks to the guest or a third party (suspended while a portal report is open, decision O4). */
public function isOutward(): bool;
}