Skip to content

v0.1.3

Choose a tag to compare

@github-actions github-actions released this 22 Jul 06:16

Changes since v0.1.2.

Highlights

Curation and the proposal gate - knowledge management with a human in the loop

The workspace can now surface how its knowledge could be tidied, and every change to the
projected graph goes through a reviewable proposal - it generates, it does not commit.

  • Read-only curation signals: a new curation projection points out where the ontology
    wants attention - merge candidates (entities that collide on name), grab-bags
    (over-large hyperedges), and orphans (unconnected entities). Signals are a pure
    projection over the observation log; they suggest, they never mutate (Principle 7:
    consolidation generates, it does not commit).
  • Proposal workflow: new propose / review / list_proposals / get_proposal tools.
    A proposal is itself an observation on the log, and its state (open / merged / rejected /
    withdrawn) is a deterministic fold over proposal events - so the audit trail is the source
    of truth and nothing is applied out of band. Five proposal kinds are recorded:
    entity_merge, claim_promotion, claim_demotion, tbox_change, recall.
  • Entity merge by projection-time id forwarding: an accepted entity_merge does not
    delete or rewrite anything - the graph projection forwards the merged-away id onto the
    canonical one, rewires edges (dropping self-loops and deduping), aggregates sources, and
    absorbs the merged names as aliases. Append-only, fully reversible in principle (Principles
    3/14/15).

Gated consolidation - the design standard, written down first

  • docs/principles.md: Principle 7 enforcement extended - consolidation generates, does
    not commit
    . Any refine/tidy/recall pass produces proposals for review, never a silent
    rewrite.
  • docs/proposal-workflow.md: invariant I18 (consolidation is a source of proposals, not
    a sixth commit path) and a new section on the consolidation-and-curation-console flow.

Viewer - curation console and a full layout overhaul

  • Curation console: the signals, the proposal list, and a review action live in the
    viewer; clicking a proposal previews the merge on the graph (dashed arrow from the
    merged-away node to the canonical one, accented incident edges, target and canonical rings)
    before you accept it.
  • Type glossary panel: the workspace T-Box (define_type) is browsable in the viewer.
  • Two full-height side rails: left = observe (layers + node/edge legends, stacked),
    right = manage (proposals / review / types tabs), with an IDE-style bottom status bar
    for stats / session / connection.
  • Node detail moved to a wide center-bottom panel (two-column outgoing / incoming); the
    zoom controls moved to the top-right so the bottom stays clear. Centering accounts for the
    open panel height so a focused node stays visible.
  • Central-axis anchor: a rigid per-frame centroid recenter keeps the whole cluster fixed
    to the center - it no longer drifts off to one side as the simulation cools or restarts.
  • Layout loading indicator: the graph is hidden behind a spinner while the simulation is
    violently settling and revealed already fitted once it calms; clicking or focusing a node
    no longer reheats the layout.

Install

curl -fsSL https://raw.githubusercontent.com/Ashon/supragnosis/main/scripts/install.sh | sh

Or download the platform tar.gz from the assets below, extract it, and put supragnosis
on your PATH. Supported: macOS (arm64 / x86_64), Linux (x86_64); each asset ships a .sha256.

  • CLI: supragnosis --help. Register with an MCP client: claude mcp add supragnosis -- ~/.local/bin/supragnosis.

Notes / limitations

  • Merge effect is projection-time only: entity_merge forwards ids in the graph
    projection. Other read surfaces (get_entity / traverse / search_knowledge / the
    hypergraph) do not yet apply forwarding consistently - that is the next step.
  • Only entity_merge has a graph effect today; the other proposal kinds
    (claim_promotion / claim_demotion / tbox_change / recall) are recorded and
    reviewable but not yet enforced. Blocking checks (referential integrity, etc.) are future
    work.
  • review accepts a verdict directly (single-user workspace, solo self-attested exception).
    There is no un-merge / contradiction signal yet.
  • The prebuilt binary is keyword + hashing search. For local ONNX semantic search,
    build from source with cargo build --release --features fastembed.
  • HTTP daemon / viewer are loopback-only (no auth) - a local trust surface. Remote
    exposure, auth, and TLS are future work.
  • 0.x early release - the storage format and surfaces may still change.