eyeling 1.24.2 → 1.24.4

package/see/README.md

@@ -18,7 +18,7 @@ Each example starts from a Notation3 source and is compiled by `see.js` into a s
 
 The trust gate is executable verification. If a required fact is missing, the program fails instead of emitting an unsupported entailment.
 
-The `triple_terms` example uses RDF 1.2 `<<( ... )>>` triple-term syntax. Eyeling accepts that syntax by normalizing it to the existing N3 singleton graph term `{ ... }`; SEE keeps the committed `.trig` input and formal output in RDF 1.2 triple-term form.
+The `triple_terms` and `rdf_dataset` examples use RDF 1.2 `<<( ... )>>` triple-term syntax. Eyeling accepts that syntax only with `-r, --rdf`, where it normalizes triple terms to existing N3 singleton graph terms `{ ... }` and prints feasible output graph terms back as RDF 1.2 triple terms. The `rdf_dataset` example also uses an RDF/TriG named graph block, which RDF compatibility mode normalizes to the N3 `log:nameOf { ... }` graph-term shape and prints back as a TriG named graph block where feasible; SEE keeps the committed `.trig` input and formal output in RDF 1.2/TriG form.
 
 
 ## Run
@@ -138,6 +138,7 @@ The repository currently contains **50 N3-compiled SEE examples**. Each example
 | <a id="example-odrl-dpv-risk-ranking"></a>[ODRL + DPV risk ranking](#example-odrl-dpv-risk-ranking) | compiled from Notation3 by `see.js`; policy and data-protection evidence are ranked by risk level and selected through rule-derived comparisons. | [doc](examples/doc/odrl_dpv_risk_ranked.md), [js](examples/odrl_dpv_risk_ranked.js), [input](examples/input/odrl_dpv_risk_ranked.trig), [output](examples/output/odrl_dpv_risk_ranked.md), [n3](examples/n3/odrl_dpv_risk_ranked.n3) |
 | <a id="example-path-discovery"></a>[Path discovery](#example-path-discovery) | compiled from the upstream path-discovery rules; the runner loads the full 96k-fact airroutes graph from TriG and evaluates the bounded route query with an indexed adjacency list. | [doc](examples/doc/path_discovery.md), [js](examples/path_discovery.js), [input](examples/input/path-discovery.trig), [output](examples/output/path_discovery.md), [n3](examples/n3/path_discovery.n3) |
 | <a id="example-rc-discharge-envelope"></a>[RC discharge envelope](#example-rc-discharge-envelope) | compiled from Notation3 by `see.js`; exponentiation over an upper decay bound certifies the first sampled capacitor step below tolerance. | [doc](examples/doc/rc_discharge_envelope.md), [js](examples/rc_discharge_envelope.js), [input](examples/input/rc_discharge_envelope.trig), [output](examples/output/rc_discharge_envelope.md), [n3](examples/n3/rc_discharge_envelope.n3) |
+| <a id="example-rdf-dataset-compatibility"></a>[RDF dataset compatibility](#example-rdf-dataset-compatibility) | compiled from Notation3 by `see.js`; RDF/TriG named graph input and RDF 1.2 triple terms demonstrate the same N3 graph-term normalization used by Eyeling's explicit RDF compatibility mode. | [doc](examples/doc/rdf_dataset.md), [js](examples/rdf_dataset.js), [input](examples/input/rdf_dataset.trig), [output](examples/output/rdf_dataset.md), [n3](examples/n3/rdf_dataset.n3) |
 | <a id="example-rdf-message-flow"></a>[RDF Message Flow](#example-rdf-message-flow) | compiled from Notation3 by `see.js`; live RDF Messages advance through ingest, validate, interpret, route, and sink stages, with each completed message releasing the next one. | [doc](examples/doc/rdf_message_flow.md), [js](examples/rdf_message_flow.js), [input](examples/input/rdf_message_flow.trig), [output](examples/output/rdf_message_flow.md), [n3](examples/n3/rdf_message_flow.n3) |
 | <a id="example-rdf-messages"></a>[RDF Messages](#example-rdf-messages) | compiled from Notation3 by `see.js`; ordered RDF Message Log example preserving explicit message boundaries, an empty heartbeat, message-local payloads, and reused blank-node labels. | [doc](examples/doc/rdf_messages.md), [js](examples/rdf_messages.js), [input](examples/input/rdf_messages.trig), [output](examples/output/rdf_messages.md), [n3](examples/n3/rdf_messages.n3) |
 | <a id="example-school-placement-route-audit"></a>[School placement route audit](#example-school-placement-route-audit) | compiled from Notation3 by `see.js`; student, school, distance, and policy facts derive an auditable school-placement route decision. | [doc](examples/doc/school_placement_audit.md), [js](examples/school_placement_audit.js), [input](examples/input/school_placement_audit.trig), [output](examples/output/school_placement_audit.md), [n3](examples/n3/school_placement_audit.n3) |

package/see/examples/doc/rdf_dataset.md

@@ -0,0 +1,26 @@
+# RDF dataset compatibility
+
+Generated by `see.js` from a Notation3 source file.
+
+RDF 1.1 named graph data and RDF 1.2 triple terms are normalized to ordinary N3 graph terms before SEE compiles the derivation.
+
+## Compilation summary
+
+- Example name: `rdf_dataset`
+- Input facts emitted: 4
+- Forward rules compiled: 1
+- Backward predicate rules compiled: 0
+- Fuses compiled: 0
+- Predicate count: 5
+
+## Built-ins used
+
+- `log:nameOf`
+
+## Runtime model
+
+The generated `examples/rdf_dataset.js` is a specialized JavaScript derivation program. For ordinary sources, `see.js` emits the source facts as `examples/input/rdf_dataset.trig`. For rules-only sources, generation can reuse an existing external evidence file such as `examples/input/rdf-dataset.trig` or `examples/input/rdf_dataset.trig`. The runner reads that TriG evidence directly and performs a local fixpoint derivation; it does not parse the program source or call an external reasoner.
+
+## Output model
+
+Running `node examples/rdf_dataset.js` produces a SEE-style Markdown report with an **Entailment** section, an **Explanation** section, and a **Formal TriG Output** section containing the selected derived/query facts.

package/see/examples/input/path_discovery.trig

@@ -9,7 +9,7 @@
 @prefix in: <https://example.org/see/input#> .
 
 # Formal SEE input evidence in RDF 1.2 TriG.
-# The generated runner uses the N3 form produced from this file by tools/n3gen.js.
+# The generated runner reads this TriG evidence directly in RDF compatibility mode.
 
 # No source facts were present in the N3 program.
 

package/see/examples/input/rdf_dataset.trig

@@ -0,0 +1,34 @@
+VERSION "1.2"
+
+@prefix : <https://eyereasoner.github.io/see/examples/rdf-dataset#> .
+@prefix log: <http://www.w3.org/2000/10/swap/log#> .
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix see: <https://example.org/see#> .
+@prefix in: <https://example.org/see/input#> .
+
+# Formal SEE input evidence in RDF 1.2 TriG.
+# The generated runner reads this TriG evidence directly.
+
+:sensor :reports :overheating .
+:overheating :requires :inspection .
+:maintenanceSystem :trusted true .
+
+:factoryDataset {
+  :observation rdf:reifies <<( :sensor :reports :overheating )>> .
+  :observation :recordedBy :maintenanceSystem .
+}
+
+in:metadata {
+  in:run a see:InputDataset .
+  in:run see:name "rdf_dataset" .
+  in:run see:title "RDF dataset compatibility" .
+  in:run see:sourceFile "examples/n3/rdf_dataset.n3" .
+  in:run see:sourceSHA256 "76035a24eb72fc1d28a5e1f3021baefee0dde667aa8fc9f2b0a111f9c773b744" .
+  in:run see:description "RDF 1.1 named graph data and RDF 1.2 triple terms are normalized to ordinary N3 graph terms before SEE compiles the derivation." .
+  in:run see:compiler "see.js N3-to-JS compiler" .
+  in:run see:inputFacts 4 .
+  in:run see:compiledRules 1 .
+  in:run see:compiledBackwardRules 0 .
+  in:run see:compiledFuses 0 .
+  in:run see:compiledQueries 1 .
+}

package/see/examples/n3/rdf_dataset.n3

@@ -0,0 +1,34 @@
+# RDF dataset compatibility
+# RDF 1.1 named graph data and RDF 1.2 triple terms are normalized to ordinary N3 graph terms before SEE compiles the derivation.
+
+VERSION "1.2"
+@prefix : <https://eyereasoner.github.io/see/examples/rdf-dataset#> .
+@prefix log: <http://www.w3.org/2000/10/swap/log#> .
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+
+:sensor :reports :overheating .
+:overheating :requires :inspection .
+:maintenanceSystem :trusted true .
+
+:factoryDataset {
+  :observation rdf:reifies <<( :sensor :reports :overheating )>> .
+  :observation :recordedBy :maintenanceSystem .
+}
+
+{
+  :sensor :reports ?condition .
+  ?condition :requires ?action .
+  :maintenanceSystem :trusted true .
+} => {
+  :workOrder :entails <<( :sensor :needs ?action )>> .
+  :audit log:nameOf {
+    :workOrder :basedOn :factoryDataset .
+    :workOrder :checkedBy :maintenanceSystem .
+  } .
+} .
+
+{
+  :workOrder :entails <<( ?device :needs ?action )>> .
+} log:query {
+  :workOrder :entails <<( ?device :needs ?action )>> .
+} .

package/see/examples/output/rdf_dataset.md

@@ -0,0 +1,54 @@
+# RDF dataset compatibility  
+
+## Entailment  
+The compiled query selected 1 fact(s) after the rule closure was computed.  
+Main entailment: **:workOrder :entails <<( :sensor :needs :inspection )>>.**  
+
+Selected entailments:  
+- :workOrder :entails <<( :sensor :needs :inspection )>> .  
+
+## Explanation  
+Starts with 4 source fact(s), applies 1 rule(s), and reaches a fixpoint.  
+The log:query projection then keeps only the matching fact(s) shown above.  
+
+Derivation steps:  
+- Rule 1 (3 premise pattern(s) => 2 conclusion pattern(s)) derives :workOrder :entails <<( :sensor :needs :inspection )>> ., :audit log:nameOf { :workOrder :basedOn :factoryDataset . :workOrder :checkedBy :maintenanceSystem } .  
+  - Uses: :sensor :reports :overheating . _(source)_; :overheating :requires :inspection . _(source)_; :maintenanceSystem :trusted true . _(source)_  
+
+Selected explanation support:  
+  - :workOrder :entails <<( :sensor :needs :inspection )>> . _(derived by Rule 1)_  
+    - :sensor :reports :overheating . _(source)_  
+    - :overheating :requires :inspection . _(source)_  
+    - :maintenanceSystem :trusted true . _(source)_  
+
+The query-selected facts are serialized in the Formal TriG Output section.  
+
+## Formal TriG Output  
+
+```trig  
+VERSION "1.2"  
+
+@prefix : <https://eyereasoner.github.io/see/examples/rdf-dataset#> .  
+@prefix log: <http://www.w3.org/2000/10/swap/log#> .  
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .  
+@prefix see: <https://example.org/see#> .  
+@prefix in: <https://example.org/see/input#> .  
+
+:workOrder :entails <<( :sensor :needs :inspection )>> .  
+
+in:metadata {  
+  in:run a see:InputDataset .  
+  in:run see:name "rdf_dataset" .  
+  in:run see:title "RDF dataset compatibility" .  
+  in:run see:sourceFile "examples/n3/rdf_dataset.n3" .  
+  in:run see:sourceSHA256 "76035a24eb72fc1d28a5e1f3021baefee0dde667aa8fc9f2b0a111f9c773b744" .  
+  in:run see:description "RDF 1.1 named graph data and RDF 1.2 triple terms are normalized to ordinary N3 graph terms before SEE compiles the derivation." .  
+  in:run see:compiler "see.js N3-to-JS compiler" .  
+  in:run see:inputFacts 4 .  
+  in:run see:compiledRules 1 .  
+  in:run see:compiledBackwardRules 0 .  
+  in:run see:compiledFuses 0 .  
+  in:run see:compiledQueries 1 .  
+}  
+```  
+