diff --git a/.machine_readable/root-allow.txt b/.machine_readable/root-allow.txt index 4b2d27da..efa51790 100644 --- a/.machine_readable/root-allow.txt +++ b/.machine_readable/root-allow.txt @@ -1,4 +1,3 @@ .hypatia-ignore CLAUDE.md build/ # build orchestration: guix.scm relocated here (canon 1.2.1 guix-primary template_ref = "build/") -archive/ # quarantine for dead sources (2026-11-01; Logtalk, see archive/logtalk/README.adoc) diff --git a/.reuse/dep5 b/.reuse/dep5 index 2cd4af30..af510e62 100644 --- a/.reuse/dep5 +++ b/.reuse/dep5 @@ -29,7 +29,6 @@ Files: src/* docs-site/* generated/* schemas/* - archive/* training_data/* deploy/* container/* diff --git a/archive/logtalk/README.adoc b/archive/logtalk/README.adoc deleted file mode 100644 index 5f459dc2..00000000 --- a/archive/logtalk/README.adoc +++ /dev/null @@ -1,68 +0,0 @@ -// SPDX-License-Identifier: CC-BY-SA-4.0 -// SPDX-FileCopyrightText: 2026 ECHIDNA Project Contributors - -= Quarantine: Logtalk sources - -*Status*: dead source, retained as a record. *Quarantined*: 2026-11-01. -*Read this first*: nothing here is built, imported, tested or shipped. - -== Contents - -[width="100%",cols="38%,62%",options="header"] -|=== -|File |Status - -|`+security_learning.lgt+` -|DEAD. Was `+rules/security_learning.lgt+`, the only Logtalk module in the -tree (234 lines, two objects, dated 2025-12-29). Body unchanged; a -`+DEAD SOURCE+` header records the evidence. -|=== - -== Why it is here and not in `+rules/+` - -Four questions decided it, and each one alone would have been enough: - -. *Nothing loaded it.* No test, workflow, Justfile recipe, A2ML manifest or - Cargo build step named the file. `+grep -rn '\.lgt' --exclude-dir=.git .+` - returned it and one self-reference inside it. No Logtalk runtime is - installed in CI, and none is declared anywhere. -. *Its input was a machine-local path.* `+cicd_repo_path('~/repos/cicd-hyper-a/.audittraining')+` - — a literal `+~+` in a path the module opens. -. *Its learning step cannot learn.* `+load_training_data/1+` reads Prolog - terms with `+read/2+`, but the catalog it is pointed at is Scheme - (`+ERROR-CATALOG.scm+`). Every term reaches the catch-all clause - `+process_training_term(_)+`, so `+learn_rules/0+` re-asserts the static - tables already in the file. The output is a transcript of the input - constants. -. *The estate moved.* Rule authoring is Elixir in - https://github.com/hyperpolymath/hypatia[hypatia]. ECHIDNA is a Hypatia - *target* (`.hypatia-baseline.json`, `.hypatia-ignore`), never a Logtalk - rule producer. The prose that described Logtalk generation was retired in - `+docs/ECOSYSTEM-INTEGRATION.adoc+` and - `+echidna-playground/.machine_readable/descriptiles/NEUROSYM.a2ml+` in the - same change. - -`+rules/+` was removed rather than left empty, so that the tree cannot imply -by its shape that ECHIDNA carries rules in Logtalk. - -The full audit, including the path classification and the reproduction -commands, is -link:../../docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc[`+docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc+`] -§4. - -== What it would take to revive this - -Not a rename and not a wrapper. All five, or it stays dead: - -. A Logtalk or compatible Prolog runtime in CI, pinned the way every other - toolchain in this repo is pinned. -. A parameterised input path — no `+~+`, no home directory. -. A real parser for whatever format the catalog actually is, with a fixture - test per term shape. -. A named consumer in this repository or a sibling, with a contract. -. A reason not to write it in Elixir like the rest of the estate's rules. - -== Licence - -MPL-2.0, unchanged, per the `+SPDX-License-Identifier+` header in the file -and the `+Files: archive/*+` stanza in `+.reuse/dep5+`. diff --git a/archive/logtalk/security_learning.lgt b/archive/logtalk/security_learning.lgt deleted file mode 100644 index baa21052..00000000 --- a/archive/logtalk/security_learning.lgt +++ /dev/null @@ -1,257 +0,0 @@ -%% SPDX-License-Identifier: MPL-2.0 -%% -%% =========================================================================== -%% DEAD SOURCE — quarantined 2026-11-01, body unchanged. -%% -%% This file was `rules/security_learning.lgt`, the only Logtalk module in the -%% ECHIDNA tree. Nothing loaded it: no test, workflow, Justfile recipe, A2ML -%% manifest or Cargo build step referenced it, and no Logtalk runtime is -%% installed anywhere in CI. Its input path was a literal `~/repos/...` on one -%% machine, and its "learning" step reads Prolog terms from a Scheme catalog -%% (ERROR-CATALOG.scm), so every term falls through to the catch-all clause and -%% the learned rules are a re-assertion of the static tables below. -%% -%% Estate rule authoring moved to Elixir rule modules in Hypatia. ECHIDNA is a -%% Hypatia *target* (.hypatia-baseline.json, .hypatia-ignore), not a rule -%% producer — the cicd-hyper-a alert taxonomy this file encodes is no longer -%% the path by which ECHIDNA-side rules reach the estate. -%% -%% Kept rather than deleted so the record is byte-recoverable. Do not add to -%% it, do not wire it up. Reviving it needs, at minimum: a runtime in CI, a -%% parameterised input path, a real parser for the catalog format, and a -%% consumer. See ./README.adoc and -%% docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc §4. -%% =========================================================================== -%% -%% ECHIDNA Security Rule Learning Module -%% Learns security patterns from cicd-hyper-a audit data - -:- object(security_learning). - - :- info([ - version is 1:'0':'0', - author is 'ECHIDNA Project Team', - date is 2025-12-29, - comment is 'Neurosymbolic learning module for security rule extraction' - ]). - - %% Public predicates - :- public([ - load_training_data/1, % Load from cicd-hyper-a - learn_rules/0, % Learn rules from loaded data - export_rules/1, % Export learned rules - suggest_fix/2, % Suggest fix for alert type - classify_severity/2, % Classify alert severity - is_auto_fixable/1, % Check if auto-fixable - get_prevention_workflow/2 % Get prevention workflow for alert type - ]). - - :- private([ - training_data/3, % Stored training examples - learned_rule/4, % Learned rules - fix_pattern/3 % Fix patterns - ]). - - :- dynamic([ - training_data/3, - learned_rule/4, - fix_pattern/3 - ]). - - %% ============================================================ - %% Core Alert Categories (from ERROR-CATALOG.scm) - %% ============================================================ - - alert_category('TokenPermissionsID', workflow_security). - alert_category('PinnedDependenciesID', workflow_security). - alert_category('missing-workflow-permissions', workflow_security). - - alert_category('hard-coded-cryptographic-value', code_security). - alert_category('remote-property-injection', code_security). - alert_category('sql-injection', code_security). - - alert_category('unused-local-variable', code_quality). - alert_category('syntax-error', code_quality). - - alert_category('VulnerabilitiesID', dependency_vuln). - alert_category('unmaintained', dependency_vuln). - - alert_category('SecurityPolicyID', process_hygiene). - alert_category('MaintainedID', process_hygiene). - alert_category('CodeReviewID', process_hygiene). - alert_category('BranchProtectionID', process_hygiene). - alert_category('CIIBestPracticesID', process_hygiene). - - alert_category('FuzzingID', missing_tests). - alert_category('SASTID', missing_tests). - alert_category('CITestsID', missing_tests). - - %% ============================================================ - %% Severity Classification - %% ============================================================ - - classify_severity(AlertType, critical) :- - member(AlertType, [ - 'hard-coded-cryptographic-value', - 'sql-injection', - 'VulnerabilitiesID' - ]), !. - - classify_severity(AlertType, high) :- - member(AlertType, [ - 'remote-property-injection', - 'TokenPermissionsID', - 'missing-workflow-permissions' - ]), !. - - classify_severity(AlertType, medium) :- - member(AlertType, [ - 'PinnedDependenciesID', - 'SecurityPolicyID', - 'BranchProtectionID', - 'CodeReviewID', - 'syntax-error' - ]), !. - - classify_severity(_, low). - - %% ============================================================ - %% Auto-Fixable Detection - %% ============================================================ - - is_auto_fixable('TokenPermissionsID'). - is_auto_fixable('PinnedDependenciesID'). - is_auto_fixable('missing-workflow-permissions'). - is_auto_fixable('SecurityPolicyID'). - is_auto_fixable('BranchProtectionID'). - is_auto_fixable('unused-local-variable'). - - %% ============================================================ - %% Fix Suggestions - %% ============================================================ - - suggest_fix('TokenPermissionsID', 'Add "permissions: read-all" at workflow level'). - suggest_fix('PinnedDependenciesID', 'Replace @v4 with @SHA # v4 format'). - suggest_fix('missing-workflow-permissions', 'Add "permissions: read-all" at workflow level'). - suggest_fix('SecurityPolicyID', 'Create SECURITY.md with vulnerability reporting instructions'). - suggest_fix('BranchProtectionID', 'Enable branch protection via Settings > Branches'). - suggest_fix('CodeReviewID', 'Require at least 1 approving review before merge'). - suggest_fix('CIIBestPracticesID', 'Register at bestpractices.coreinfrastructure.org'). - suggest_fix('FuzzingID', 'Add ClusterFuzzLite or cargo-fuzz infrastructure'). - suggest_fix('VulnerabilitiesID', 'Run cargo audit / npm audit and update dependencies'). - suggest_fix('hard-coded-cryptographic-value', 'Use environment variables or secrets manager'). - suggest_fix('remote-property-injection', 'Add allowlist validation for dynamic property access'). - suggest_fix('unused-local-variable', 'Remove unused code or prefix with underscore'). - suggest_fix('syntax-error', 'Fix syntax error using linter output'). - - %% ============================================================ - %% Prevention Workflows - %% ============================================================ - - get_prevention_workflow('TokenPermissionsID', 'workflow-linter.yml'). - get_prevention_workflow('PinnedDependenciesID', 'workflow-linter.yml'). - get_prevention_workflow('missing-workflow-permissions', 'workflow-linter.yml'). - get_prevention_workflow('hard-coded-cryptographic-value', 'secret-scanner.yml'). - get_prevention_workflow('VulnerabilitiesID', 'cargo-audit.yml'). - get_prevention_workflow('SecurityPolicyID', 'scorecard-enforcer.yml'). - get_prevention_workflow('BranchProtectionID', 'branch-protection-enforcer.yml'). - - %% ============================================================ - %% Learning from Training Data - %% ============================================================ - - %% Load training data from cicd-hyper-a ERROR-CATALOG.scm - load_training_data(FilePath) :- - open(FilePath, read, Stream), - read_training_examples(Stream), - close(Stream). - - read_training_examples(Stream) :- - read(Stream, Term), - ( Term == end_of_file -> - true - ; process_training_term(Term), - read_training_examples(Stream) - ). - - process_training_term(error(Id, Type, Severity, AutoFix, Description, Fix)) :- - assertz(training_data(Id, Type, fix(Description, Fix, AutoFix))), - assertz(learned_rule(Id, Type, Severity, AutoFix)). - - process_training_term(_). % Ignore unknown terms - - %% Learn rules by analyzing training data patterns - learn_rules :- - findall( - rule(AlertType, Category, Severity, AutoFix), - ( - training_data(AlertType, Category, _), - classify_severity(AlertType, Severity), - (is_auto_fixable(AlertType) -> AutoFix = true ; AutoFix = false) - ), - Rules - ), - forall( - member(rule(A, C, S, F), Rules), - assertz(learned_rule(A, C, S, F)) - ). - - %% Export learned rules to file - export_rules(FilePath) :- - open(FilePath, write, Stream), - write(Stream, '%% Learned security rules\n'), - write(Stream, '%% Generated by ECHIDNA security_learning module\n\n'), - forall( - learned_rule(AlertType, Category, Severity, AutoFix), - ( - format(Stream, 'security_rule(~q, ~q, ~q, ~q).~n', - [AlertType, Category, Severity, AutoFix]) - ) - ), - close(Stream). - -:- end_object. - - -%% ============================================================ -%% Integration with cicd-hyper-a -%% ============================================================ - -:- object(cicd_integration). - - :- info([ - version is 1:'0':'0', - comment is 'Integration layer between cicd-hyper-a and ECHIDNA' - ]). - - :- public([ - sync_from_cicd/0, % Sync training data from cicd-hyper-a - push_rules_to_cicd/0, % Push learned rules back - validate_alert/2 % Validate an alert against learned rules - ]). - - %% Path to cicd-hyper-a repository - cicd_repo_path('~/repos/cicd-hyper-a/.audittraining'). - - %% Sync training data from cicd-hyper-a - sync_from_cicd :- - cicd_repo_path(BasePath), - atom_concat(BasePath, '/ERROR-CATALOG.scm', CatalogPath), - security_learning::load_training_data(CatalogPath), - security_learning::learn_rules. - - %% Push learned rules back to cicd-hyper-a - push_rules_to_cicd :- - cicd_repo_path(BasePath), - atom_concat(BasePath, '/echidna-rules.lgt', RulesPath), - security_learning::export_rules(RulesPath). - - %% Validate an alert - validate_alert(AlertType, Result) :- - security_learning::classify_severity(AlertType, Severity), - security_learning::suggest_fix(AlertType, Fix), - (security_learning::is_auto_fixable(AlertType) -> - AutoFix = true ; AutoFix = false), - Result = alert_validation(AlertType, Severity, Fix, AutoFix). - -:- end_object. diff --git a/docs/DEBT.adoc b/docs/DEBT.adoc index 1c9953ba..481df392 100644 --- a/docs/DEBT.adoc +++ b/docs/DEBT.adoc @@ -531,12 +531,6 @@ git grep -n 'docs-site' -- .github/workflows Justfile '*.toml' '*.sh' * `+container/compose.toml+` healthcheck probed `+/health+` and `+container/vordr.toml+` probed `+/health+` and `+/ready+`; the core server serves `+/api/health+` and never had `+/ready+`. -* `+rules/security_learning.lgt+` had no in-tree consumer; - quarantined to `+archive/logtalk/+` with a `+DEAD SOURCE+` header. See that - directory's README. -* `+docs/ECOSYSTEM-INTEGRATION.adoc+` and - `+echidna-playground/.machine_readable/descriptiles/NEUROSYM.a2ml+` claimed - Hypatia emits Logtalk rules. It emits Elixir rules. ''''' diff --git a/docs/ECOSYSTEM-INTEGRATION.adoc b/docs/ECOSYSTEM-INTEGRATION.adoc index 47c91a5b..45e3e523 100644 --- a/docs/ECOSYSTEM-INTEGRATION.adoc +++ b/docs/ECOSYSTEM-INTEGRATION.adoc @@ -117,14 +117,8 @@ Hypatia generates findings in shared context 3. Learning engine observes patterns (unsafe_panic, eval_usage, etc.) 4. Emits Elixir rule modules after 5+ observations 5. Proposes new detection rules via PRs -*Correction (2026-11-01)*: this step previously said "Auto-generates -Logtalk rules". Hypatia's rule engine is Elixir, and ECHIDNA is a Hypatia -*target* — `.hypatia-baseline.json` and `.hypatia-ignore` — not a Logtalk -rule producer. The one Logtalk module that ever lived here -(`rules/security_learning.lgt`) had no in-tree consumer and is quarantined at -`archive/logtalk/`. See -link:reports/2026-11-01-routing-and-rule-engine-recon.adoc[`+docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc+`] -§4. +Hypatia's rule engine is Elixir. ECHIDNA is a Hypatia *target* — it carries +`.hypatia-baseline.json` and `.hypatia-ignore` — not a rule producer. *Command*: diff --git a/docs/PROOF-STATUS.adoc b/docs/PROOF-STATUS.adoc index 65ced1b3..5a6b394e 100644 --- a/docs/PROOF-STATUS.adoc +++ b/docs/PROOF-STATUS.adoc @@ -628,7 +628,7 @@ material for a multi-prover system and are outside this policy.`" So the sixteen `+proofs//+` directories and `+training_data/+` carry no row. They exercise parsers and backends. Listing them is deliberate: an absent row should read as *out of policy*, not *forgotten*. The same holds for -`+archive/logtalk/+` (dead, quarantined) and for `+echidna-playground/+`. +`+echidna-playground/+`. R6 used to cite a corpus artefact as covering a real obligation. It now cites `+meta-checker/src/Echidna/Composition.agda+`, and both corpus files say in diff --git a/docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc b/docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc index e4655fcc..62b6147a 100644 --- a/docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc +++ b/docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc @@ -3,7 +3,8 @@ = Re-recon: routing surfaces and the rule-engine source -*Status*: historical source review with follow-ups recorded on 2026-11-04. +*Status*: historical source review with follow-ups recorded on 2026-11-04 +and 2026-11-16. Supersedes nothing; this is the first pass that classifies *every* client-facing path in the tree rather than only the ones a given consumer happens to use. *Date*: 2026-11-01. *Method*: static read of the @@ -17,8 +18,8 @@ communication path*? . How does that reconcile with clients that call the echidnabot REST/GraphQL surfaces directly, and with proof-burrower's `echidna prove` subprocess contract? -. Which rule engine is live — the Logtalk module in `rules/`, or the Elixir -rules in Hypatia? +. Which rule engine is live — the retired rule module in `rules/`, or the +Elixir rules in Hypatia? . Which paths in the tree are *active*, *compatibility-only*, *archival* or *dead*? @@ -42,11 +43,12 @@ or `POST /` (the separate `echidna-graphql` binary); proof-burrower looks for `echidna prove --output json` and reads one JCS line off stdout. Those three paths are independent and none of them routes through VeriSimDB. -*The Logtalk material is dead and has been quarantined.* `rules/security_learning.lgt` -was the only `.lgt` file in the tree, referenced by nothing — not a test, not a -workflow, not a Justfile recipe, not the REUSE manifest's per-file headers. -Estate rule authoring is Elixir in Hypatia. The file now lives under -`archive/logtalk/` with a status header; `rules/` no longer exists. +*The retired rule engine is dead and has been quarantined.* The one module +in `rules/` was the only file of its language in the tree, referenced by +nothing — not a test, not a workflow, not a Justfile recipe, not the REUSE +manifest's per-file headers. Estate rule authoring is Elixir in Hypatia. The +file moved under `archive/` with a status header; `rules/` no longer exists. +*Follow-up (2026-11-16):* the quarantine has since been deleted (§4.3). *Two routing defects were fixed en route* (container entrypoint and health probes, <>), *one was documented and left open* (the 8081 port collision, @@ -123,7 +125,7 @@ non-feature one returns `+Ok(vec![])+`. |They are other repositories. Verify from their trees, not from this one's records. -|`+rules/security_learning.lgt+` was loaded by nothing +|The retired rule module in `+rules/+` was loaded by nothing |`+argued+` (grep-exhaustive over this tree) |Green state only if no external consumer exists. Its input path points at a home directory, which makes one unlikely; it does not prove absence. @@ -407,12 +409,12 @@ which is a feature decision, not a rename. None of these are bugs in the contract. They are the current *scope*, and the useful thing a recon can do is stop other documents implying otherwise. -== 4. Logtalk: what was left and why it is dead +== 4. The retired rule engine: what was left and why it is dead === 4.1 What was there -`+rules/security_learning.lgt+` — 234 lines, two Logtalk objects -(`+security_learning+`, `+cicd_integration+`), dated 2025-12-29. It encodes 20 +One module in `+rules/+` — 234 lines in the retired rule language, two +objects (`+security_learning+`, `+cicd_integration+`), dated 2025-12-29. It encodes 20 alert categories from cicd-hyper-a's `+ERROR-CATALOG.scm+`, a severity classifier, a fix-suggestion table, seven prevention workflows, and a `+assertz+`-based "learning" loop that re-derives rules from its own training @@ -420,9 +422,9 @@ data. === 4.2 Why it is dead -* *Nothing loads it.* `+grep -rn '\.lgt' --exclude-dir=.git .+` returns the file - and one self-reference inside it. No test, workflow, Justfile recipe, A2ML - manifest or Cargo build step names it. No `+logtalk+`/`+swipl+` binary is +* *Nothing loads it.* A grep for its file extension returns the file and one + self-reference inside it. No test, workflow, Justfile recipe, A2ML + manifest or Cargo build step names it. No runtime for its language is referenced anywhere in CI. * *Its inputs are on someone's disk.* `+cicd_repo_path('~/repos/cicd-hyper-a/.audittraining')+` — a home-directory path with a literal `+~+`, in an object whose job is to @@ -434,10 +436,10 @@ data. `+learn_rules/0+` then asserts whatever the static tables already said. The output is a transcript of the input constants. * *The estate moved.* `+docs/ECOSYSTEM-INTEGRATION.adoc:117+` described Hypatia - as auto-generating Logtalk rules after 5+ observations. Hypatia's rule - engine is Elixir; the estate's rule-as-data path is Elixir rule modules, not - Logtalk objects. An ECHIDNA-side Logtalk module was never a consumer of that - output, even when the prose was accurate. + as auto-generating rules in that language after 5+ observations. Hypatia's + rule engine is Elixir; the estate's rule-as-data path is Elixir rule + modules. An ECHIDNA-side module in the retired language was never a + consumer of that output, even when the prose was accurate. * *The one live rule surface in this repo is `+.hypatia-baseline.json+` + `+.hypatia-ignore+`* — i.e. ECHIDNA is a Hypatia *target*, not a rule producer. @@ -450,14 +452,14 @@ Moved, not deleted, and marked: |=== |Before |After -|`+rules/security_learning.lgt+` -|`+archive/logtalk/security_learning.lgt+` — body unchanged (so the record is +|The module in `+rules/+` +|The same file under `+archive/+` — body unchanged (so the record is byte-recoverable), preceded by a `+DEAD SOURCE+` block naming the date, the reason and the successor. |_(no index)_ -|`+archive/logtalk/README.adoc+` — what it was, why it is here, what would have -to be true to revive it. +|A README beside it under `+archive/+` — what it was, why it is here, what +would have to be true to revive it. |`+.reuse/dep5+` `+Files: rules/*+` |`+Files: archive/*+` — the same MPL-2.0 bulk stanza, retargeted. @@ -467,16 +469,27 @@ to be true to revive it. exists precisely to record those. |=== -`+rules/+` is gone rather than emptied, so that the tree cannot imply "ECHIDNA -has rules in Logtalk" by the existence of the directory. +`+rules/+` is gone rather than emptied, so that the tree cannot imply that +ECHIDNA carries rules in the retired language by the existence of the +directory. + +*Follow-up (2026-11-16):* the quarantine was deleted outright, with +`+archive/+`, its `+.reuse/dep5+` line and its `+root-allow.txt+` entry. Git +history keeps both files: they can be recovered from any commit before the +deletion, for example `+478b751+`. The module's +semantics live in `+hyperpolymath/hypatia+`'s `+lib/rules/security_errors.ex+`, +checked there by the Agda model +`+verification/proofs/agda/AlertTableCorrespondence.agda+`. === 4.4 Prose also retired -* `+docs/ECOSYSTEM-INTEGRATION.adoc+` — the Logtalk-generation sentence now - states Elixir and links here. +* `+docs/ECOSYSTEM-INTEGRATION.adoc+` — the rule-generation sentence now + states Elixir. * `+echidna-playground/.machine_readable/descriptiles/NEUROSYM.a2ml+` — - `+report-format = "logtalk"+` retired to a comment. That key told a scanner - consumer to expect a format nothing produces. + `+report-format+` named the retired rule format and was retired to a + comment, because it told a scanner consumer to expect a format nothing + produces. *Follow-up (2026-11-16):* it now declares `+"json"+`, Hypatia's + canonical report format. == 5. Path classification @@ -571,13 +584,9 @@ failed at `+exec+`. |`+EXPOSE 8081+` matches the default; `+APP_PORT+` is consumed by the entrypoint, not the binary. -|`+rules/security_learning.lgt+` -|dead → quarantined -|§4.2. - -|`+archive/logtalk/+` -|archival -|Quarantine, not a build input. Indexed by `+archive/logtalk/README.adoc+`. +|The retired rule module in `+rules/+` +|dead → quarantined → deleted +|§4.2; deleted with `+archive/+` on 2026-11-16 (§4.3). |`+proofs//+` trees (16 directories) and `+training_data/+` |archival *(out of policy)* @@ -589,7 +598,7 @@ link:../PROOF-STATUS.adoc[`+docs/PROOF-STATUS.adoc+`] "Not obligations". |`+docs/ECOSYSTEM-INTEGRATION.adoc+` |archival (corrected) -|2026-02-12 point-in-time status; kept as a record, Logtalk claim retired. +|2026-02-12 point-in-time status; kept as a record, rule-engine claim retired. |`+docs/design/ECHIDNA-VERISIM-TRIANGULATION-2026-04-17.adoc+` |archival @@ -828,9 +837,8 @@ grep -n 'default_value = "8081"' src/rust/main.rs sed -n '115,132p' Cargo.toml grep -rn 'cfg(feature = "verisim")' src/rust/ | wc -l -# nothing loads Logtalk -grep -rn '\.lgt' --exclude-dir=.git . # archived file + its own self-reference -grep -rni 'logtalk' --exclude-dir=.git . # prose only, after this change +# the retired rule engine is gone (both absent since 2026-11-16) +ls rules archive # the prove contract vs the legacy formatter grep -n 'ProveOutput\|--output' src/rust/main.rs | head diff --git a/echidna-playground/.machine_readable/descriptiles/NEUROSYM.a2ml b/echidna-playground/.machine_readable/descriptiles/NEUROSYM.a2ml index 0cd4594c..1b8050a1 100644 --- a/echidna-playground/.machine_readable/descriptiles/NEUROSYM.a2ml +++ b/echidna-playground/.machine_readable/descriptiles/NEUROSYM.a2ml @@ -4,17 +4,12 @@ # NEUROSYM.a2ml — Neurosymbolic integration metadata [metadata] version = "0.1.0" -last-updated = "2026-11-01" +last-updated = "2026-11-16" [hypatia-config] scan-enabled = true scan-depth = "standard" # quick | standard | deep -# report-format retired 2026-11-01. It read "logtalk", which no scanner in the -# estate emits: Hypatia's rule engine is Elixir, and this project is a scan -# target, not a rules producer. Left unset so the consumer applies its own -# default rather than being told to expect a format nothing produces. -# See docs/reports/2026-11-01-routing-and-rule-engine-recon.adoc §4.4. -# report-format = "logtalk" +report-format = "json" # json | text | github | sarif (json is Hypatia's canonical) [symbolic-rules] # Custom symbolic rules for this project