eyeling 1.24.30 → 1.24.33

package/examples/input/rdf-message-flow.trig

@@ -1,50 +1,36 @@
-# ==============================
-# RDF Message Flow input sidecar
-# ==============================
+# =============================
+# RDF Message Flow message log
+# =============================
 #
 # This file is the data half of the runnable example:
 #
 #   eyeling -r examples/rdf-message-flow.n3 examples/input/rdf-message-flow.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 stream is an
-# ordered sequence of such messages, and that messages in a stream should not be
-# combined by default. To demonstrate those ideas in Eyeling today, the default
-# graph below contains example-local envelope records (:m001 ... :m005) and each
-# non-empty message payload is placed in its own named graph (in:payload001 ...
-# in:payload005).
+# It is a parser-level RDF Message Log using the RDF 1.2 Messages draft syntax:
+# VERSION "1.2-messages" selects message-log parsing and MESSAGE delimiters
+# separate the ordered RDF Messages. Eyeling replays this log internally by
+# materializing message envelopes and one payload graph per non-empty message.
+# The sidecar itself does not contain application-level envelope facts.
 #
-# The envelope IRIs are not identifiers for RDF Messages defined by the spec;
-# they are application-level records used by the flow-control rules. The named
-# payload graphs are the datasets/messages being interpreted atomically. The
-# third envelope is an empty heartbeat, which is valid because RDF Messages may
-# be empty. Blank node labels are kept unique because this sidecar is ordinary
-# TriG; a true RDF Message Log parser would reset blank-node scope per MESSAGE.
+# The third message is deliberately empty. The same blank node label _:obs is
+# also reused in several messages; an RDF Message Log parser scopes blank node
+# identifiers to each message, so those labels do not collide.
 
-@prefix : <https://eyereasoner.github.io/eyeling/examples/rdf-message-flow#> .
-@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#> .
-@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#> .
-@prefix see: <https://example.org/see#> .
-@prefix in: <https://example.org/see/input#> .
+VERSION "1.2-messages"
+PREFIX : <https://eyereasoner.github.io/eyeling/examples/rdf-message-flow#>
+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#>
+PREFIX see: <https://example.org/see#>
+PREFIX in: <https://example.org/see/input#>
 
-:temperatureFlow a flow:RDFMessageStream .
-:temperatureFlow flow:orderedEnvelopes (:m001 :m002 :m003 :m004 :m005) .
-:temperatureFlow flow:envelope :m001 .
-:temperatureFlow flow:envelope :m002 .
-:temperatureFlow flow:envelope :m003 .
-:temperatureFlow flow:envelope :m004 .
-:temperatureFlow flow:envelope :m005 .
-:temperatureFlow :producer :thermometerA .
-:temperatureFlow :consumer :flowProcessor .
-:temperatureFlow :pipeline (:ingest :validate :interpret :route :sink) .
-:temperatureFlow :highThreshold 26 .
+# Message 1: stream context plus first observation.
+:temperatureFlow a flow:RDFMessageStream ;
+  :producer :thermometerA ;
+  :consumer :flowProcessor ;
+  :pipeline (:ingest :validate :interpret :route :sink) ;
+  :highThreshold 26 .
 
 :thermometerA a flow:StreamProducer .
 :flowProcessor a flow:StreamConsumer .
@@ -52,77 +38,42 @@
 :alertSink a flow:StreamConsumer .
 :heartbeatSink a flow:StreamConsumer .
 
-:m001 a flow:MessageEnvelope .
-:m001 :atStage :ingest .
-:m001 flow:offset 1 .
-:m001 flow:nextEnvelope :m002 .
-:m001 prov:generatedAtTime "2026-05-12T18:20:00Z"^^xsd:dateTime .
-:m001 flow:payloadKind :observation .
-:m001 flow:expectedResult 21 .
-:m001 flow:payloadGraph in:payload001 .
+_:obs a sosa:Observation ;
+  sosa:madeBySensor :thermometerA ;
+  sosa:resultTime "2026-05-12T18:20:00Z"^^xsd:dateTime ;
+  sosa:hasSimpleResult 21 .
 
-:m002 a flow:MessageEnvelope .
-:m002 flow:offset 2 .
-:m002 flow:nextEnvelope :m003 .
-:m002 prov:generatedAtTime "2026-05-12T18:21:00Z"^^xsd:dateTime .
-:m002 flow:payloadKind :observation .
-:m002 flow:expectedResult 22 .
-:m002 flow:payloadGraph in:payload002 .
+in:run a see:InputDataset ;
+  see:name "rdf_message_flow" ;
+  see:title "RDF Message Flow" ;
+  see:sourceFile "examples/rdf-message-flow.n3" ;
+  see:description "A true RDF 1.2 Message Log sidecar. Eyeling parses VERSION 1.2-messages and MESSAGE delimiters into replayable internal message envelopes." ;
+  see:compiler "Eyeling RDF Message Log input" .
 
-:m003 a flow:MessageEnvelope .
-:m003 flow:offset 3 .
-:m003 flow:nextEnvelope :m004 .
-:m003 prov:generatedAtTime "2026-05-12T18:22:00Z"^^xsd:dateTime .
-:m003 flow:payloadKind :heartbeat .
+MESSAGE
 
-:m004 a flow:MessageEnvelope .
-:m004 flow:offset 4 .
-:m004 flow:nextEnvelope :m005 .
-:m004 prov:generatedAtTime "2026-05-12T18:23:00Z"^^xsd:dateTime .
-:m004 flow:payloadKind :observation .
-:m004 flow:expectedResult 28 .
-:m004 flow:payloadGraph in:payload004 .
+# Message 2: normal observation.
+_:obs a sosa:Observation ;
+  sosa:madeBySensor :thermometerA ;
+  sosa:resultTime "2026-05-12T18:21:00Z"^^xsd:dateTime ;
+  sosa:hasSimpleResult 22 .
 
-:m005 a flow:MessageEnvelope .
-:m005 flow:offset 5 .
-:m005 prov:generatedAtTime "2026-05-12T18:24:00Z"^^xsd:dateTime .
-:m005 flow:payloadKind :observation .
-:m005 flow:expectedResult 29 .
-:m005 flow:payloadGraph in:payload005 .
+MESSAGE
 
-in:payload001 {
-  _:m001b0 a sosa:Observation .
-  _:m001b0 sosa:madeBySensor :thermometerA .
-  _:m001b0 sosa:resultTime "2026-05-12T18:20:00Z"^^xsd:dateTime .
-  _:m001b0 sosa:hasSimpleResult 21 .
-}
+# Message 3: empty heartbeat. The next MESSAGE delimiter finalizes this empty
+# message and opens message 4.
+MESSAGE
 
-in:payload002 {
-  _:m002b0 a sosa:Observation .
-  _:m002b0 sosa:madeBySensor :thermometerA .
-  _:m002b0 sosa:resultTime "2026-05-12T18:21:00Z"^^xsd:dateTime .
-  _:m002b0 sosa:hasSimpleResult 22 .
-}
+# Message 4: hot observation.
+_:obs a sosa:Observation ;
+  sosa:madeBySensor :thermometerA ;
+  sosa:resultTime "2026-05-12T18:23:00Z"^^xsd:dateTime ;
+  sosa:hasSimpleResult 28 .
 
-in:payload004 {
-  _:m004b0 a sosa:Observation .
-  _:m004b0 sosa:madeBySensor :thermometerA .
-  _:m004b0 sosa:resultTime "2026-05-12T18:23:00Z"^^xsd:dateTime .
-  _:m004b0 sosa:hasSimpleResult 28 .
-}
+MESSAGE
 
-in:payload005 {
-  _:m005b0 a sosa:Observation .
-  _:m005b0 sosa:madeBySensor :thermometerA .
-  _:m005b0 sosa:resultTime "2026-05-12T18:24:00Z"^^xsd:dateTime .
-  _:m005b0 sosa:hasSimpleResult 29 .
-}
-
-in:metadata {
-  in:run a see:InputDataset .
-  in:run see:name "rdf_message_flow" .
-  in:run see:title "RDF Message Flow" .
-  in:run see:sourceFile "examples/rdf-message-flow.n3" .
-  in:run see:description "A single Eyeling example split across an N3 rule file and a TriG input sidecar. It models an ordered RDF Message Stream using 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" .
-}
+# Message 5: hot observation. EOF finalizes the message.
+_:obs a sosa:Observation ;
+  sosa:madeBySensor :thermometerA ;
+  sosa:resultTime "2026-05-12T18:24:00Z"^^xsd:dateTime ;
+  sosa:hasSimpleResult 29 .

package/examples/input/rdf-message-microgrid.trig

@@ -1,89 +1,56 @@
-# ===================================
-# RDF Message Microgrid input sidecar
-# ===================================
+# ==================================
+# RDF Message Microgrid message log
+# ==================================
 #
 # This file is the data half of the runnable example:
 #
 #   eyeling -r examples/rdf-message-microgrid.n3 examples/input/rdf-message-microgrid.trig
 #
 # The scene is a clinic operating as an islanded microgrid after a storm. The
-# data arrives as a replayable stream of atomic messages: life-safety loads,
-# power status, flexible demand, and an empty heartbeat. The default graph holds
-# application-local envelope facts, while each non-empty message payload is kept
-# in a named graph.
-#
-# The envelope IRIs are not RDF Message identifiers defined by the specification;
-# they are local replay records for this example. The named graphs are the
-# datasets/messages interpreted atomically by the N3 rules.
-
-@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 see: <https://example.org/see#> .
-@prefix in: <https://example.org/see/input#> .
+# data arrives as a true RDF Message Log: life-safety loads, power status,
+# flexible demand, and an empty heartbeat. Eyeling parses the MESSAGE boundaries
+# internally and exposes the replay to the N3 rules as eymsg: envelopes.
 
-:stormClinicLog a rmsg:MessageLog .
-:stormClinicLog rmsg:orderedMessages (:m001 :m002 :m003 :m004) .
-:stormClinicLog rmsg:message :m001 .
-:stormClinicLog rmsg:message :m002 .
-:stormClinicLog rmsg:message :m003 .
-:stormClinicLog rmsg:message :m004 .
-:stormClinicLog rmsg:retentionPolicy "storm replay archive" .
+VERSION "1.2-messages"
+PREFIX : <https://eyereasoner.github.io/eyeling/examples/rdf-message-microgrid#>
+PREFIX see: <https://example.org/see#>
+PREFIX in: <https://example.org/see/input#>
 
-:m001 a rmsg:MessageEnvelope .
-:m001 rmsg:offset 1 .
-:m001 prov:generatedAtTime "2026-05-15T19:00:00Z"^^xsd:dateTime .
-:m001 rmsg:payloadKind :lifeSafetyLoads .
-:m001 rmsg:payloadGraph in:lifeSafetyPayload .
+# Message 1: life-safety loads plus example metadata.
+:oxygenConcentrator a :LifeSafetyLoad ;
+  :requiresWatts 500 ;
+  :serves :respiratoryCareRoom .
 
-:m002 a rmsg:MessageEnvelope .
-:m002 rmsg:offset 2 .
-:m002 prov:generatedAtTime "2026-05-15T19:01:00Z"^^xsd:dateTime .
-:m002 rmsg:payloadKind :powerStatus .
-:m002 rmsg:payloadGraph in:powerPayload .
+:vaccineFridge a :ColdChainLoad ;
+  :requiresWatts 120 ;
+  :serves :vaccineColdChain .
 
-:m003 a rmsg:MessageEnvelope .
-:m003 rmsg:offset 3 .
-:m003 prov:generatedAtTime "2026-05-15T19:02:00Z"^^xsd:dateTime .
-:m003 rmsg:payloadKind :flexibleDemand .
-:m003 rmsg:payloadGraph in:flexPayload .
+in:run a see:InputDataset ;
+  see:name "rdf_message_microgrid" ;
+  see:title "RDF Message Microgrid" ;
+  see:sourceFile "examples/rdf-message-microgrid.n3" ;
+  see:description "A true RDF 1.2 Message Log for a storm clinic microgrid. Eyeling parses MESSAGE delimiters into replayable internal message envelopes for bounded, explainable load-shedding." ;
+  see:compiler "Eyeling RDF Message Log input" .
 
-:m004 a rmsg:MessageEnvelope .
-:m004 rmsg:offset 4 .
-:m004 prov:generatedAtTime "2026-05-15T19:03:00Z"^^xsd:dateTime .
-:m004 rmsg:payloadKind :heartbeat .
+MESSAGE
 
-in:lifeSafetyPayload {
-  :oxygenConcentrator a :LifeSafetyLoad .
-  :oxygenConcentrator :requiresWatts 500 .
-  :oxygenConcentrator :serves :respiratoryCareRoom .
+# Message 2: current power status.
+:batteryBank a :PowerReserve ;
+  :availableWatts 650 ;
+  :state :islanded .
 
-  :vaccineFridge a :ColdChainLoad .
-  :vaccineFridge :requiresWatts 120 .
-  :vaccineFridge :serves :vaccineColdChain .
-}
+:solarForecast a :NearTermForecast ;
+  :expectedWatts 150 .
 
-in:powerPayload {
-  :batteryBank a :PowerReserve .
-  :batteryBank :availableWatts 650 .
-  :batteryBank :state :islanded .
+MESSAGE
 
-  :solarForecast a :NearTermForecast .
-  :solarForecast :expectedWatts 150 .
-}
+# Message 3: flexible demand that can safely be shed.
+:evChargers a :FlexibleLoad ;
+  :shedWatts 600 ;
+  :serves :staffVehicles .
 
-in:flexPayload {
-  :evChargers a :FlexibleLoad .
-  :evChargers :shedWatts 600 .
-  :evChargers :serves :staffVehicles .
-}
+MESSAGE
 
-in:metadata {
-  in:run a see:InputDataset .
-  in:run see:name "rdf_message_microgrid" .
-  in:run see:title "RDF Message Microgrid" .
-  in:run see:sourceFile "examples/rdf-message-microgrid.n3" .
-  in:run see:description "A storm clinic microgrid example using application-local RDF Message envelopes and named payload graphs so a reasoner can make a bounded, explainable load-shedding decision." .
-  in:run see:compiler "Eyeling RDF/TriG input sidecar" .
-}
+# Message 4: empty heartbeat. The next MESSAGE delimiter finalizes this empty
+# message and leaves no trailing payload.
+MESSAGE

package/examples/input/rdf-messages.trig

@@ -1,90 +1,47 @@
-# ==========================
-# RDF Messages input sidecar
-# ==========================
+# ===============================
+# RDF Messages parser-level input
+# ===============================
 #
 # 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.
+# It is a true RDF Message Log. VERSION "1.2-messages" tells Eyeling to parse
+# MESSAGE delimiters as message boundaries before ordinary N3 reasoning starts.
+# Eyeling then materializes an internal eymsg: replay view with ordered envelopes
+# and one payload graph per non-empty 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 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#> .
-@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#> .
-@prefix see: <https://example.org/see#> .
-@prefix in: <https://example.org/see/input#> .
-
-: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 .
-
-: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:payload001 {
-  _:m001b0 a sosa:Observation .
-  _:m001b0 sosa:madeBySensor :thermometerA .
-  _:m001b0 sosa:resultTime "2026-05-12T18:20:00Z"^^xsd:dateTime .
-  _:m001b0 sosa:hasSimpleResult 22 .
-}
-
-in:payload003 {
-  _:m003b0 a sosa:Observation .
-  _:m003b0 sosa:madeBySensor :thermometerA .
-  _:m003b0 sosa:resultTime "2026-05-12T18:25:00Z"^^xsd:dateTime .
-  _:m003b0 sosa:hasSimpleResult 23 .
-}
-
-in:metadata {
-  in:run a see:InputDataset .
-  in:run see:name "rdf_messages" .
-  in:run see:title "RDF Messages" .
-  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" .
-}
+# The second message is deliberately empty. The first and third messages both use
+# the source-local blank-node label _:b0. Because blank-node labels are scoped to
+# each RDF Message, Eyeling rewrites them into distinct internal blank nodes.
+
+VERSION "1.2-messages"
+PREFIX : <https://eyereasoner.github.io/eyeling/examples/rdf-messages#>
+PREFIX sosa: <http://www.w3.org/ns/sosa/>
+PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>
+PREFIX see: <https://example.org/see#>
+PREFIX in: <https://example.org/see/input#>
+
+# Message 1: first temperature observation plus example metadata.
+_:b0 a sosa:Observation ;
+  sosa:madeBySensor :thermometerA ;
+  sosa:resultTime "2026-05-12T18:20:00Z"^^xsd:dateTime ;
+  sosa:hasSimpleResult 22 .
+
+in:run a see:InputDataset ;
+  see:name "rdf_messages" ;
+  see:title "RDF Messages" ;
+  see:sourceFile "examples/rdf-messages.n3" ;
+  see:description "A true RDF 1.2 Message Log. Eyeling parses VERSION 1.2-messages and MESSAGE delimiters into replayable internal message envelopes." ;
+  see:compiler "Eyeling RDF Message Log input" .
+
+MESSAGE
+
+# Message 2: empty heartbeat.
+MESSAGE
+
+# Message 3: second observation. The _:b0 label is intentionally reused here.
+_:b0 a sosa:Observation ;
+  sosa:madeBySensor :thermometerA ;
+  sosa:resultTime "2026-05-12T18:25:00Z"^^xsd:dateTime ;
+  sosa:hasSimpleResult 23 .

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

@@ -3,10 +3,10 @@
 ## Source files  
 
 - [N3 rules](../rdf-message-flow.n3)  
-- [Input TriG](../input/rdf-message-flow.trig)  
+- [Input RDF Message Log](../input/rdf-message-flow.trig)  
 
 ## Answer  
-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.  
+Continuous RDF Message flow accepted: 5 ordered parser-replayed message envelopes moved through the ingest → validate → interpret → route → sink pipeline. The threshold was 26, so results 21 and 22 were archived, the empty heartbeat kept the stream alive, and results 28 and 29 were emitted as alerts.  
 
 ## Explanation  
-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.  
+The input sidecar is now a true RDF Message Log using VERSION \"1.2-messages\" and MESSAGE delimiters. Eyeling parses the log internally into an eymsg: replay view with ordered envelopes, offsets, next-envelope links, and one payload graph per non-empty message. Only the first replayed envelope starts at ingress; each envelope must reach :sink before the continuous-flow rule releases its eymsg:nextEnvelope. Observation payloads are inspected with log:includes inside their own message formula, and the delimiter-only third message is replayed as an empty heartbeat. This keeps message boundaries in the parser/runtime instead of modeling them by hand in the TriG sidecar.  

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

@@ -3,12 +3,10 @@
 ## Source files  
 
 - [N3 rules](../rdf-message-microgrid.n3)  
-- [Input TriG](../input/rdf-message-microgrid.trig)  
+- [Input RDF Message Log](../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.  
+Storm clinic microgrid accepted: 4 parser-replayed RDF Messages were processed 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.  
+## Why this is an RDF Message Log example  
+The input now uses VERSION \"1.2-messages\" and MESSAGE delimiters. Eyeling parses those boundaries internally into an eymsg: replay view, so the rules do not need hand-written application envelopes. Each non-empty message is inspected with log:includes inside its own payload formula, and the final delimiter-only message is replayed as an empty heartbeat. The decision combines only the derived conclusions needed for load shedding while keeping the explanation tied to explicit message boundaries.  

package/examples/output/rdf-messages.md

@@ -3,12 +3,10 @@
 ## Source files  
 
 - [N3 rules](../rdf-messages.n3)  
-- [Input TriG](../input/rdf-messages.trig)  
+- [Input RDF Message Log](../input/rdf-messages.trig)  
 
 ## Answer  
-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.  
+RDF Message Log accepted: 3 parser-replayed message boundaries are preserved. The middle message is an empty heartbeat, and the same source-local blank-node label is safely reused because Eyeling scopes blank nodes per message.  
 
 ## Explanation  
-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.  
+The input now uses VERSION \"1.2-messages\" and MESSAGE delimiters instead of hand-written application envelope facts. Eyeling parses the log internally into an eymsg: replay view with ordered envelopes and one payload graph per non-empty message. The rules inspect each payload with log:includes inside its own message formula, 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 and remain contextualized by their message boundaries.