CLI observability: inspection commands, honest explanations, concurrent sync #19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/19/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
CLI observability and correctness improvements across the
elephantcommand surface, plus concurrent p2p sync and hardening from adversarial review.CLI observability & UX
elephant show <sentence-id>inspects a single entry.elephant infosurfaces the active store (ELEPHANT_HOME), identity, and known homes.daemon statusreports per-peer / per-theory sync health.why-notgives a first-class ambiguity-blocking explanation.explainmakes a blocked literal self-describing instead of a barenull.describeemits plain JSON meta values rather thanDebug String("…")wrappers.logretract entries are now addressable (stableentry_id+ explicit retract target).Correctness
what-ifrejects(prefer …)/rule hypotheticals instead of silently ignoring them.requirereturns only verified fact sets, not raw abduction candidates.Sync / concurrency
requireexhaustiveness, from adversarial review.Review
Includes fixes addressing adversarial-review findings on the observability work.