eyeling 1.24.25 → 1.24.27

package/README.md

@@ -3,6 +3,8 @@
 [![npm version](https://img.shields.io/npm/v/eyeling.svg)](https://www.npmjs.com/package/eyeling)
 [![DOI](https://img.shields.io/badge/DOI-10.5281%2Fzenodo.19068086-blue.svg)](https://doi.org/10.5281/zenodo.19068086)
 
+![Eyeling](eyeling.png)
+
 A compact [Notation3 (N3)](https://notation3.org/) reasoner in **JavaScript**.
 
 ## Quick start

package/dist/browser/eyeling.browser.js

@@ -844,6 +844,62 @@ function compileSwapRegex(pattern, extraFlags) {
   }
 }
 
+function expandSwapRegexReplacement(template, captures) {
+  // SWAP/N3 examples use $1-style capture references, but tests also rely on
+  // Perl-ish escaping in replacement strings: \\$ means a literal dollar sign
+  // and \\ means a literal backslash.  JavaScript's replacement strings do not
+  // interpret those escapes, so expand the replacement explicitly in a callback.
+  let out = '';
+  const text = String(template);
+
+  for (let i = 0; i < text.length; i++) {
+    const ch = text[i];
+
+    if (ch === '\\') {
+      if (i + 1 < text.length && (text[i + 1] === '$' || text[i + 1] === '\\')) {
+        out += text[++i];
+      } else {
+        out += ch;
+      }
+      continue;
+    }
+
+    if (ch === '$') {
+      if (i + 1 < text.length && text[i + 1] === '$') {
+        out += '$';
+        i++;
+        continue;
+      }
+
+      let j = i + 1;
+      while (j < text.length && /[0-9]/.test(text[j])) j++;
+      if (j > i + 1) {
+        const digits = text.slice(i + 1, j);
+        let chosen = null;
+        for (let k = digits.length; k > 0; k--) {
+          const n = Number(digits.slice(0, k));
+          if (n > 0 && n < captures.length) {
+            chosen = { n, len: k };
+            break;
+          }
+        }
+        if (chosen) {
+          out += captures[chosen.n] == null ? '' : String(captures[chosen.n]);
+          out += digits.slice(chosen.len);
+        } else {
+          out += '$' + digits;
+        }
+        i = j - 1;
+        continue;
+      }
+    }
+
+    out += ch;
+  }
+
+  return out;
+}
+
 // -----------------------------------------------------------------------------
 // Strict numeric literal parsing for math: builtins
 // -----------------------------------------------------------------------------
@@ -1699,7 +1755,7 @@ function __pushBuiltinDeltaLimited(out, delta, maxResults) {
 
 function __collectListLikeTermsFromTerm(t, out, seen) {
   if (t instanceof ListTerm || t instanceof OpenListTerm) {
-    const k = termFastKey ? termFastKey(t) : null;
+    const k = termFastKey(t);
     if (k === null || !seen.has(k)) {
       if (k !== null) seen.add(k);
       out.push(t);
@@ -4222,7 +4278,11 @@ function evalBuiltin(goal, subst, facts, backRules, depth, varGen, maxResults) {
     const re = compileSwapRegex(searchStr, 'g');
     if (!re) return [];
 
-    const outStr = dataStr.replace(re, replStr);
+    const outStr = dataStr.replace(re, (...args) => {
+      const captureEnd = args.length - (typeof args.at(-1) === 'object' ? 3 : 2);
+      const captures = args.slice(0, Math.max(1, captureEnd));
+      return expandSwapRegexReplacement(replStr, captures);
+    });
     const lit = makeStringLiteral(outStr);
 
     if (g.o instanceof Var) {
@@ -11498,6 +11558,20 @@ class Parser {
     if (this.peek().typ === 'Ident' && (this.peek().value || '') === 'a') {
       this.next();
       pred = internIri(RDF_NS + 'type');
+    } else if (this.peek().typ === 'Ident' && (this.peek().value || '') === 'has') {
+      // N3 syntactic sugar is also valid in predicate-object lists,
+      // including blank node property lists: [ has :p :o ] means _:b :p :o.
+      this.next();
+      pred = this.parseTerm();
+    } else if (this.peek().typ === 'Ident' && (this.peek().value || '') === 'is') {
+      // N3 syntactic sugar: [ is :p of :s ] means :s :p _:b.
+      this.next();
+      pred = this.parseTerm();
+      if (!(this.peek().typ === 'Ident' && (this.peek().value || '') === 'of')) {
+        this.fail(`Expected 'of' after 'is <expr>', got ${this.peek().toString()}`);
+      }
+      this.next();
+      invert = true;
     } else if (this.peek().typ === 'OpPredInvert') {
       this.next();
       pred = this.parseTerm();

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

@@ -1,5 +1,29 @@
+# ==============================
+# RDF Message Flow input sidecar
+# ==============================
+#
+# 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).
+#
+# 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.
+
 @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#> .
@@ -10,77 +34,87 @@
 @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.
-
-:temperatureFlow a msg:MessageStream .
-:temperatureFlow msg:orderedMessages (:m001 :m002 :m003 :m004 :m005) .
-:temperatureFlow msg:message :m001 .
-:temperatureFlow msg:message :m002 .
-:temperatureFlow msg:message :m003 .
-:temperatureFlow msg:message :m004 .
-:temperatureFlow msg:message :m005 .
+: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 .
+
+:thermometerA a flow:StreamProducer .
+:flowProcessor a flow:StreamConsumer .
+:archiveSink a flow:StreamConsumer .
+:alertSink a flow:StreamConsumer .
+:heartbeatSink a flow:StreamConsumer .
+
+:m001 a flow:MessageEnvelope .
 :m001 :atStage :ingest .
-:m001 a msg:RDFMessage .
-:m001 msg:offset 1 .
-:m001 msg:nextMessage :m002 .
-:m001 prov:generatedAtTime "2026-05-12T18:20:00Z" .
-:m001 msg:payloadKind :observation .
-:m001 msg:expectedResult 21 .
-:m001 msg:payload in:formula1 .
-:m002 a msg:RDFMessage .
-:m002 msg:offset 2 .
-:m002 msg:nextMessage :m003 .
-:m002 prov:generatedAtTime "2026-05-12T18:21:00Z" .
-:m002 msg:payloadKind :observation .
-:m002 msg:expectedResult 22 .
-:m002 msg:payload in:formula2 .
-:m003 a msg:RDFMessage .
-:m003 msg:offset 3 .
-:m003 msg:nextMessage :m004 .
-:m003 prov:generatedAtTime "2026-05-12T18:22:00Z" .
-:m003 msg:payloadKind :heartbeat .
-:m004 a msg:RDFMessage .
-:m004 msg:offset 4 .
-:m004 msg:nextMessage :m005 .
-:m004 prov:generatedAtTime "2026-05-12T18:23:00Z" .
-:m004 msg:payloadKind :observation .
-:m004 msg:expectedResult 28 .
-:m004 msg:payload in:formula3 .
-:m005 a msg:RDFMessage .
-:m005 msg:offset 5 .
-:m005 prov:generatedAtTime "2026-05-12T18:24:00Z" .
-:m005 msg:payloadKind :observation .
-:m005 msg:expectedResult 29 .
-:m005 msg:payload in:formula4 .
+: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 .
+
+: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 .
+
+: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 .
+
+: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 .
+
+: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 .
 
-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 21 .
 }
 
-in:formula2 {
+in:payload002 {
   _:m002b0 a sosa:Observation .
   _:m002b0 sosa:madeBySensor :thermometerA .
-  _:m002b0 sosa:resultTime "2026-05-12T18:21:00Z" .
+  _:m002b0 sosa:resultTime "2026-05-12T18:21:00Z"^^xsd:dateTime .
   _:m002b0 sosa:hasSimpleResult 22 .
 }
 
-in:formula3 {
+in:payload004 {
   _:m004b0 a sosa:Observation .
   _:m004b0 sosa:madeBySensor :thermometerA .
-  _:m004b0 sosa:resultTime "2026-05-12T18:23:00Z" .
+  _:m004b0 sosa:resultTime "2026-05-12T18:23:00Z"^^xsd:dateTime .
   _:m004b0 sosa:hasSimpleResult 28 .
 }
 
-in:formula4 {
+in:payload005 {
   _:m005b0 a sosa:Observation .
   _:m005b0 sosa:madeBySensor :thermometerA .
-  _:m005b0 sosa:resultTime "2026-05-12T18:24:00Z" .
+  _:m005b0 sosa:resultTime "2026-05-12T18:24:00Z"^^xsd:dateTime .
   _:m005b0 sosa:hasSimpleResult 29 .
 }
 
@@ -88,13 +122,7 @@ 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/n3/rdf_message_flow.n3" .
-  in:run see:sourceSHA256 "e4e534c8ac3c2aa276e7158cca8d3146531879033f73685c302b486be2ab0099" .
-  in:run see:description "A companion to rdf_messages.n3. This example focuses on a live stream where\nRDF Messages continuously flow through a small processing pipeline. The next\nmessage is released only after the current message reaches the sink, so the\nstream behaves as an ordered, replayable flow rather than a single merged RDF\ngraph." .
+  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" .
-  in:run see:inputFacts 42 .
-  in:run see:compiledRules 9 .
-  in:run see:compiledBackwardRules 0 .
-  in:run see:compiledFuses 0 .
-  in:run see:compiledQueries 1 .
 }

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

@@ -0,0 +1,89 @@
+# ===================================
+# RDF Message Microgrid input sidecar
+# ===================================
+#
+# 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#> .
+
+: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" .
+
+: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 .
+
+: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 .
+
+: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 .
+
+:m004 a rmsg:MessageEnvelope .
+:m004 rmsg:offset 4 .
+:m004 prov:generatedAtTime "2026-05-15T19:03:00Z"^^xsd:dateTime .
+:m004 rmsg:payloadKind :heartbeat .
+
+in:lifeSafetyPayload {
+  :oxygenConcentrator a :LifeSafetyLoad .
+  :oxygenConcentrator :requiresWatts 500 .
+  :oxygenConcentrator :serves :respiratoryCareRoom .
+
+  :vaccineFridge a :ColdChainLoad .
+  :vaccineFridge :requiresWatts 120 .
+  :vaccineFridge :serves :vaccineColdChain .
+}
+
+in:powerPayload {
+  :batteryBank a :PowerReserve .
+  :batteryBank :availableWatts 650 .
+  :batteryBank :state :islanded .
+
+  :solarForecast a :NearTermForecast .
+  :solarForecast :expectedWatts 150 .
+}
+
+in:flexPayload {
+  :evChargers a :FlexibleLoad .
+  :evChargers :shedWatts 600 .
+  :evChargers :serves :staffVehicles .
+}
+
+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" .
+}

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.