eyeling 1.22.9 → 1.22.11

package/HANDBOOK.md

@@ -3419,6 +3419,22 @@ That is the Appendix F layer. ARC gives the file a readable surface. Constructor
 
 The better ACT examples are heavily commented. The comments should say not just what the syntax is doing, but what scientific role the block plays:
 
+#### H.5.6 Editorial conventions for ACT files
+
+For this repository, the ACT examples should stay visibly **Eyeling-native**.
+They should read as compact N3 task-logic models rather than as a second language layer.
+
+A good default order is:
+
+1. scenario facts;
+2. positive `:can` rules;
+3. negative `:cannot` rules;
+4. checks;
+5. the final ARC report.
+
+The ARC report should make the decisive contrast explicit: what task is possible, what task is impossible, and which missing ingredient or witness explains the contrast.
+
+
 - interoperability
 - locality
 - no-cloning

package/eyeling.js

@@ -842,7 +842,8 @@ function __existentializeBlankTerm(t, mapping, varGen, localBlankLabels) {
 }
 
 function __existentializeBlankTriples(rawGraphOrTriples, varGen) {
-  const triples = rawGraphOrTriples instanceof GraphTerm ? Array.from(rawGraphOrTriples.triples) : Array.from(rawGraphOrTriples);
+  const triples =
+    rawGraphOrTriples instanceof GraphTerm ? Array.from(rawGraphOrTriples.triples) : Array.from(rawGraphOrTriples);
   const localBlankLabels =
     rawGraphOrTriples instanceof GraphTerm &&
     Object.prototype.hasOwnProperty.call(rawGraphOrTriples, '__quotedLocalBlankLabels') &&

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eyeling",
-  "version": "1.22.9",
+  "version": "1.22.11",
   "description": "A minimal Notation3 (N3) reasoner in JavaScript.",
   "main": "./index.js",
   "keywords": [