AsDecided v0.28.0 — Bounded graph boost and retrieval diagnostics

AsDecided v0.28.0 improves how the CLI ranks and explains decision search results.

What changed

AsDecided uses lexical relevance and relationship data to rank results.

Before this release, a highly connected record could outrank a record with a much stronger lexical match.

A candidate must now have at least 85% of the strongest BM25 score to receive graph boost. A candidate below this floor keeps its lexical score, but receives no graph boost.

Relationship data can still break a close tie. It cannot replace lexical relevance.

Diagnose a missing decision

The new decided diagnose command explains why one named record did or did not appear in the results.

decided diagnose "desktop persistence" DEC-014 decisions/
decided diagnose "desktop persistence" DEC-014 decisions/ --json

The command can identify these conditions:

• No query term matched the record.
• Only part of a multi-term query matched.
• A type, tag, or live-state filter excluded the record.
• Another record received a higher rank.
• The record was outside the selected result limit.
• The target ID was missing or ambiguous.

The command uses the same tokeniser, filters, and ranking path as decided find.

Inspect the graph gate

decided find --explain now reports:

• graph_floor_ratio: the fixed lexical floor of 0.85.
• graph_gate: either applied or clamped.

The default find output does not change. The JSON schema version remains 1.

Boundaries

This release does not add embeddings, semantic ranking, or model-based diagnosis.

Retrieval remains local and deterministic. The same corpus and query produce the same result order.

Install

cargo install decided --version 0.28.0

Or use the versioned container image:

docker pull ghcr.io/asdecided/core:v0.28.0

The release workflow also publishes native archives, SHA256 checksums, provenance attestations, an SBOM, signed container images, crates.io packages, and the MCP Registry record.