eyeling 1.34.4 → 1.34.5

package/docs/eyelang-guide.md

@@ -460,7 +460,7 @@ node test/eyelang/run-regression.mjs
 node test/eyelang/run-examples.mjs
 ```
 
-The conformance suite lives in [`test/eyelang/conformance/`](../test/eyelang/conformance/) and is split into `core` and `extension` profiles matching the language reference. Each case is a small program with an exact expected stdout file, and some internal conformance cases also include a goal file for testing the embeddable solver, so other implementations can reuse the same cases. The regression suite lives in [`test/eyelang/run-regression.mjs`](../test/eyelang/run-regression.mjs) and covers CLI regressions, the public JavaScript API, and white-box invariants for parser, unification, and indexing behavior.
+The conformance suite lives in [`test/eyelang/conformance/`](../test/eyelang/conformance/) as one flat eyelang corpus. Each case is a small `.pl` program with an exact expected stdout `.pl` file, and some cases also include a goal file for testing the embeddable solver, so other implementations can reuse the same cases. The suite covers the standard language surface from the language reference, including reusable built-ins. The regression suite lives in [`test/eyelang/run-regression.mjs`](../test/eyelang/run-regression.mjs) and covers CLI regressions, the public JavaScript API, and white-box invariants for parser, unification, and indexing behavior.
 
 ## Development and release
 

package/docs/eyelang-language-reference.md

@@ -41,7 +41,7 @@
   - [9.8 Aggregation and ordering](#98-aggregation-and-ordering)
   - [9.9 Context terms](#99-context-terms)
   - [9.10 Search control](#910-search-control)
-- [10. Extension built-ins](#10-extension-built-ins)
+- [10. Implementation-specific built-ins](#10-implementation-specific-built-ins)
 - [11. Declarations](#11-declarations)
   - [11.1 Memoization](#111-memoization)
   - [11.2 Default-output materialization](#112-default-output-materialization)
@@ -51,10 +51,7 @@
   - [12.3 Sockets and AI agents](#123-sockets-and-ai-agents)
 - [13. Output and read-back profile](#13-output-and-read-back-profile)
   - [13.1 Explanation output](#131-explanation-output)
-- [14. Conformance profiles](#14-conformance-profiles)
-  - [14.1 Core language profile](#141-core-language-profile)
-  - [14.2 Standard built-in profile](#142-standard-built-in-profile)
-  - [14.3 Standard host profile](#143-standard-host-profile)
+- [14. Conformance](#14-conformance)
 - [15. Relationship to ISO Prolog](#15-relationship-to-iso-prolog)
 - [16. Examples](#16-examples)
   - [16.1 Transitive closure](#161-transitive-closure)
@@ -345,7 +342,7 @@ This section specifies the **standard built-ins** of the eyelang language. An im
 
 A built-in call is still written as an atomic formula, but the relation is provided by the host implementation rather than by source clauses. Several built-ins are mode-sensitive: they are intended to run when their input arguments are sufficiently ground, and implementations may leave user-defined clauses visible when that mode is not yet satisfied.
 
-Implementations MAY provide additional built-ins, but such built-ins are extensions and are not part of this normative catalog. Extension built-ins are discussed separately in section 10.
+Implementations MAY provide additional built-ins, but such built-ins are implementation-specific and are not part of this normative catalog. Implementation-specific built-ins are discussed separately in section 10.
 
 ### 9.1 Equality and unification
 
@@ -485,13 +482,13 @@ The N3 example [`context-schema-audit.n3`](../examples/context-schema-audit.n3)
 | `once(Goal)` | Succeeds with at most the first solution of `Goal`. |
 | `forall(Generator, Test)` | Succeeds when every solution of `Generator` also satisfies `Test`; succeeds vacuously when `Generator` has no solutions. |
 
-## 10. Extension built-ins
+## 10. Implementation-specific built-ins
 
-Implementations MAY provide additional built-ins beyond the standard predicates listed above. Such built-ins are **extension built-ins**. They are useful for embedding eyelang in particular host environments, exposing efficient finite-domain solvers, or providing domain-specific relations for examples and applications.
+Implementations MAY provide additional built-ins beyond the standard predicates listed above. Such built-ins are **implementation-specific built-ins**. They are useful for embedding eyelang in particular host environments, exposing efficient finite-domain solvers, or providing domain-specific relations for applications.
 
-Extension built-ins are not required for conformance to this specification. A portable eyelang program SHOULD NOT depend on an extension built-in unless the target implementation explicitly documents that extension.
+Implementation-specific built-ins are not required for conformance to this specification. A portable eyelang program SHOULD NOT depend on one unless the target implementation explicitly documents it.
 
-An extension built-in SHOULD obey the same surface-language discipline as standard built-ins:
+An implementation-specific built-in SHOULD obey the same surface-language discipline as standard built-ins:
 
 - it is called using ordinary atomic-formula syntax, for example `some_extension(A, B)`;
 - its arguments and results are eyelang terms from the Herbrand universe;
@@ -499,9 +496,9 @@ An extension built-in SHOULD obey the same surface-language discipline as standa
 - it SHOULD document its intended modes, especially which arguments must be ground before it runs deterministically;
 - it MUST NOT change the meaning of ordinary facts, rules, unification, or standard built-ins.
 
-For example, an implementation may include extension modules for number-theory algorithms, matrix operations, or host-specific integrations. Those modules may be valuable and may make example programs much faster, but their predicate names, arities, algorithms, and modes are implementation-defined unless they are separately standardized.
+For example, an implementation may include host-specific integrations or domain accelerators. Those modules may be valuable and may make applications much faster, but their predicate names, arities, algorithms, and modes are implementation-defined unless they are separately standardized.
 
-An implementation that provides explanation output SHOULD make extension built-ins explainable at least as opaque successful or failed built-in calls, so that proof traces do not incorrectly report "no clauses" for a host-provided relation.
+An implementation that provides explanation output SHOULD make implementation-specific built-ins explainable at least as opaque successful or failed built-in calls, so that proof traces do not incorrectly report "no clauses" for a host-provided relation.
 
 ## 11. Declarations
 
@@ -623,37 +620,25 @@ Default host output behavior is:
 
 When proof output is enabled, each answer SHOULD be followed by a machine-readable `why/2` fact. Explanation output is ordinary eyelang syntax whose second argument is a nested abstract proof term such as `proof(goal(G), by(Method), bindings(Bindings), uses(Proofs))`; implementations SHOULD print `goal(...)` and `by(...)` on separate lines for readability. A proof term preserves the answer goal, derivation method, relevant bindings, and nested uses while omitting proof IDs. User clauses SHOULD be referenced explicitly as `fact(Filename, clause(N))` or `rule(Filename, clause(N))`, where `N` is the 1-based clause number within that source. Built-ins SHOULD be referenced as `builtin(Name, Arity)` because they do not come from source clauses. Explanation output is outside the logical semantics of the input program and MUST NOT change the set of answers.
 
-## 14. Conformance profiles
+## 14. Conformance
 
-### 14.1 Core language profile
-
-A conforming core language implementation supports:
+A conforming eyelang implementation supports the standard language described above as one conformance surface rather than as separate core and extension profiles. This includes:
 
 - lexical syntax described above;
 - facts and definite clauses;
 - first-order unification without occurs check;
 - left-to-right goal-directed proof search;
 - lists and comma conjunctions;
-- answer printing.
-
-### 14.2 Standard built-in profile
-
-A conforming standard built-in implementation supports the built-ins listed in section 9. These are the portable built-ins independent implementations should implement when they claim standard built-in compatibility.
-
-### 14.3 Standard host profile
-
-A conforming standard host also supports:
-
+- answer printing and read-back formatting;
+- the standard built-ins listed in section 9;
 - `memoize/2` declarations;
 - `materialize/2` declarations;
 - default derived output;
-- explanation output;
-- stdin, file, and URL inputs in the CLI.
-
-Browser execution, package layout, and any extension built-ins described in implementation documentation are outside this specification unless separately standardized.
+- explanation output when the host exposes proof output.
 
+Browser execution, package layout, CLI URL loading, and any implementation-specific built-ins described in host documentation are outside this conformance surface unless separately standardized.
 
-Conformance cases for these profiles live in the repository under `conformance/`. They are run by `npm test` before the example suite, and can be run alone with `npm run test:conformance`. The cases use exact expected standard output files so independent implementations can compare behavior case by case.
+Conformance cases live in the repository under `test/eyelang/conformance/`. They are run by `npm test` before the example suite, and can be run alone with `node test/eyelang/run-conformance.mjs`. Each case has an input program under `conformance/cases/` and an exact expected standard-output file under `conformance/expected/`; both use `.pl` so expected output remains eyelang-readable.
 
 ## 15. Relationship to ISO Prolog
 

package/package.json

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

package/test/eyelang/conformance/README.md

@@ -4,8 +4,8 @@ This directory contains the executable conformance cases for the eyelang languag
 
 The suite is intentionally file-based so another implementation can run the same programs and compare exact standard output. A case consists of:
 
-- `conformance/cases/<profile>/<name>.pl` — input program;
-- `conformance/expected/<profile>/<name>.out` — exact expected standard output.
+- `conformance/cases/<name>.pl` — input program;
+- `conformance/expected/<name>.pl` — exact expected standard output, stored as eyelang-readable facts.
 
 The current runner compares standard output from normal execution. Proof explanations are opt-in in the CLI and are not part of these conformance goldens. Standard error, performance, and resource limits are outside this suite.
 
@@ -23,23 +23,21 @@ Run only the conformance suite:
 node test/eyelang/run-conformance.mjs
 ```
 
-Run a single conformance profile directly:
+Run matching conformance cases by passing a filename fragment:
 
 ```sh
-node test/eyelang/run-conformance.mjs core
-node test/eyelang/run-conformance.mjs extension
+node test/eyelang/run-conformance.mjs reusable
+node test/eyelang/run-conformance.mjs 092_scalar_string_conversions
 ```
 
 The runner executes materialized programs in-process through the public JavaScript API so small conformance cases avoid measuring Node startup overhead.
 
-## Profiles
+## Scope
 
-`core` covers the portable core language profile from the [eyelang language reference](../../../docs/eyelang-language-reference.md): lexical syntax, facts, definite clauses, first-order terms, lists, conjunction, structured unification through user predicates, left-to-right goal-directed proof search, materialized output, and read-back printing.
+The conformance corpus is a single eyelang suite. It covers the standard language described by the language reference: lexical syntax, facts, definite clauses, first-order terms, lists, conjunction, structured unification, left-to-right goal-directed proof search, materialized output, read-back printing, standard built-ins, declarations, and standard host behavior.
 
-`extension` covers the standard built-in and host behavior exercised by the current reference implementation: arithmetic, comparison, strings, list relations, aggregation, context-term helpers, term-inspection helpers, search-control helpers, `memoize/2`, `materialize/2`, and default derived output.
-
-The profile name `extension` is a test-suite grouping name. It does not mean that these cases are outside the eyelang language reference; most of them correspond to the standard built-in profile and standard host profile in the [eyelang language reference](../../../docs/eyelang-language-reference.md).
+The suite deliberately does not separate `core` and `extension` profiles. Reusable built-ins such as arithmetic, strings, lists, aggregation, context terms, term inspection, and search control are part of the standard eyelang conformance surface. Implementation-specific built-ins may still exist in downstream hosts, but they should have their own tests outside this corpus unless they are standardized.
 
 ## Updating expected output
 
-There is no committed auto-accept mode. To update an expected file, run the matching case with the conformance runner, inspect the result, and replace the corresponding file under `conformance/expected/<profile>/` deliberately.
+There is no committed auto-accept mode. To update an expected file, run the matching case with the conformance runner, inspect the result, and replace the corresponding file under `conformance/expected/` deliberately.

package/test/eyelang/conformance/cases/001_fact_output.pl

@@ -0,0 +1,4 @@
+% Reference 6, 7, 11: facts can be exposed through a materialized derived predicate.
+materialize(parent, 2).
+base_parent(pat, jan).
+parent(X, Y) :- base_parent(X, Y).

package/test/eyelang/conformance/cases/002_rule_recursion.pl

@@ -0,0 +1,7 @@
+% Reference 6, 7: definite clauses, conjunction, and recursive proof search.
+materialize(ancestor, 2).
+parent(pat, jan).
+parent(jan, emma).
+ancestor_any(X, Y) :- parent(X, Y).
+ancestor_any(X, Z) :- parent(X, Y), ancestor_any(Y, Z).
+ancestor(pat, Y) :- ancestor_any(pat, Y).

package/test/eyelang/conformance/cases/002_rule_recursion.query

@@ -0,0 +1 @@
+ancestor(pat, X)

package/test/eyelang/conformance/cases/003_terms_and_readback.pl

@@ -0,0 +1,16 @@
+% Reference 3, 5, 11: scalars, compounds, lists, and read-back printing.
+materialize(value, 2).
+raw_value(atom, pat).
+raw_value(quoted_atom, 'atom with spaces').
+raw_value(quoted_quote, 'needs''quote').
+raw_value(empty_atom, '').
+raw_value(string, "line\nquote: \"ok\"").
+raw_value(integer, -42).
+raw_value(decimal, 0.25).
+raw_value(scientific, 1.25e-3).
+raw_value(compound, pair(3, nested(atom, [x, y]))).
+raw_value(zero_arity, nil()).
+raw_value(empty_list, []).
+raw_value(proper_list, [a, b, c]).
+raw_value(improper_list, [a, b | tail]).
+value(K, V) :- raw_value(K, V).

package/test/eyelang/conformance/cases/003_terms_and_readback.query

@@ -0,0 +1 @@
+value(K, V)

package/test/eyelang/conformance/cases/004_conjunction_and_parentheses.pl

@@ -0,0 +1,5 @@
+% Reference 5.5, 7: parenthesized comma terms are conjunctions in goal position.
+p(a).
+q(a).
+ok(X, yes) :- (p(X), q(X)).
+materialize(ok, 2).

package/test/eyelang/conformance/cases/004_conjunction_and_parentheses.query

@@ -0,0 +1 @@
+ok(X, Y)

package/test/eyelang/conformance/cases/005_list_deconstruction.pl

@@ -0,0 +1,6 @@
+% Reference 5.4, 12.1: list syntax and unification in rule heads.
+first([X | _Rest], X).
+tail([_Head | Tail], Tail).
+answer(first, X) :- first([a, b, c], X).
+answer(tail, Tail) :- tail([a, b, c], Tail).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/005_list_deconstruction.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/006_comma_formula_data.pl

@@ -0,0 +1,4 @@
+% Reference 5.5: comma terms remain data outside goal position.
+record((name(alice, "Alice"), knows(alice, bob))).
+answer(formula, F) :- record(F).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/006_comma_formula_data.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/007_anonymous_variables.pl

@@ -0,0 +1,5 @@
+% Reference 3.4, 5.1, 7.1: each anonymous variable occurrence is fresh.
+pair(a, one).
+pair(b, two).
+answer(fresh, yes) :- pair(a, _), pair(b, _).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/007_anonymous_variables.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/008_graphic_atoms.pl

@@ -0,0 +1,6 @@
+% Reference 3.5, 5.2, 11: graphic atom constants are scalar terms.
+materialize(value, 2).
+raw_value(hash, #).
+raw_value(arrow, =>).
+raw_value(comparison, =<).
+value(K, V) :- raw_value(K, V).

package/test/eyelang/conformance/cases/008_graphic_atoms.query

@@ -0,0 +1 @@
+value(K, V)

package/test/eyelang/conformance/cases/009_comments_and_whitespace.pl

@@ -0,0 +1,5 @@
+% Reference 3.2, 3.6: comments are ignored outside quoted text and atoms.
+  item(quoted_percent, "% not a comment").    % trailing comment
+item(quoted_atom, 'has % sign').
+answer(K, V) :- item(K, V).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/009_comments_and_whitespace.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/010_variable_scope_and_reuse.pl

@@ -0,0 +1,8 @@
+% Reference 5.1, 7.1: variable occurrences are scoped per clause and reused within a clause.
+edge(a, b).
+edge(b, c).
+edge(c, d).
+two_step(X, Z) :- edge(X, Y), edge(Y, Z).
+answer(from_a, Z) :- two_step(a, Z).
+answer(from_b, Z) :- two_step(b, Z).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/010_variable_scope_and_reuse.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/011_predicate_arity.pl

@@ -0,0 +1,6 @@
+% Reference 6: predicate name and arity both identify a predicate group.
+p(a).
+p(a, b).
+answer(unary, X) :- p(X).
+answer(binary, pair(X, Y)) :- p(X, Y).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/011_predicate_arity.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/012_nested_compound_unification.pl

@@ -0,0 +1,5 @@
+% Reference 5.3, 7.1: unification follows nested compound term structure.
+fact(pair(a, nested(b, [c, d]))).
+answer(middle, X) :- fact(pair(a, nested(X, [c, d]))).
+answer(list_tail, T) :- fact(pair(a, nested(b, [c | T]))).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/012_nested_compound_unification.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/013_multiple_clauses_order.pl

@@ -0,0 +1,6 @@
+% Reference 6, 7: multiple clauses for one predicate are explored as alternatives.
+color(red).
+color(blue).
+paint(X) :- color(X).
+answer(color, X) :- paint(X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/013_multiple_clauses_order.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/014_failure_filters_answers.pl

@@ -0,0 +1,7 @@
+% Reference 7.2: a failing subgoal removes that candidate answer.
+candidate(a).
+candidate(b).
+allowed(a).
+answer(X, ok) :- candidate(X), allowed(X).
+
+materialize(answer, 2).

package/test/eyelang/conformance/cases/014_failure_filters_answers.query

@@ -0,0 +1 @@
+answer(X, V)

package/test/eyelang/conformance/cases/015_improper_list_unification.pl

@@ -0,0 +1,6 @@
+% Reference 5.4: improper list surface syntax unifies with head-tail structure.
+cell([head | tail], head, tail).
+answer(list, L) :- cell(L, head, tail).
+answer(head, H) :- cell([H | tail], H, tail).
+answer(tail, T) :- cell([head | T], head, T).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/015_improper_list_unification.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/016_zero_arity_compound.pl

@@ -0,0 +1,4 @@
+% Reference 4, 5.3: zero-arity compounds are written and matched with parentheses.
+status(nil(), ok).
+answer(value, X) :- status(X, ok).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/016_zero_arity_compound.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/017_three_step_recursion.pl

@@ -0,0 +1,8 @@
+% Reference 7: recursive definite clauses can derive paths beyond one step.
+link(a, b).
+link(b, c).
+link(c, d).
+path(X, Y) :- link(X, Y).
+path(X, Z) :- link(X, Y), path(Y, Z).
+answer(reachable, X) :- path(a, X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/017_three_step_recursion.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/018_quoted_atom_readback.pl

@@ -0,0 +1,6 @@
+% Reference 3.5, 11: quoted atoms preserve spaces, quotes, and the empty atom.
+symbol('two words').
+symbol('needs''quote').
+symbol('').
+answer(symbol, X) :- symbol(X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/018_quoted_atom_readback.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/019_parenthesized_three_conjuncts.pl

@@ -0,0 +1,7 @@
+% Reference 5.5, 7: parenthesized comma terms with more than two members are conjunctions as goals.
+p(a).
+q(a).
+r(a).
+ok(X) :- (p(X), q(X), r(X)).
+answer(ok, X) :- ok(X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/019_parenthesized_three_conjuncts.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/020_nested_list_terms.pl

@@ -0,0 +1,5 @@
+% Reference 5.3, 5.4: lists may contain structured terms that unify positionally.
+node([pair(a, b), pair(c, d)]).
+answer(first_key, X) :- node([pair(X, _), pair(c, d)]).
+answer(second_key, X) :- node([pair(a, b), pair(X, d)]).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/020_nested_list_terms.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/021_repeated_variable_head.pl

@@ -0,0 +1,7 @@
+% Reference 5.1, 7.1: repeated variables in a rule body require the same term.
+pair(a, a).
+pair(a, b).
+pair(c, c).
+diagonal(X) :- pair(X, X).
+answer(diagonal, X) :- diagonal(X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/022_rule_head_structure.pl

@@ -0,0 +1,5 @@
+% Reference 5.3, 6, 7.1: structured rule heads destructure matching goals.
+unpack(pair(X, Y), X, Y).
+answer(first, A) :- unpack(pair(alpha, beta), A, _).
+answer(second, B) :- unpack(pair(alpha, beta), _, B).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/023_quoted_escapes_readback.pl

@@ -0,0 +1,5 @@
+% Reference 3.5, 11: quoted strings and atoms preserve escape sequences at read-back.
+raw(string, "line\nnext\t\\slash").
+raw(atom, 'line\nnext\t\\slash').
+answer(K, V) :- raw(K, V).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/024_numeric_literal_readback.pl

@@ -0,0 +1,6 @@
+% Reference 3.3, 11: signed, decimal, and exponent numeric literals retain lexical form.
+raw(negative_decimal, -3.5).
+raw(positive_exp, 6.02e23).
+raw(negative_exp, -1.0e-3).
+answer(K, V) :- raw(K, V).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/025_body_parentheses_with_formula_data.pl

@@ -0,0 +1,5 @@
+% Reference 5.5, 7: formula data can be passed through parenthesized conjunctions.
+record((left(a), right(b))).
+accept((left(a), right(b))).
+answer(ok, F) :- (record(F), accept(F)).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/026_underscore_named_variable_reuse.pl

@@ -0,0 +1,5 @@
+% Reference 3.4, 5.1: variables beginning with underscore are named variables unless exactly _.
+pair(a, a).
+pair(a, b).
+answer(shared, _Value) :- pair(_Value, _Value).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/027_default_derived_output.pl

@@ -0,0 +1,5 @@
+% Reference 11: default output prints new ground binary derivations, not source facts.
+parent(pat, jan).
+parent(jan, emma).
+ancestor(X, Y) :- parent(X, Y).
+ancestor(X, Z) :- parent(X, Y), ancestor(Y, Z).

package/test/eyelang/conformance/cases/028_materialize_focus.pl

@@ -0,0 +1,5 @@
+% Reference 10.2, 11: materialize/2 restricts selected default predicate groups.
+materialize(answer, 2).
+seed(a).
+helper(X, y) :- seed(X).
+answer(X, ok) :- helper(X, y).

package/test/eyelang/conformance/cases/029_arithmetic_and_comparison.pl

@@ -0,0 +1,11 @@
+% Reference 9.2, 9.3: arithmetic and comparison built-ins.
+answer(sum, X) :- add(2, 3, X).
+answer(diff, X) :- sub(7, 4, X).
+answer(product, X) :- mul(6, 7, X).
+answer(integer_division, X) :- div(7, 2, X).
+answer(remainder, X) :- mod(7, 2, X).
+answer(power, X) :- pow(2, 8, X).
+answer(minimum, X) :- min(3, 9, X).
+answer(less_than, true) :- lt(3, 9).
+answer(greater_equal, true) :- ge(9, 9).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/029_arithmetic_and_comparison.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/030_strings_and_atoms.pl

@@ -0,0 +1,4 @@
+% Reference 9.6: atom and string built-ins.
+answer(str_concat, X) :- str_concat("eye", "lang", X).
+answer(contains, true) :- contains("eyelang", "lang").
+materialize(answer, 2).

package/test/eyelang/conformance/cases/030_strings_and_atoms.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/031_lists_aggregation_ordering.pl

@@ -0,0 +1,10 @@
+% Reference 9.7, 9.8: list, aggregation, and ordering built-ins.
+answer(member, X) :- member(X, [a, b]).
+answer(append, X) :- append([a], [b, c], X).
+answer(nth0, X) :- nth0(1, [a, b, c], X).
+answer(set_nth0, X) :- set_nth0(1, [a, b, c], x, X).
+answer(reverse, X) :- reverse([a, b, c], X).
+answer(length, N) :- length([a, b, c], N).
+answer(findall, X) :- findall(N, between(1, 3, N), X).
+answer(sort, X) :- sort([b, a, b], X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/031_lists_aggregation_ordering.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/032_holds_parts.pl

@@ -0,0 +1,4 @@
+% Reference 9.9: holds/3 exposes context members of any arity.
+context((ready, name(alice, "Alice"), route(alice, bob, 7))).
+answer(parts, exposed(Name, Args)) :- context(C), holds(C, Name, Args).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/033_negation_once_generators.pl

@@ -0,0 +1,7 @@
+% Reference 9.5, 9.10: generators, negation as failure, and once/1.
+candidate(a).
+candidate(b).
+closed(b).
+answer(open, X) :- candidate(X), not(closed(X)).
+answer(first_between, X) :- once(between(2, 4, X)).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/033_negation_once_generators.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/034_equality_and_inequality.pl

@@ -0,0 +1,6 @@
+% Reference 9.1: eq/2 unifies terms and neq/2 succeeds on non-unifiable terms.
+answer(eq_variable, X) :- eq(X, pair(a, [b, c])).
+answer(eq_nested, true) :- eq(pair(X, X), pair(same, same)).
+answer(neq_atoms, true) :- neq(alice, bob).
+answer(neq_structures, true) :- neq(pair(a), pair(a, b)).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/034_equality_and_inequality.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/035_list_relations.pl

@@ -0,0 +1,5 @@
+% Reference 9.7: rest/2, select/3, and not_member/2.
+answer(rest, X) :- rest([a, b, c], X).
+answer(select, selected(X, R)) :- select(X, [a, b], R).
+answer(not_member, true) :- not_member(c, [a, b]).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/035_list_relations.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/036_append_splits.pl

@@ -0,0 +1,3 @@
+% Reference 9.7: append/3 can enumerate proper prefix/suffix splits.
+answer(split, split(A, B)) :- append(A, B, [a, b]).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/036_append_splits.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/037_matching_and_comparison.pl

@@ -0,0 +1,7 @@
+% Reference 9.3, 9.6: lexical comparison and simple text matching.
+answer(matches, true) :- matches("eyelang", "eye").
+answer(not_matches, true) :- not_matches("eyelang", "cat").
+answer(lex_lt, true) :- lt(alpha, beta).
+answer(lex_gt, true) :- gt(beta, alpha).
+answer(numeric_le, true) :- le(2, 2).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/037_matching_and_comparison.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/038_memoize_declaration.pl

@@ -0,0 +1,8 @@
+% Reference 10.1: memoize/2 is a declaration and does not change answers.
+materialize(reach, 2).
+memoize(reach_any, 2).
+edge(a, b).
+edge(b, c).
+reach_any(X, Y) :- edge(X, Y).
+reach_any(X, Z) :- edge(X, Y), reach_any(Y, Z).
+reach(a, Y) :- reach_any(a, Y).

package/test/eyelang/conformance/cases/038_memoize_declaration.query

@@ -0,0 +1 @@
+reach(a, X)

package/test/eyelang/conformance/cases/039_numeric_functions.pl

@@ -0,0 +1,9 @@
+% Reference 9.2: scalar arithmetic functions return numeric values.
+answer(neg, X) :- neg(5, X).
+answer(abs, X) :- abs(-5, X).
+answer(rounded, X) :- rounded(2.6, X).
+answer(sin_zero, X) :- sin(0, X).
+answer(cos_zero, X) :- cos(0, X).
+answer(log_one, X) :- log(1, X).
+answer(float_division, X) :- div(7.0, 2.0, X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/039_numeric_functions.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/040_between_enumeration.pl

@@ -0,0 +1,3 @@
+% Reference 9.5: between/3 enumerates every integer in an inclusive range.
+answer(n, X) :- between(3, 5, X).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/040_between_enumeration.query

@@ -0,0 +1 @@
+answer(K, V)

package/test/eyelang/conformance/cases/041_smallest_divisor.pl

@@ -0,0 +1,3 @@
+% Reference 9.5: smallest_divisor_from/3 finds the first divisor at or above the start.
+answer(divisor, D) :- smallest_divisor_from(21, 2, D).
+materialize(answer, 2).

package/test/eyelang/conformance/cases/041_smallest_divisor.query

@@ -0,0 +1 @@
+answer(K, V)