Homepage improvements & imprint update

.gitignore

@@ -120,6 +120,7 @@ testrun.log
 **/Plugins/**/*.dylib
 **/Plugins/**/*.so
 **/Plugins/**/*.dll
+**/*.dSYM/
 **/Cargo.lock
 /Examples/MultiService/MultiService
 /Examples/AuditLogDemo/AuditLogDemo
@@ -130,3 +131,17 @@ core
 /Examples/SourceStructure/SourceStructure
 /Examples/StreamingDemo/StreamingDemo
 /Examples/StreamingPipeline/StreamingPipeline
+/Examples/QualifierPlugin/QualifierPlugin
+/Examples/QualifierPluginC/QualifierPluginC
+/Examples/QualifierPluginPython/QualifierPluginPython
+/Examples/DataSync/DataSync
+/Examples/URLClient/URLClient
+/Examples/TerminalUI/TerminalUI
+/Examples/TerminalSystemMonitor/TerminalSystemMonitor
+/Examples/PipelineDemo/PipelineDemo
+/Examples/NumericSeparators/NumericSeparators
+/Examples/ExtractInCase/ExtractInCase
+/Examples/PipelineDemo/events.jsonl
+/Examples/PipelineDemo/demo-output
+/Examples/PipelineDemo/output
+/Examples/FormatAwareIO/output

.gitlab-ci.yml

@@ -263,7 +263,11 @@ integration:linux:
     - which clang && clang --version | head -1
     - which llc && llc --version | head -1
     - ls -la /usr/share/swift/usr/lib/swift/linux/ | head -5
-    - ./aro-dist/aro build ./Examples/HelloWorld --verbose 2>&1 || echo "Build failed with exit code $?"
+    - echo "=== About to run aro build ==="
+    - ls -la ./aro-dist/aro || echo "aro binary not found"
+    - file ./aro-dist/aro || echo "file command failed"
+    - timeout 60 ./aro-dist/aro build ./Examples/HelloWorld --verbose 2>&1 || echo "Build failed with exit code $?"
+    - echo "=== aro build completed ==="
 
     - chmod +x test-examples.pl
     - perl test-examples.pl --verbose

Book/TheLanguageGuide/AppendixA-ActionReference.md

@@ -671,49 +671,79 @@ Emit a <PaymentProcessed: event> with <payment>.
 
 ### Notify
 
-Sends notifications to users, administrators, or systems. The action automatically emits a `NotificationSentEvent` that can be handled by feature sets with `NotificationSent Handler` business activity.
+Sends notifications to a user, an object, or every item in a collection. The action automatically emits a `NotificationSentEvent` for each notified target, and these events can be handled by feature sets with `NotificationSent Handler` business activity.
 
 **Verbs:** `notify`, `alert`, `signal`
 
 **Syntax:**
+
+Two forms are supported depending on how you structure the arguments:
+
 ```aro
+(* Form 1: target is the result, message is the "with" payload *)
+Notify the <target> with <message>.
+
+(* Form 2: message is the result, recipient is the "to" object *)
 Notify the <message> to the <recipient>.
-Alert the <message> to the <recipient>.
-Signal the <message> to the <recipient>.
 ```
 
+Form 1 (`with`) treats the result variable as the entity being notified. This is the preferred form when you want handlers to access the notified object's fields (for example, to use a `when` guard). Form 2 (`to`) is equivalent but places the notification message in the result position.
+
+**Collection Dispatch:**
+When the target (or recipient) resolves to a list, the runtime emits one `NotificationSentEvent` per item. Each event carries the item as the target value, allowing handlers to inspect the item's fields independently.
+
 **Examples:**
 ```aro
-(* User notification *)
-Notify the <welcome-message> to the <user>.
+(* Notify a single user object *)
+Create the <alice> with { name: "Alice", age: 30, email: "alice@example.com" }.
+Notify the <alice> with "Welcome to ARO!".
 
-(* Admin alert *)
-Alert the <system-warning> to the <admin>.
+(* Notify every item in a collection — one event per item *)
+Create the <group> with [
+    { name: "Bob",   age: 14 },
+    { name: "Carol", age: 25 },
+    { name: "Eve",   age: 20 }
+].
+Notify the <group> with "Hello everyone!".
 
-(* System signal *)
+(* Legacy to-form *)
+Notify the <welcome-message> to the <user>.
+Alert the <system-warning> to the <admin>.
 Signal the <shutdown-notice> to the <processes>.
 ```
 
 **NotificationSent Handler:**
-Feature sets can subscribe to notification events:
+Feature sets subscribe to notification events by using `NotificationSent Handler` as their business activity. A `when` guard on the handler declaration acts as a per-delivery filter — the guard is evaluated before the handler body runs, and the target object's fields are available directly in the condition:
 
 ```aro
+(* Unconditional handler — fires for every notification *)
 (Log All Notifications: NotificationSent Handler) {
     Extract the <message> from the <event: message>.
-    Extract the <type> from the <event: type>.
-    Log "Notification [${type}]: ${message}" to the <console>.
+    Log "Notification: " ++ <message> to the <console>.
     Return an <OK: status> for the <logging>.
 }
+
+(* Conditional handler — fires only when age >= 16 *)
+(Greet User: NotificationSent Handler) when <age> >= 16 {
+    Extract the <user> from the <event: user>.
+    Extract the <name> from the <user: name>.
+    Log "hello " ++ <name> to the <console>.
+    Return an <OK: status> for the <notification>.
+}
 ```
 
+In the second handler, `<age>` is resolved from the notified object's fields before the body executes. If the condition is false, the handler is silently skipped for that delivery.
+
 **Event Payload:**
 - `message` - The notification content
-- `recipient` - Target of the notification
+- `user` - The notified target object (when using the `with` form)
+- `recipient` - Target name (when using the `to` form)
 - `type` - One of: "notify", "alert", or "signal"
-- `timestamp` - When the notification was sent
 
 **Valid Prepositions:** `to`, `for`, `with`
 
+> **See Also:** Section 5.4 (Handler Guards), Chapter 13.4 (Handler Guards) for a full explanation of the `when` guard on handler declarations.
+
 ---
 
 ### Write