979: why links follow the merged platform decisions Decisions 25 and 27 of the platform are merged into decision 5, and 59 into 57. The links point at the entries which hold the text now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lxo4MXbp6VPoDkUrTBNXJ1
Rewrite thirteen shorter pages in plain English Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lxo4MXbp6VPoDkUrTBNXJ1
docs: the application names the workflow it did not start Starting workflows described the state before stories 504 and 653. It said VanillaBP builds the aggregate of a workflow the BPMS started, that the process instance key or the trigger time becomes its id, and that a workflow can arrive with a business key of somebody else's choosing. None of that is true any more. The page now says what the code does. A @WorkflowStartedByBpms method returns the workflow aggregate, and that aggregate names the workflow. The BPMS holds the name afterwards: Camunda 7 as the business key, Camunda 8 and the Process-Engine-API as the process variable named after the id attribute. Every start is then read from the state of the workflow: a name with an aggregate is our own start, no name is a start past VanillaBP, and a name no aggregate carries is refused. The trigger carries no time, and the section which recommended taking one is gone. The method is required where the BPMS fires a start event by itself; a plain or message start event is judged when somebody uses it, not at boot. Timers and Migrating from version 1 said the same old thing in one sentence each and follow along, the first one also to the renamed section. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0168Fox39crp8dfWkZ9W84Ub
docs: in which time zone a timer counts BPMN says nothing about time zones, so each engine answers for itself. Measured Camunda 7: a timeDate naming no zone is read in the JVM's zone, and a P1D over the autumn change is 25 hours. Names the shape which survives a change of BPMS. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0168Fox39crp8dfWkZ9W84Ub
docs: a timer has a page of its own The three forms a BPMN timer takes, the three places it can sit in, and what reaches the model when the time comes out of the workflow aggregate. Says what VanillaBP does not do here: no timer API, and no adapter reads the date, the duration or the cycle. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0168Fox39crp8dfWkZ9W84Ub