eyeling 1.24.31 → 1.25.0

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/liar.n3

@@ -3,7 +3,7 @@
 # Example from Patrick Hochstenbach
 # =================================
 
-# expect-exit: 2
+# expect-exit: 65
 
 @prefix : <https://eyereasoner.github.io/ns#>.
 @prefix log: <http://www.w3.org/2000/10/swap/log#>.

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.  

package/examples/rdf-message-microgrid.n3

@@ -6,63 +6,46 @@
 #
 #   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
+# A clinic is running as an islanded microgrid after a storm. Several small
+# systems send RDF data: one message describes life-safety loads, another
+# describes battery and solar status, 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.
+# The companion input is now a true parser-level RDF Message Log. Eyeling handles
+# VERSION "1.2-messages" and MESSAGE delimiters internally, then exposes a replay
+# view using eymsg: ordered envelopes and payload graphs. The N3 rules therefore
+# focus on the domain decision rather than recreating log replay by hand.
 
 @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 eymsg: <https://eyereasoner.github.io/eyeling/vocab/message#>.
 @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.
+# Every envelope in the replay view is an explicit parser-recognized boundary.
 {
-  ?Log a rmsg:MessageLog;
-    rmsg:message ?Message.
-  ?Message a rmsg:MessageEnvelope;
-    rmsg:offset ?Offset.
+  ?Stream a eymsg:RDFMessageStream;
+    eymsg:envelope ?Message.
+  ?Message a eymsg:MessageEnvelope;
+    eymsg:offset ?Offset.
 } => {
-  ?Message rmsg:boundaryExplicit true.
-  ?Log rmsg:replayContains ?Message.
+  ?Message :boundaryExplicit true.
+  ?Stream :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 a eymsg:MessageEnvelope;
+    eymsg:payloadKind eymsg:empty.
 } => {
-  ?Message rmsg:emptyMessageAllowed true.
+  ?Message :emptyMessageAllowed true.
 }.
 
-# Inspect the life-safety message inside its own payload graph.
+# Inspect the life-safety message inside its own parser-replayed payload graph.
 {
-  ?Message rmsg:payloadKind :lifeSafetyLoads;
-    rmsg:payloadGraph ?Payload.
+  ?Message eymsg:payloadGraph ?Payload.
   ?Payload log:nameOf ?PayloadContext.
   ?PayloadContext log:includes {
     :oxygenConcentrator :requiresWatts ?Oxygen.
@@ -70,14 +53,13 @@
   }.
   (?Oxygen ?Fridge) math:sum ?CriticalWatts.
 } => {
-  :clinicMicrogrid rmsg:criticalWatts ?CriticalWatts.
-  :clinicMicrogrid rmsg:mustKeep :oxygenConcentrator, :vaccineFridge.
+  :clinicMicrogrid :criticalWatts ?CriticalWatts.
+  :clinicMicrogrid :mustKeep :oxygenConcentrator, :vaccineFridge.
 }.
 
 # Inspect the power-status message atomically.
 {
-  ?Message rmsg:payloadKind :powerStatus;
-    rmsg:payloadGraph ?Payload.
+  ?Message eymsg:payloadGraph ?Payload.
   ?Payload log:nameOf ?PayloadContext.
   ?PayloadContext log:includes {
     :batteryBank :availableWatts ?BatteryWatts.
@@ -85,57 +67,61 @@
   }.
   (?BatteryWatts ?SolarWatts) math:sum ?AvailableWatts.
 } => {
-  :clinicMicrogrid rmsg:availableWatts ?AvailableWatts.
+  :clinicMicrogrid :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.
+  ?Message eymsg:payloadGraph ?Payload.
   ?Payload log:nameOf ?PayloadContext.
   ?PayloadContext log:includes {
     :evChargers :shedWatts ?ShedWatts.
   }.
 } => {
-  :clinicMicrogrid rmsg:deferrableWatts ?ShedWatts.
-  :clinicMicrogrid rmsg:mayDefer :evChargers.
+  :clinicMicrogrid :deferrableWatts ?ShedWatts.
+  :clinicMicrogrid :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.
+  :clinicMicrogrid :criticalWatts ?CriticalWatts;
+    :availableWatts ?AvailableWatts;
+    :deferrableWatts ?ShedWatts;
+    :mustKeep :oxygenConcentrator, :vaccineFridge;
+    :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.
+  :clinicMicrogrid :protectedBudgetWatts ?ProtectedBudget.
+  :clinicMicrogrid :resilienceAction :protectClinic.
+  :clinicMicrogrid :keeps :oxygenConcentrator, :vaccineFridge.
+  :clinicMicrogrid :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.
+  ?Stream a eymsg:RDFMessageStream;
+    eymsg:orderedEnvelopes ?Messages;
+    eymsg:firstEnvelope ?M1.
   ?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.
+  ?M1 :boundaryExplicit true;
+    eymsg:nextEnvelope ?M2.
+  ?M2 :boundaryExplicit true;
+    eymsg:nextEnvelope ?M3.
+  ?M3 :boundaryExplicit true;
+    eymsg:nextEnvelope ?M4.
+  ?M4 :boundaryExplicit true;
+    :emptyMessageAllowed true.
+  :clinicMicrogrid :criticalWatts ?CriticalWatts;
+    :availableWatts ?AvailableWatts;
+    :deferrableWatts ?ShedWatts;
+    :protectedBudgetWatts ?ProtectedBudget;
+    :resilienceAction :protectClinic.
+  ("# rdf-message-microgrid\n\n## Source files\n\n- [N3 rules](../rdf-message-microgrid.n3)\n- [Input RDF Message Log](../input/rdf-message-microgrid.trig)\n\n## Answer\nStorm clinic microgrid accepted: %d parser-replayed RDF Messages were processed 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 Message Log example\nThe 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." ?Count ?CriticalWatts ?AvailableWatts ?ShedWatts ?ProtectedBudget) string:format ?Block.
 } => {
   :rdfMessageMicrogridExample log:outputString ?Block.
-  :rdfMessageMicrogridExample :demonstrates :AtomicMessageContext, :EmptyHeartbeat, :ReplayableMessageLog, :ResilientDecisionSupport.
+  :rdfMessageMicrogridExample :demonstrates :ParserLevelMessageLog, :AtomicMessageContext, :EmptyHeartbeat, :ReplayableMessageLog, :ResilientDecisionSupport.
 }.

package/examples/rdf-messages.n3

@@ -11,115 +11,102 @@
 # The RDF Messages draft defines an RDF Message as an RDF dataset interpreted
 # atomically, an RDF Message Stream as an ordered sequence of messages, and an
 # RDF Message Log as a replayable record of such a stream. The draft also says
-# that messages should not be combined by default and that blank node labels are
+# that messages should not be combined by default and that blank-node labels are
 # scoped to the message in which they occur.
 #
-# This Eyeling example demonstrates those ideas in ordinary N3/TriG rather than
-# in a parser-level RDF Message Log with VERSION "1.2-messages" and MESSAGE
-# delimiters. The companion TriG file therefore has two layers:
+# This example now uses the parser-level syntax directly: the companion input
+# starts with VERSION "1.2-messages" and separates messages with MESSAGE
+# delimiters. Eyeling handles those delimiters before N3 reasoning starts and
+# exposes an internal eymsg: replay view: a stream resource, ordered envelopes,
+# next-envelope links, payload kind, and one payload graph per non-empty message.
 #
-#   1. application-local envelope facts in the default graph, such as message
-#      order, offset, expected result, and the textual blank-node label seen in
-#      the original stream; and
-#   2. one named graph per non-empty message payload, treated as the atomic RDF
-#      dataset/message to be inspected.
-#
-# The rules below validate a replay archive with three message envelopes. The
-# middle message is an empty heartbeat. The first and third messages both record
-# the local blank-node label "_:b0"; because this sidecar is normal TriG, the
-# actual TriG blank nodes are unique, while the envelope records show the
-# message-scoped label reuse that a true RDF Message Log parser would preserve
-# by resetting blank-node scope at each MESSAGE delimiter.
+# The rules below validate that replay view. They never hand-model message
+# envelopes in the TriG sidecar. They inspect payload graphs atomically, accept
+# the delimiter-only heartbeat, and check that a reused source-local blank-node
+# label becomes two distinct message-scoped blank nodes.
 
 @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 eymsg: <https://eyereasoner.github.io/eyeling/vocab/message#>.
 @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#>.
 
-# A message with an offset inside a log has an explicit replay boundary.
-# The envelope resource is application-local; the payload graph is the dataset
-# treated as the RDF Message.
+# Every parser-replayed envelope is an explicit message boundary.
 {
-  ?Log a rmsg:MessageLog;
-    rmsg:message ?Message.
-  ?Message a rmsg:MessageEnvelope;
-    rmsg:offset ?Offset.
+  ?Stream a eymsg:RDFMessageStream;
+    eymsg:envelope ?Envelope.
+  ?Envelope a eymsg:MessageEnvelope;
+    eymsg:offset ?Offset.
 } => {
-  ?Message rmsg:boundaryExplicit true.
-  ?Log rmsg:replayContains ?Message.
+  ?Envelope :boundaryExplicit true.
+  ?Stream :replayContains ?Envelope.
 }.
 
-# The payload is a dataset-like named graph. Inspect it with log:includes instead
-# of merging all payload triples into the global graph.
+# Payload graphs are inspected with log:includes, so the observations remain
+# inside their message contexts instead of being silently merged.
 {
-  ?Message a rmsg:MessageEnvelope;
-    rmsg:expectedResult ?Result;
-    rmsg:payloadGraph ?Payload.
+  ?Envelope a eymsg:MessageEnvelope;
+    eymsg:payloadKind eymsg:nonEmpty;
+    eymsg:payloadGraph ?Payload.
   ?Payload log:nameOf ?PayloadContext.
   ?PayloadContext log:includes { ?Observation sosa:hasSimpleResult ?Result. }.
 } => {
-  ?Message rmsg:payloadResult ?Result.
-}.
-
-# Empty messages are legal RDF Messages. Here the empty second envelope acts as
-# a heartbeat/keep-alive and still occupies a boundary in the replay archive.
-{
-  ?Message a rmsg:MessageEnvelope;
-    rmsg:payloadKind :heartbeat.
-} => {
-  ?Message rmsg:emptyMessageAllowed true.
-  :HeartbeatEvidence :accepted ?Message.
+  ?Envelope :payloadObservation ?Observation.
+  ?Envelope :payloadResult ?Result.
 }.
 
-# The same local blank-node label may recur in different messages. In this
-# plain-TriG sidecar the real blank nodes are unique, and the envelope metadata
-# records the per-message label visible in the source stream.
+# Empty messages are valid RDF Messages. The second envelope is a heartbeat even
+# though it has no payload graph.
 {
-  ?First a rmsg:MessageEnvelope;
-    rmsg:localBlankLabel ?Label.
-  ?Second a rmsg:MessageEnvelope;
-    rmsg:localBlankLabel ?Label.
-  ?First log:notEqualTo ?Second.
+  ?Envelope a eymsg:MessageEnvelope;
+    eymsg:payloadKind eymsg:empty.
 } => {
-  :BlankNodeScope :reusedLabel ?Label.
-  :BlankNodeScope :isPerMessage true.
+  ?Envelope :emptyMessageAllowed true.
+  :HeartbeatEvidence :accepted ?Envelope.
 }.
 
-# Different observations from the same sensor are not a global contradiction:
-# by default, message payloads remain separate communication contexts.
+# The input deliberately reuses the same source-local blank-node label in message
+# 1 and message 3. Eyeling rewrites labels per message, so these are distinct
+# blank nodes after replay.
 {
-  ?First a rmsg:MessageEnvelope;
-    rmsg:payloadResult ?FirstResult.
-  ?Second a rmsg:MessageEnvelope;
-    rmsg:payloadResult ?SecondResult.
-  ?FirstResult math:notEqualTo ?SecondResult.
-  ?First log:notEqualTo ?Second.
+  ?Stream a eymsg:RDFMessageStream;
+    eymsg:firstEnvelope ?First.
+  ?First eymsg:nextEnvelope ?Second;
+    :payloadObservation ?FirstObservation;
+    :payloadResult ?FirstResult.
+  ?Second eymsg:nextEnvelope ?Third;
+    :emptyMessageAllowed true.
+  ?Third :payloadObservation ?ThirdObservation;
+    :payloadResult ?ThirdResult.
+  ?FirstObservation log:notEqualTo ?ThirdObservation.
+  ?FirstResult math:notEqualTo ?ThirdResult.
 } => {
+  :BlankNodeScope :reusedSourceLabelIsMessageScoped true.
   :MessageContext :differentObservationsStayContextual true.
 }.
 
-# The Eyeling verdict is emitted only when all message-specific validations have
-# been derived from the log metadata, ordered message list, payload graphs, and
-# built-ins.
+# The Eyeling verdict is emitted only when all parser-replayed message-specific
+# validations have been derived from the stream, ordered envelopes, payload
+# graphs, and built-ins.
 {
-  :temperatureLog rmsg:orderedMessages ?Messages.
+  ?Stream a eymsg:RDFMessageStream;
+    eymsg:orderedEnvelopes ?Messages;
+    eymsg:firstEnvelope ?First.
   ?Messages list:length ?Count.
-  :m001 rmsg:boundaryExplicit true;
-    rmsg:payloadResult ?FirstResult.
-  :m002 rmsg:boundaryExplicit true;
-    rmsg:emptyMessageAllowed true.
-  :m003 rmsg:boundaryExplicit true;
-    rmsg:payloadResult ?SecondResult.
-  :BlankNodeScope :reusedLabel ?Label;
-    :isPerMessage true.
+  ?First :boundaryExplicit true;
+    :payloadResult ?FirstResult;
+    eymsg:nextEnvelope ?Second.
+  ?Second :boundaryExplicit true;
+    :emptyMessageAllowed true;
+    eymsg:nextEnvelope ?Third.
+  ?Third :boundaryExplicit true;
+    :payloadResult ?SecondResult.
+  :BlankNodeScope :reusedSourceLabelIsMessageScoped true.
   :MessageContext :differentObservationsStayContextual true.
-  ("# rdf-messages\n\n## Source files\n\n- [N3 rules](../rdf-messages.n3)\n- [Input TriG](../input/rdf-messages.trig)\n\n## Answer\nRDF Message replay archive accepted: %d explicit message boundaries are preserved. Message :m002 is an empty heartbeat, and the local blank-node label %s is safely reused in separate message envelopes.\n\n## Explanation\nThe 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, %s and %s, are different observations from the same stream but are contextualized by their message boundaries.\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 ?Label ?FirstResult ?SecondResult) string:format ?Block.
+  ("# rdf-messages\n\n## Source files\n\n- [N3 rules](../rdf-messages.n3)\n- [Input RDF Message Log](../input/rdf-messages.trig)\n\n## Answer\nRDF Message Log accepted: %d 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.\n\n## Explanation\nThe 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, %s and %s, are different observations from the same stream and remain contextualized by their message boundaries." ?Count ?FirstResult ?SecondResult) string:format ?Block.
 } => {
   :rdfMessagesExample log:outputString ?Block.
-  :rdfMessagesExample :demonstrates :ExplicitBoundaries, :AtomicMessageContext, :EmptyHeartbeat, :MessageScopedBlankNodes, :ReplayableMessageLog.
+  :rdfMessagesExample :demonstrates :ParserLevelMessageLog, :ExplicitBoundaries, :AtomicMessageContext, :EmptyHeartbeat, :MessageScopedBlankNodes.
 }.