Skip to content

History / Integration SPI

Revisions

  • 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

    @stephanpelikan stephanpelikan committed Oct 12, 2026
  • 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

    @stephanpelikan stephanpelikan committed Oct 11, 2026
  • docs: phase two is a moment, not a BPMS call Phase one is your transaction, phase two is everything which runs after its commit. The names say when work runs and not who runs it, so a call to a BPMS is one kind of phase-two work and an operation an extension registered for itself is another. The glossary of the home page, the integration SPI table, the extensions page and the outbox section of both platform pages now say the same thing, so a reader meets one definition instead of two. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RYPiyZ32jQQhqYKx44cw23

    @stephanpelikan stephanpelikan committed Sep 20, 2026
  • docs: the integration SPI page starts with what it is for The page opened with the direction of the API, which reads like something every application has to implement. What the reader needs first is that VanillaBP already answers these questions and that this is the way to answer one of them differently, which most applications never do. The direction follows in the second paragraph, where it is a detail rather than the headline. Home entry and glossary say the same thing now. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XjxJNwTRcKzTmXCwLU7Wi4

    @stephanpelikan stephanpelikan committed Sep 1, 2026
  • docs: the page is called integration SPI The artifact is io.vanillabp:vanillabp-integration-spi, so the wiki calls the thing what its coordinate calls it instead of inventing a second name. Page renamed, all links and the glossary entry follow. The adapter SPI is gone from the wiki: it is nothing a reader of these pages implements. Where the start instant explains its own name, the reason is now VanillaBP's rather than an SPI the page never introduces. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XjxJNwTRcKzTmXCwLU7Wi4

    @stephanpelikan stephanpelikan committed Sep 1, 2026