eyeling 1.24.24 → 1.24.26

package/examples/input/rdf-messages.trig

@@ -1,5 +1,32 @@
+# ==========================
+# RDF Messages input sidecar
+# ==========================
+#
+# This file is the data half of the runnable example:
+#
+#   eyeling -r examples/rdf-messages.n3 examples/input/rdf-messages.trig
+#
+# It is intentionally plain TriG rather than a parser-level RDF Message Log with
+# VERSION "1.2-messages" and MESSAGE delimiters. The RDF Messages draft says an
+# RDF Message is an RDF dataset interpreted atomically, that a message stream is
+# an ordered sequence of such messages, that messages are not combined by
+# default, and that blank-node labels are scoped to the message.
+#
+# To demonstrate those ideas in Eyeling today, the default graph contains
+# application-local envelope records (:m001 ... :m003) plus replay order and
+# offsets. Each non-empty message payload is placed in its own named graph
+# (in:payload001 and in:payload003). The second envelope is an empty heartbeat,
+# which is valid because RDF Messages may be empty.
+#
+# The envelope IRIs are not message identifiers defined by the spec; they are
+# application-level records used by the rules. The named payload graphs are the
+# datasets/messages being interpreted atomically. The rmsg:localBlankLabel values
+# show that the same source-local label "_:b0" can recur in different messages;
+# the concrete TriG blank nodes themselves are unique because this sidecar is
+# ordinary TriG rather than an RDF Message Log parser resetting blank-node scope.
+
 @prefix : <https://eyereasoner.github.io/eyeling/examples/rdf-messages#> .
-@prefix msg: <https://w3c-cg.github.io/rsp/spec/messages#> .
+@prefix rmsg: <https://eyereasoner.github.io/eyeling/examples/rdf-messages/vocab#> .
 @prefix prov: <http://www.w3.org/ns/prov#> .
 @prefix sosa: <http://www.w3.org/ns/sosa/> .
 @prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@@ -10,46 +37,46 @@
 @prefix see: <https://example.org/see#> .
 @prefix in: <https://example.org/see/input#> .
 
-# Formal Eyeling input evidence in RDF 1.2 TriG.
-# The generated runner reads this TriG evidence directly.
+:temperatureLog a rmsg:MessageLog .
+:temperatureLog rmsg:orderedMessages (:m001 :m002 :m003) .
+:temperatureLog rmsg:message :m001 .
+:temperatureLog rmsg:message :m002 .
+:temperatureLog rmsg:message :m003 .
+:temperatureLog rmsg:profile :generatedAtTimeProfile .
+:temperatureLog rmsg:retentionPolicy "replayable archive" .
+
+:m001 a rmsg:MessageEnvelope .
+:m001 rmsg:offset 1 .
+:m001 prov:generatedAtTime "2026-05-12T18:20:00Z"^^xsd:dateTime .
+:m001 rmsg:payloadKind :observation .
+:m001 rmsg:localBlankLabel "_:b0" .
+:m001 rmsg:expectedResult 22 .
+:m001 rmsg:payloadGraph in:payload001 .
+
+:m002 a rmsg:MessageEnvelope .
+:m002 rmsg:offset 2 .
+:m002 prov:generatedAtTime "2026-05-12T18:22:00Z"^^xsd:dateTime .
+:m002 rmsg:payloadKind :heartbeat .
 
-:temperatureLog a msg:MessageLog .
-:temperatureLog msg:orderedMessages (:m001 :m002 :m003) .
-:temperatureLog msg:message :m001 .
-:temperatureLog msg:message :m002 .
-:temperatureLog msg:message :m003 .
-:temperatureLog msg:profile :generatedAtTimeProfile .
-:temperatureLog msg:retentionPolicy "replayable archive" .
-:m001 a msg:RDFMessage .
-:m001 msg:offset 1 .
-:m001 prov:generatedAtTime "2026-05-12T18:20:00Z" .
-:m001 msg:payloadKind :observation .
-:m001 msg:localBlankLabel "_:b0" .
-:m001 msg:expectedResult 22 .
-:m001 msg:payload in:formula1 .
-:m002 a msg:RDFMessage .
-:m002 msg:offset 2 .
-:m002 prov:generatedAtTime "2026-05-12T18:22:00Z" .
-:m002 msg:payloadKind :heartbeat .
-:m003 a msg:RDFMessage .
-:m003 msg:offset 3 .
-:m003 prov:generatedAtTime "2026-05-12T18:25:00Z" .
-:m003 msg:payloadKind :observation .
-:m003 msg:localBlankLabel "_:b0" .
-:m003 msg:expectedResult 23 .
-:m003 msg:payload in:formula2 .
+:m003 a rmsg:MessageEnvelope .
+:m003 rmsg:offset 3 .
+:m003 prov:generatedAtTime "2026-05-12T18:25:00Z"^^xsd:dateTime .
+:m003 rmsg:payloadKind :observation .
+:m003 rmsg:localBlankLabel "_:b0" .
+:m003 rmsg:expectedResult 23 .
+:m003 rmsg:payloadGraph in:payload003 .
 
-in:formula1 {
+in:payload001 {
   _:m001b0 a sosa:Observation .
   _:m001b0 sosa:madeBySensor :thermometerA .
-  _:m001b0 sosa:resultTime "2026-05-12T18:20:00Z" .
+  _:m001b0 sosa:resultTime "2026-05-12T18:20:00Z"^^xsd:dateTime .
   _:m001b0 sosa:hasSimpleResult 22 .
 }
 
-in:formula2 {
+in:payload003 {
   _:m003b0 a sosa:Observation .
   _:m003b0 sosa:madeBySensor :thermometerA .
-  _:m003b0 sosa:resultTime "2026-05-12T18:25:00Z" .
+  _:m003b0 sosa:resultTime "2026-05-12T18:25:00Z"^^xsd:dateTime .
   _:m003b0 sosa:hasSimpleResult 23 .
 }
 
@@ -57,13 +84,7 @@ in:metadata {
   in:run a see:InputDataset .
   in:run see:name "rdf_messages" .
   in:run see:title "RDF Messages" .
-  in:run see:sourceFile "examples/n3/rdf_messages.n3" .
-  in:run see:sourceSHA256 "2ea8b414b92e65531cf384000955ca47811d5b7c779a8d2c9fb007515e745f32" .
-  in:run see:description "This Eyeling example models the main idea from\nhttps://pietercolpaert.be/papers/eswc2026-rdf-messages/:\na message stream/log is not just one freely mergeable RDF graph. It is an\nordered sequence of RDF Datasets that are interpreted atomically, one message\nat a time. The middle message is deliberately empty to model a heartbeat, and\nthe local blank-node label \"_:b0\" is deliberately reused by two messages to\nshow message-scoped blank nodes." .
+  in:run see:sourceFile "examples/rdf-messages.n3" .
+  in:run see:description "A single Eyeling example split across an N3 rule file and a TriG input sidecar. It models a replayable RDF Message Log with application-level envelopes and named payload graphs so that each payload can be interpreted atomically without merging all message contents into one graph." .
   in:run see:compiler "Eyeling RDF/TriG input sidecar" .
-  in:run see:inputFacts 25 .
-  in:run see:compiledRules 6 .
-  in:run see:compiledBackwardRules 0 .
-  in:run see:compiledFuses 0 .
-  in:run see:compiledQueries 1 .
 }

package/examples/output/rdf-message-flow.md

@@ -6,7 +6,7 @@
 - [Input TriG](../input/rdf-message-flow.trig)  
 
 ## Answer  
-Continuous RDF Message flow accepted: 5 ordered messages moved through the ingest → validate → interpret → route → sink pipeline. The threshold was 26, so results 21 and 22 were archived, the heartbeat kept the stream alive, and results 28 and 29 were emitted as alerts.  
+Continuous RDF Message flow accepted: 5 ordered message envelopes moved through the ingest → validate → interpret → route → sink pipeline. The threshold was 26, so results 21 and 22 were archived, the heartbeat kept the stream alive, and results 28 and 29 were emitted as alerts.  
 
 ## Explanation  
-The N3 source starts only :m001 at ingress. Each message must reach :sink before the continuous-flow rule releases its msg:nextMessage. Observation payloads are inspected with log:includes inside each message formula, while the empty heartbeat uses the same envelope and routing stages without a payload. This models messages flowing through a live stream while preserving message boundaries.  
+The input is a single runnable example split across an N3 rule file and a TriG sidecar. The TriG file uses example-local envelope facts for stream order and processing state, while each named payload graph is treated as an atomic RDF Message dataset. Only :m001 starts at ingress; each envelope must reach :sink before the continuous-flow rule releases its flow:nextEnvelope. Observation payloads are inspected with log:includes inside their own payload formula, and the empty heartbeat advances without a payload graph. This keeps message boundaries visible to the reasoner instead of merging all payload triples into one global graph.  

package/examples/output/rdf-message-microgrid.md

@@ -0,0 +1,14 @@
+# rdf-message-microgrid  
+
+## Source files  
+
+- [N3 rules](../rdf-message-microgrid.n3)  
+- [Input TriG](../input/rdf-message-microgrid.trig)  
+
+## Answer  
+Storm clinic microgrid accepted: 4 RDF Message envelopes were replayed atomically. Critical care needs 620 W, current battery plus solar gives 800 W, and deferring the EV chargers frees 600 W, so the protected budget is 1400 W. The reasoned action is to keep the oxygen concentrator and vaccine fridge online, while deferring EV charging.  
+
+## Why this is an RDF Messages example  
+The input is a single runnable example split across an N3 rule file and a TriG sidecar. The default graph records stream order, offsets, and envelope metadata. Each non-empty named graph is treated as an atomic message payload, and the fourth message is an empty heartbeat. The rules inspect each payload with log:includes inside its own formula, then combine only the derived conclusions needed for the microgrid decision. This keeps the explanation tied to message boundaries instead of silently flattening the stream into one global graph.  
+
+This is intentionally not a parser-level VERSION \"1.2-messages\" / MESSAGE delimiter test. It is a reasoning example over an already-materialized sidecar representation of a message log.  

package/examples/output/rdf-messages.md

@@ -6,7 +6,9 @@
 - [Input TriG](../input/rdf-messages.trig)  
 
 ## Answer  
-RDF Message log accepted: 3 explicit message boundaries are preserved. Message :m002 is an empty heartbeat, and the local blank-node label _:b0 is safely reused in separate messages.  
+RDF Message replay archive accepted: 3 explicit message boundaries are preserved. Message :m002 is an empty heartbeat, and the local blank-node label _:b0 is safely reused in separate message envelopes.  
 
 ## Explanation  
-The N3 source models an RDF Message Log as an ordered sequence of RDF Messages. Each non-empty message has a formula-valued payload that is inspected with log:includes, so the observation data stays inside the message boundary instead of being treated as one global graph. The two temperature results, 22 and 23, are different observations from the same stream but are contextualized by their message boundaries.  
+The input is a single runnable example split across an N3 rule file and a TriG sidecar. The TriG file uses application-local envelope facts for stream order and replay metadata, while each non-empty named payload graph is treated as an atomic RDF Message dataset. Payloads are inspected with log:includes inside their own formulas, so the observation data stays inside the message boundary instead of being treated as one global graph. The two temperature results, 22 and 23, are different observations from the same stream but are contextualized by their message boundaries.  
+
+This is intentionally not a parser-level VERSION \"1.2-messages\" / MESSAGE delimiter test. It is a reasoning example over an already-materialized sidecar representation of a message log.  

package/examples/rdf-message-flow.n3

@@ -1,14 +1,35 @@
 # ================
 # RDF Message Flow
 # ================
-# A companion to rdf_messages.n3. This example focuses on a live stream where
-# RDF Messages continuously flow through a small processing pipeline. The next
-# message is released only after the current message reaches the sink, so the
-# stream behaves as an ordered, replayable flow rather than a single merged RDF
-# graph.
+#
+# Run as:
+#
+#   eyeling -r examples/rdf-message-flow.n3 examples/input/rdf-message-flow.trig
+#
+# Motivation
+# ----------
+# The RDF Messages draft describes an RDF Message as an RDF dataset interpreted
+# atomically, and an RDF Message Stream as an ordered sequence of such messages.
+# It also defines RDF Message Logs with explicit MESSAGE delimiters. This Eyeling
+# example keeps the same message-level discipline while staying in ordinary
+# N3/TriG that Eyeling can reason over today.
+#
+# The companion TriG file therefore separates two layers:
+#
+#   1. example-local envelope facts in the default graph, such as order,
+#      processing stage, and payload graph; and
+#   2. one named graph per non-empty message payload, treated here as the RDF
+#      dataset/message that must be inspected atomically.
+#
+# The rules below deliberately do not merge all payload graphs into one global
+# graph. Instead, each observation is checked with log:includes inside the named
+# payload formula. The empty heartbeat has no payload graph but still advances
+# through the same pipeline. The next message is released only after the current
+# one reaches the sink, making the example a small back-pressure / flow-control
+# story rather than a batch merge of all input triples.
 
 @prefix : <https://eyereasoner.github.io/eyeling/examples/rdf-message-flow#>.
-@prefix msg: <https://example.org/msg#>.
+@prefix flow: <https://eyereasoner.github.io/eyeling/examples/rdf-message-flow/vocab#>.
 @prefix prov: <http://www.w3.org/ns/prov#>.
 @prefix sosa: <http://www.w3.org/ns/sosa/>.
 @prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@@ -17,126 +38,120 @@
 @prefix log: <http://www.w3.org/2000/10/swap/log#>.
 @prefix string: <http://www.w3.org/2000/10/swap/string#>.
 
-
-# The stream starts with just the first message at ingress. Later messages are
-# not pre-loaded; each one is released by the previous message after sink.
-
-
-
-# Empty heartbeat: it flows through the same pipeline and keeps the stream live.
-
-
-
-# Stage 1: once a message has entered the stream, validate its envelope.
-
-{ ?Message :atStage :ingest. } => {
-  ?Message :atStage :validate.
+# Stage 1: once an envelope has entered the stream, validate it.
+{ ?Envelope :atStage :ingest. } => {
+  ?Envelope :atStage :validate.
 }.
 
-# Stage 2: validation preserves the message boundary before interpretation.
+# Stage 2: validation records that the envelope keeps an explicit message
+# boundary before the payload is interpreted.
 {
-  ?Message :atStage :validate;
-    a msg:RDFMessage;
-    msg:offset ?Offset.
+  ?Envelope :atStage :validate;
+    a flow:MessageEnvelope;
+    flow:offset ?Offset.
 } => {
-  ?Message msg:boundaryExplicit true.
-  ?Message :atStage :interpret.
+  ?Envelope flow:boundaryExplicit true.
+  ?Envelope :atStage :interpret.
 }.
 
-# Stage 3a: observation payloads are inspected inside their message formula.
+# Stage 3a: observation payloads are inspected inside their own payload graph.
+# This models the RDF Messages idea that messages are separate atomic datasets.
 {
-  ?Message :atStage :interpret;
-    msg:payloadKind :observation;
-    msg:expectedResult ?Result;
-    msg:payload ?Payload.
+  ?Envelope :atStage :interpret;
+    flow:payloadKind :observation;
+    flow:expectedResult ?Result;
+    flow:payloadGraph ?Payload.
   ?Payload log:nameOf ?PayloadContext.
   ?PayloadContext log:includes { ?Observation sosa:hasSimpleResult ?Result. }.
 } => {
-  ?Message msg:payloadResult ?Result.
-  ?Message :atStage :route.
+  ?Envelope flow:payloadResult ?Result.
+  ?Envelope :atStage :route.
 }.
 
-# Stage 3b: empty heartbeats have no payload, but still move through the flow.
+# Stage 3b: empty heartbeats contain no quads, but RDF Messages explicitly allow
+# empty messages, so the envelope still moves through the flow.
 {
-  ?Message :atStage :interpret;
-    msg:payloadKind :heartbeat.
+  ?Envelope :atStage :interpret;
+    flow:payloadKind :heartbeat.
 } => {
-  ?Message msg:emptyMessageAllowed true.
-  ?Message :atStage :route.
+  ?Envelope flow:emptyMessageAllowed true.
+  ?Envelope :atStage :route.
 }.
 
 # Stage 4a: hot observations are routed to the alert sink.
 {
-  ?Message :atStage :route;
-    msg:payloadResult ?Result.
+  ?Envelope :atStage :route;
+    flow:payloadResult ?Result.
   :temperatureFlow :highThreshold ?Threshold.
   ?Result math:greaterThan ?Threshold.
 } => {
-  ?Message :route :alertSink.
-  ?Message :atStage :sink.
-  :alertSink :received ?Message.
+  ?Envelope :route :alertSink.
+  ?Envelope :atStage :sink.
+  :alertSink :received ?Envelope.
 }.
 
 # Stage 4b: normal observations are routed to the archive sink.
 {
-  ?Message :atStage :route;
-    msg:payloadResult ?Result.
+  ?Envelope :atStage :route;
+    flow:payloadResult ?Result.
   :temperatureFlow :highThreshold ?Threshold.
   ?Result math:notGreaterThan ?Threshold.
 } => {
-  ?Message :route :archiveSink.
-  ?Message :atStage :sink.
-  :archiveSink :received ?Message.
+  ?Envelope :route :archiveSink.
+  ?Envelope :atStage :sink.
+  :archiveSink :received ?Envelope.
 }.
 
 # Stage 4c: heartbeats are routed separately from observations.
 {
-  ?Message :atStage :route;
-    msg:emptyMessageAllowed true.
+  ?Envelope :atStage :route;
+    flow:emptyMessageAllowed true.
 } => {
-  ?Message :route :heartbeatSink.
-  ?Message :atStage :sink.
-  :heartbeatSink :received ?Message.
+  ?Envelope :route :heartbeatSink.
+  ?Envelope :atStage :sink.
+  :heartbeatSink :received ?Envelope.
 }.
 
-# Continuous-flow rule: reaching the sink releases the next message into ingress.
+# Continuous-flow rule: reaching the sink releases the next envelope into ingress.
+# This mirrors a consumer-visible ordered stream: later messages are not processed
+# until the earlier message has completed the pipeline.
 {
-  ?Message :atStage :sink;
-    msg:nextMessage ?Next.
-  ?Next a msg:RDFMessage.
+  ?Envelope :atStage :sink;
+    flow:nextEnvelope ?Next.
+  ?Next a flow:MessageEnvelope.
 } => {
-  ?Message :releases ?Next.
+  ?Envelope :releases ?Next.
   ?Next :atStage :ingest.
 }.
 
-# The Eyeling verdict is emitted only after all five messages have flowed through
-# ingest, validation, interpretation, routing, and sink.
+# The Eyeling verdict is emitted only after all five envelopes have flowed
+# through ingest, validation, interpretation, routing, and sink while preserving
+# their message boundaries.
 {
-  :temperatureFlow msg:orderedMessages ?Messages;
+  :temperatureFlow flow:orderedEnvelopes ?Envelopes;
     :highThreshold ?Threshold.
-  ?Messages list:length ?Count.
+  ?Envelopes list:length ?Count.
   :m001 :atStage :sink;
-    msg:payloadResult ?FirstResult;
+    flow:payloadResult ?FirstResult;
     :route :archiveSink;
     :releases :m002.
   :m002 :atStage :sink;
-    msg:payloadResult ?SecondResult;
+    flow:payloadResult ?SecondResult;
     :route :archiveSink;
     :releases :m003.
   :m003 :atStage :sink;
-    msg:emptyMessageAllowed true;
+    flow:emptyMessageAllowed true;
     :route :heartbeatSink;
     :releases :m004.
   :m004 :atStage :sink;
-    msg:payloadResult ?FourthResult;
+    flow:payloadResult ?FourthResult;
     :route :alertSink;
     :releases :m005.
   :m005 :atStage :sink;
-    msg:payloadResult ?FifthResult;
+    flow:payloadResult ?FifthResult;
     :route :alertSink.
-  ("# rdf-message-flow\n\n## Source files\n\n- [N3 rules](../rdf-message-flow.n3)\n- [Input TriG](../input/rdf-message-flow.trig)\n\n## Answer\nContinuous RDF Message flow accepted: %d ordered messages moved through the ingest → validate → interpret → route → sink pipeline. The threshold was %d, so results %s and %s were archived, the heartbeat kept the stream alive, and results %s and %s were emitted as alerts.\n\n## Explanation\nThe N3 source starts only :m001 at ingress. Each message must reach :sink before the continuous-flow rule releases its msg:nextMessage. Observation payloads are inspected with log:includes inside each message formula, while the empty heartbeat uses the same envelope and routing stages without a payload. This models messages flowing through a live stream while preserving message boundaries." ?Count ?Threshold ?FirstResult ?SecondResult ?FourthResult ?FifthResult) string:format ?Block.
+  ("# rdf-message-flow\n\n## Source files\n\n- [N3 rules](../rdf-message-flow.n3)\n- [Input TriG](../input/rdf-message-flow.trig)\n\n## Answer\nContinuous RDF Message flow accepted: %d ordered message envelopes moved through the ingest → validate → interpret → route → sink pipeline. The threshold was %d, so results %s and %s were archived, the heartbeat kept the stream alive, and results %s and %s were emitted as alerts.\n\n## Explanation\nThe input is a single runnable example split across an N3 rule file and a TriG sidecar. The TriG file uses example-local envelope facts for stream order and processing state, while each named payload graph is treated as an atomic RDF Message dataset. Only :m001 starts at ingress; each envelope must reach :sink before the continuous-flow rule releases its flow:nextEnvelope. Observation payloads are inspected with log:includes inside their own payload formula, and the empty heartbeat advances without a payload graph. This keeps message boundaries visible to the reasoner instead of merging all payload triples into one global graph." ?Count ?Threshold ?FirstResult ?SecondResult ?FourthResult ?FifthResult) string:format ?Block.
 } => {
   :rdfMessageFlowExample log:outputString ?Block.
   :rdfMessageFlowExample :demonstrates :ContinuousFlow, :BackPressureRelease, :AtomicMessageContext, :HeartbeatInFlow, :ThresholdRouting.
 }.
-

package/examples/rdf-message-microgrid.n3

@@ -0,0 +1,141 @@
+# =====================
+# RDF Message Microgrid
+# =====================
+#
+# Run as:
+#
+#   eyeling -r examples/rdf-message-microgrid.n3 examples/input/rdf-message-microgrid.trig
+#
+# Motivation
+# ----------
+# A clinic has lost grid power during a storm. Several small systems continue to
+# send RDF data: one message describes life-safety loads, another describes the
+# current battery and solar situation, another describes flexible demand that may
+# be deferred, and a fourth message is an empty heartbeat.
+#
+# The RDF Messages draft treats each message as an RDF dataset intended to be
+# interpreted atomically. It also treats a message stream as an ordered sequence
+# and allows empty messages. This example models those ideas in ordinary TriG/N3:
+# the companion TriG file contains application-local envelope facts in the
+# default graph, and each non-empty payload is placed in its own named graph.
+#
+# The point is not only technical. Atomic messages let a small reasoner make a
+# careful decision under pressure: protect the oxygen concentrator and vaccine
+# fridge, defer the EV chargers, and explain the action from the replayed message
+# boundaries instead of silently merging every payload into one timeless graph.
+#
+# This is intentionally not a parser-level VERSION "1.2-messages" / MESSAGE
+# delimiter test. It is a reasoning example over an already-materialized sidecar
+# representation of a message log.
+
+@prefix : <https://eyereasoner.github.io/eyeling/examples/rdf-message-microgrid#>.
+@prefix rmsg: <https://eyereasoner.github.io/eyeling/examples/rdf-message-microgrid/vocab#>.
+@prefix prov: <http://www.w3.org/ns/prov#>.
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
+@prefix math: <http://www.w3.org/2000/10/swap/math#>.
+@prefix list: <http://www.w3.org/2000/10/swap/list#>.
+@prefix log: <http://www.w3.org/2000/10/swap/log#>.
+@prefix string: <http://www.w3.org/2000/10/swap/string#>.
+
+# Every envelope with an offset is an explicit replay boundary. The envelope is
+# application-local metadata; the payload graph is the dataset/message being
+# interpreted atomically.
+{
+  ?Log a rmsg:MessageLog;
+    rmsg:message ?Message.
+  ?Message a rmsg:MessageEnvelope;
+    rmsg:offset ?Offset.
+} => {
+  ?Message rmsg:boundaryExplicit true.
+  ?Log rmsg:replayContains ?Message.
+}.
+
+# Empty RDF Messages are valid. Here the fourth envelope is a heartbeat that
+# confirms the stream is still alive without adding any payload triples.
+{
+  ?Message a rmsg:MessageEnvelope;
+    rmsg:payloadKind :heartbeat.
+} => {
+  ?Message rmsg:emptyMessageAllowed true.
+}.
+
+# Inspect the life-safety message inside its own payload graph.
+{
+  ?Message rmsg:payloadKind :lifeSafetyLoads;
+    rmsg:payloadGraph ?Payload.
+  ?Payload log:nameOf ?PayloadContext.
+  ?PayloadContext log:includes {
+    :oxygenConcentrator :requiresWatts ?Oxygen.
+    :vaccineFridge :requiresWatts ?Fridge.
+  }.
+  (?Oxygen ?Fridge) math:sum ?CriticalWatts.
+} => {
+  :clinicMicrogrid rmsg:criticalWatts ?CriticalWatts.
+  :clinicMicrogrid rmsg:mustKeep :oxygenConcentrator, :vaccineFridge.
+}.
+
+# Inspect the power-status message atomically.
+{
+  ?Message rmsg:payloadKind :powerStatus;
+    rmsg:payloadGraph ?Payload.
+  ?Payload log:nameOf ?PayloadContext.
+  ?PayloadContext log:includes {
+    :batteryBank :availableWatts ?BatteryWatts.
+    :solarForecast :expectedWatts ?SolarWatts.
+  }.
+  (?BatteryWatts ?SolarWatts) math:sum ?AvailableWatts.
+} => {
+  :clinicMicrogrid rmsg:availableWatts ?AvailableWatts.
+}.
+
+# Inspect the flexible-demand message atomically. The EV chargers are useful, but
+# they are safe to defer so life-safety loads keep running.
+{
+  ?Message rmsg:payloadKind :flexibleDemand;
+    rmsg:payloadGraph ?Payload.
+  ?Payload log:nameOf ?PayloadContext.
+  ?PayloadContext log:includes {
+    :evChargers :shedWatts ?ShedWatts.
+  }.
+} => {
+  :clinicMicrogrid rmsg:deferrableWatts ?ShedWatts.
+  :clinicMicrogrid rmsg:mayDefer :evChargers.
+}.
+
+# The decision combines conclusions from the separate messages, while preserving
+# the evidence that each conclusion came through an explicit message boundary.
+{
+  :clinicMicrogrid rmsg:criticalWatts ?CriticalWatts;
+    rmsg:availableWatts ?AvailableWatts;
+    rmsg:deferrableWatts ?ShedWatts;
+    rmsg:mustKeep :oxygenConcentrator, :vaccineFridge;
+    rmsg:mayDefer :evChargers.
+  (?AvailableWatts ?ShedWatts) math:sum ?ProtectedBudget.
+  ?ProtectedBudget math:greaterThan ?CriticalWatts.
+} => {
+  :clinicMicrogrid rmsg:protectedBudgetWatts ?ProtectedBudget.
+  :clinicMicrogrid rmsg:resilienceAction :protectClinic.
+  :clinicMicrogrid rmsg:keeps :oxygenConcentrator, :vaccineFridge.
+  :clinicMicrogrid rmsg:defers :evChargers.
+}.
+
+# Emit the example report only when the message stream, empty heartbeat, atomic
+# payload inspection, and protection decision have all been derived.
+{
+  :stormClinicLog rmsg:orderedMessages ?Messages.
+  ?Messages list:length ?Count.
+  :m001 rmsg:boundaryExplicit true.
+  :m002 rmsg:boundaryExplicit true.
+  :m003 rmsg:boundaryExplicit true.
+  :m004 rmsg:boundaryExplicit true;
+    rmsg:emptyMessageAllowed true.
+  :clinicMicrogrid rmsg:criticalWatts ?CriticalWatts;
+    rmsg:availableWatts ?AvailableWatts;
+    rmsg:deferrableWatts ?ShedWatts;
+    rmsg:protectedBudgetWatts ?ProtectedBudget;
+    rmsg:resilienceAction :protectClinic.
+  ("# rdf-message-microgrid\n\n## Source files\n\n- [N3 rules](../rdf-message-microgrid.n3)\n- [Input TriG](../input/rdf-message-microgrid.trig)\n\n## Answer\nStorm clinic microgrid accepted: %d RDF Message envelopes were replayed atomically. Critical care needs %d W, current battery plus solar gives %d W, and deferring the EV chargers frees %d W, so the protected budget is %d W. The reasoned action is to keep the oxygen concentrator and vaccine fridge online, while deferring EV charging.\n\n## Why this is an RDF Messages example\nThe input is a single runnable example split across an N3 rule file and a TriG sidecar. The default graph records stream order, offsets, and envelope metadata. Each non-empty named graph is treated as an atomic message payload, and the fourth message is an empty heartbeat. The rules inspect each payload with log:includes inside its own formula, then combine only the derived conclusions needed for the microgrid decision. This keeps the explanation tied to message boundaries instead of silently flattening the stream into one global graph.\n\nThis is intentionally not a parser-level VERSION \\\"1.2-messages\\\" / MESSAGE delimiter test. It is a reasoning example over an already-materialized sidecar representation of a message log." ?Count ?CriticalWatts ?AvailableWatts ?ShedWatts ?ProtectedBudget) string:format ?Block.
+} => {
+  :rdfMessageMicrogridExample log:outputString ?Block.
+  :rdfMessageMicrogridExample :demonstrates :AtomicMessageContext, :EmptyHeartbeat, :ReplayableMessageLog, :ResilientDecisionSupport.
+}.