docs: review pass, fix 4.0 API drift and align canonical URLs

- Add the orphaned Dynamic Consistency Boundary page to the navigation
- Rename index.md to introduction.md per docs convention
- message.md: replace removed AggregateHeader with StreamNameHeader/PlayheadHeader/RecordedOnHeader and refresh the built-in headers list
- store.md: fix removed StreamStore/Stream/criteria classes (StreamCriterion, Store, Message\Stream, Criteria-based remove)
- repository.md: point to InstantRetryCommandBus instead of the removed RetryOutdatedAggregateCommandBus
- getting-started.md: fix undefined $hotelProjection variable and outdated bundle URL
- Replace generic [here] link anchors, fix forward references and grammar
- testing.md: add install command for the separate phpunit package
- README/composer.json: switch to patchlevel.dev canonical URLs

Author: DavidBadura

README.md

@@ -11,21 +11,16 @@ powered by the reliable Doctrine ecosystem and focused on developer experience.
 ## Features
 
 * Everything is included in the package for event sourcing
-* Based on [doctrine dbal](https://github.com/doctrine/dbal) and their ecosystem
+* Based on doctrine dbal and their ecosystem
 * Developer experience oriented and fully typed
-* Automatic [snapshot](https://patchlevel.github.io/event-sourcing-docs/latest/snapshots/)-system to boost your
-  performance
-* [Split](https://patchlevel.github.io/event-sourcing-docs/latest/split_stream/) big aggregates into multiple streams
-* Versioned and managed lifecycle
-  of [subscriptions](https://patchlevel.github.io/event-sourcing-docs/latest/subscription/) like projections and
-  processors
-* Safe usage of [Personal Data](https://patchlevel.github.io/event-sourcing-docs/latest/personal_data/) with
-  crypto-shredding
-* Smooth [upcasting](https://patchlevel.github.io/event-sourcing-docs/latest/upcasting/) of old events
-* Simple setup with [scheme management](https://patchlevel.github.io/event-sourcing-docs/latest/store/)
-  and [doctrine migration](https://patchlevel.github.io/event-sourcing-docs/latest/store/)
-* Built in [cli commands](https://patchlevel.github.io/event-sourcing-docs/latest/cli/)
-  with [symfony](https://symfony.com/)
+* Automatic snapshot-system to boost your performance
+* Split big aggregates into multiple streams
+* Versioned and managed lifecycle of subscriptions like projections and processors
+* Safe usage of personal data with crypto-shredding
+* Smooth upcasting of old events
+* Simple setup with schema management and doctrine migration
+* Built in cli commands with symfony
+* Dynamic consistency boundary for decisions across streams
 * and much more...
 
 ## Installation
@@ -36,14 +31,21 @@ composer require patchlevel/event-sourcing
 
 ## Documentation
 
-* Latest [Docs](https://event-sourcing.patchlevel.io/latest/getting_started/)
-* Related [Blog](https://patchlevel.de/blog)
+* Latest [Docs](https://patchlevel.dev/docs/event-sourcing/latest)
+* Related [Blog](https://patchlevel.dev/blog)
 
 ## Integration
 
 * [Symfony](https://github.com/patchlevel/event-sourcing-bundle)
 * [Psalm](https://github.com/patchlevel/event-sourcing-psalm-plugin)
 
+## Contributing
+
+We are open to contributions as long as they are in line with
+our [BC-Policy](https://patchlevel.dev/our-backward-compatibility-promise).
+
+Also note that the `composer.lock` is always generated with the newest supported PHP version as this is the version our tools run in the CI.
+
 ## Supported databases
 
 We officially only support the databases and versions listed in the table, as these are tested in the CI.

composer.json

@@ -19,7 +19,7 @@
     "dynamic consistency boundary",
     "patchlevel"
   ],
-  "homepage": "https://event-sourcing.patchlevel.io",
+  "homepage": "https://patchlevel.dev/docs/event-sourcing/latest",
   "authors": [
     {
       "name": "Daniel Badura",

docs/command-bus.md

@@ -425,3 +425,4 @@ $provider = new ChainHandlerProvider([
 * [How to use clock](clock.md)
 * [How to use aggregate id](identifier.md)
 * [How to use query bus](query-bus.md)
+* [How to decide across streams with a dynamic consistency boundary](dynamic-consistency-boundary.md)

docs/dynamic-consistency-boundary.md

@@ -87,7 +87,7 @@ final class GuestIsCheckedOut
 ```
 
 :::note
-You can find out more about events [here](events.md).    
+You can find out more about [events](events.md).
 :::    
 
 ## Define Commands
@@ -456,6 +456,6 @@ You can find this [Getting Started](./getting-started.md) section.
 
 ## Learn more
 
-* [Events](./events.md)
-* [Command Bus](./command-bus.md)
-* [Store](./store.md)
+* [How to define events](events.md)
+* [How to dispatch commands](command-bus.md)
+* [How to store events](store.md)

docs/events.md

@@ -8,7 +8,7 @@ You can also listen on events to react and perform different actions.
 An event has a name and additional information called payload.
 Such an event can be represented as any class.
 It is important that the payload can be serialized as JSON at the end.
-Later it will be explained how to ensure it for all values.
+How to ensure this for complex values is shown in the [normalizer](#normalizer) section below.
 
 To register an event you have to set the `Event` attribute over the class,
 otherwise it will not be recognized as an event.
@@ -80,7 +80,7 @@ $serializer = DefaultEventSerializer::createFromPaths(['src/Domain']);
 ```
 The serializer needs the path information where the event classes are located
 so that it can instantiate the correct classes.
-Internally, an EventRegistry is used, which will be described later.
+Internally, an EventRegistry is used, which is described in the [Event Registry](#event-registry) section below.
 
 ## Normalizer
 

docs/getting-started.md

@@ -265,7 +265,7 @@ You can find out more about [processors](subscription.md).
 After we have defined everything, we still have to plug the whole thing together:
 
 :::tip
-If you use symfony, you can use our [symfony bundle](https://event-sourcing-bundle.patchlevel.io/latest/installation/) to skip this step.
+If you use symfony, you can use our [symfony bundle](https://patchlevel.dev/docs/event-sourcing-bundle/latest) to skip this step.
 :::
 
 ```php
@@ -326,7 +326,7 @@ $hotelRepository = $repositoryManager->get(Hotel::class);
 ```
 
 :::note
-You can find out more about stores [here](store.md).
+You can find out more about the [store](store.md).
 :::
 
 ## Database setup
@@ -386,12 +386,12 @@ $hotel2 = $hotelRepository->load(Uuid::fromString('d0d0d0d0-d0d0-d0d0-d0d0-d0d0d
 $hotel2->checkIn('David');
 $hotelRepository->save($hotel2);
 
-$hotels = $hotelProjection->getHotels();
+$hotels = $hotelProjector->getHotels();
 ```
 
 :::note
 You can also use other forms of IDs such as uuid version 6 or a custom format.
-You can find more about this [here](identifier.md).
+You can find more about [identifiers](identifier.md).
 :::
 
 ## Result

docs/index.md docs/introduction.mddocs/index.md renamed to docs/introduction.md

@@ -19,18 +19,17 @@ the [repository](repository.md).
 You can add a header using `withHeader`:
 
 ```php
-use Patchlevel\EventSourcing\Aggregate\AggregateHeader;
 use Patchlevel\EventSourcing\Clock\SystemClock;
 use Patchlevel\EventSourcing\Message\Message;
+use Patchlevel\EventSourcing\Store\Header\PlayheadHeader;
+use Patchlevel\EventSourcing\Store\Header\RecordedOnHeader;
+use Patchlevel\EventSourcing\Store\Header\StreamNameHeader;
 
 $clock = new SystemClock();
 $message = Message::create(new NameChanged('foo'))
-    ->withHeader(new AggregateHeader(
-        aggregateName: 'profile',
-        aggregateId: 'bca7576c-536f-4428-b694-7b1f00c714b7',
-        playhead: 2,
-        recordedOn: $clock->now(),
-    ));
+    ->withHeader(new StreamNameHeader('profile-bca7576c-536f-4428-b694-7b1f00c714b7'))
+    ->withHeader(new PlayheadHeader(2))
+    ->withHeader(new RecordedOnHeader($clock->now()));
 ```
 :::note
 The message object is immutable. It creates a new instance with the new data.
@@ -39,19 +38,24 @@ The message object is immutable. It creates a new instance with the new data.
 You can also access the headers:
 
 ```php
-use Patchlevel\EventSourcing\Aggregate\AggregateHeader;
 use Patchlevel\EventSourcing\Message\Message;
+use Patchlevel\EventSourcing\Store\Header\PlayheadHeader;
 
 /** @var Message $message */
-$message->header(AggregateHeader::class); // AggregateHeader object
-$message->hasHeader(AggregateHeader::class); // true
-$message->headers(); // [AggregateHeader object]
+$message->header(PlayheadHeader::class); // PlayheadHeader object
+$message->hasHeader(PlayheadHeader::class); // true
+$message->headers(); // [StreamNameHeader object, PlayheadHeader object, ...]
 ```
 ## Built-in headers
 
 The message object has some built-in headers which are used internally.
 
-* `AggregateHeader` - Contains the aggregate name, aggregate id, playhead and recorded on.
+* `StreamNameHeader` - The name of the stream the message belongs to, in the format `[aggregateName]-[aggregateId]`.
+* `PlayheadHeader` - The position of the message within its stream.
+* `RecordedOnHeader` - The date and time when the message was recorded.
+* `EventIdHeader` - The unique id of the event.
+* `IndexHeader` - The global position of the message in the store.
+* `TagsHeader` - The tags attached to the message (experimental).
 * `ArchivedHeader` - Flag if the message is archived.
 * `StreamStartHeader` - Flag if the message is the first message in a new stream.
 

docs/message.md

@@ -2,7 +2,7 @@
   "navigation": [
     {
       "title": "Introduction",
-      "file": "index.md"
+      "file": "introduction.md"
     },
     {
       "title": "Getting Started",
@@ -80,6 +80,10 @@
           "title": "Split Stream",
           "file": "split-stream.md"
         },
+        {
+          "title": "Dynamic Consistency Boundary",
+          "file": "dynamic-consistency-boundary.md"
+        },
         {
           "title": "Time / Clock",
           "file": "clock.md"

docs/project.json

@@ -176,8 +176,8 @@ An `AggregateOutdated` exception is thrown if a conflict occurs.
 :::
 
 :::tip
-If you use the Command Bus, you can use the [RetryOutdatedAggregateCommandBus](command-bus.md#retry-outdated-aggregate-command-bus)
-to retry the command when an `AggregateOutdated` exception occurs automatically.
+If you use the Command Bus, you can use the [instant retry](command-bus.md#instant-retry) decorator
+to retry the command automatically when an `AggregateOutdated` exception occurs.
 :::
 
 ### Load an aggregate