explain: add all-derivations signed provenance and conflict decisions #25

New issue

Open

opened 2026-07-16 06:43:17 +00:00 by anuna-02 · 0 comments

anuna-02 commented

2026-07-16 06:43:17 +00:00

(Migrated from codeberg.org)

Summary

Extend explain with an all-derivations, signed-provenance view that also exposes the
operative attacks and preferences for each derivation.

Motivation from the grounded two-machine run

Human explain lab-origin selected one route and ended at an opaque internal fact
identifier:

Using defeasible rule: r-nohost-lab
Using fact: f8

For a shared signed theory, an auditor needed to know which journal assertion supplied
that fact, its SPL, SID, signer DID, and whether it remained active. The run also had
multiple possible support routes and competing defeaters; the single selected tree did
not reveal alternatives or why one conflict resolution mattered.

Issues #9, #12, and #13 improved entry inspection and blocked-literal diagnostics.
This proposal connects successful derivations to that signed journal data and exposes
all relevant alternatives.

Proposed CLI

For example:

elephant explain lab-origin -t rootclaim-grounded --all --provenance --json

For each fact/rule/preference node, include where applicable:

literal and proof tag;
full SPL and rule label;
SID/entry ID, signer DID, timestamp, and active/retracted status;
supporting premises;
applicable attackers/defeaters;
the superiority edge or ambiguity decision that determined the outcome.

This is signed-theory provenance only; Elephant need not understand an external wiki
or evidence URL.

Acceptance criteria

--all returns every distinct minimal successful derivation, deterministically
ordered, with a documented bound/truncation indicator.
--provenance resolves opaque fact IDs to journal entries and signers.
Retracted or quarantined entries cannot appear as active support, but can be shown in
an explicitly requested historical view.
Conflict nodes say which rules opposed one another and which preference, if any,
resolved them.
Text output remains readable; JSON uses stable IDs so clients can join to show or
log without parsing CBCL.
Tests include multiple proofs, two signers, a defeater, a preference, and a retracted
former proof.

Environment / evidence

Observed with Elephant 0.1.2. Example text and richer query artifacts are retained at:
github.com/anuna-cooperative/flf-elephant-experiment@96ca63675e/runs/2026-07-16/grounded-machineB

### Summary Extend `explain` with an all-derivations, signed-provenance view that also exposes the operative attacks and preferences for each derivation. ### Motivation from the grounded two-machine run Human `explain lab-origin` selected one route and ended at an opaque internal fact identifier: ```text Using defeasible rule: r-nohost-lab Using fact: f8 ``` For a shared signed theory, an auditor needed to know which journal assertion supplied that fact, its SPL, SID, signer DID, and whether it remained active. The run also had multiple possible support routes and competing defeaters; the single selected tree did not reveal alternatives or why one conflict resolution mattered. Issues #9, #12, and #13 improved entry inspection and blocked-literal diagnostics. This proposal connects successful derivations to that signed journal data and exposes all relevant alternatives. ### Proposed CLI For example: ```console elephant explain lab-origin -t rootclaim-grounded --all --provenance --json ``` For each fact/rule/preference node, include where applicable: - literal and proof tag; - full SPL and rule label; - SID/entry ID, signer DID, timestamp, and active/retracted status; - supporting premises; - applicable attackers/defeaters; - the superiority edge or ambiguity decision that determined the outcome. This is signed-theory provenance only; Elephant need not understand an external wiki or evidence URL. ### Acceptance criteria - `--all` returns every distinct minimal successful derivation, deterministically ordered, with a documented bound/truncation indicator. - `--provenance` resolves opaque fact IDs to journal entries and signers. - Retracted or quarantined entries cannot appear as active support, but can be shown in an explicitly requested historical view. - Conflict nodes say which rules opposed one another and which preference, if any, resolved them. - Text output remains readable; JSON uses stable IDs so clients can join to `show` or `log` without parsing CBCL. - Tests include multiple proofs, two signers, a defeater, a preference, and a retracted former proof. ### Environment / evidence Observed with Elephant 0.1.2. Example text and richer query artifacts are retained at: https://github.com/anuna-cooperative/flf-elephant-experiment/tree/96ca63675edd88cf4982449c5f78b9441c320a39/runs/2026-07-16/grounded-machineB

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

anuna-research/elephant#25

No description provided.

Rows
Columns