Skip to content

v1.6.0 — a topic has to name what a memory is about

Choose a tag to compare

View all tags
@dthorntonz dthorntonz released this 01 Sep 22:29
· 1 commit to main since this release
v1.6.0
85b1c8b

Tagging could only ever add, so a bulk pass was a decision you could not take back — and a pass you cannot undo is a pass you make timidly. This release supplies the missing verb, and then, with undo in hand, makes the suggester worth trusting: it was proposing words like "now" and "users", which would connect every memory to every other one.

Added

  • untag <id> <topic> takes a topic off a memory — the counterpart tag never had. Removing a topic removes an edge, never a memory. When the last memory carrying a topic lets it go, the topic name goes with it, because a vocabulary word no memory uses connects nothing and would keep being offered as a suggestion.

Changed

  • The dream's topic suggester now proposes subjects rather than words. It was offering "now", "never", "day", "users" and "app" — all of which pass the retrieval stopword filter, appear all over a project, and would connect every memory to every other. Three things changed: a topic-side stoplist (kept separate from the retrieval one, which protects ranking and must not widen), a floor of three memories before an existing topic is worth spreading, and a shape rule that rejects identifier fragments like e01, v2 and 72b.
  • The untagged-memory worklist now says how many rows actually carry a suggestion, not just how many are untagged. The old count claimed more reviewable work than existed.

Fixed

  • The reality check no longer reports a file that is sitting right there when its name holds more than one space. The candidate walk stopped after the first space, so ~/Desktop/Field Notes Draft.md read as the missing directory ~/Desktop/Field. It now walks up to three words, and still reports a spaced path that is genuinely gone.

Documentation

  • The dream worklist's reproject guidance no longer reads as "apply what you just saw". The worklist prints the best fifteen; --apply writes every proposal above the margin, which on a lived-in store is an order of magnitude more and is not trustworthy at the low end.

Full changelog: https://github.com/itdtllc/fornixdb/blob/main/CHANGELOG.md

Assets 2
Loading