@rasensio/aidlc-content 1.81.0 → 1.82.0

package/docs/knowledge-graph.md

@@ -33,6 +33,17 @@ aidlc knowledge context --scope phase --phase design
 `discover` scans a codebase and seeds the graph — that is how a brownfield project starts. After that,
 record findings as you make them rather than at the end.
 
+**Re-running `discover` only fills gaps.** It replaces a description only when it is empty or still
+one that discovery itself wrote, and never changes an entity's name, source, author, confidence or
+tags. A module it finds is written into the existing entry with the same name or source path, not
+added under a second id; when two entries match, it writes nothing for that module and prints a
+warning naming them. A fact that did not change is not rewritten, so a re-run on an unchanged repo
+leaves an empty diff. The reason is this repo's own graph: a second run replaced a seven-line
+hand-written description with "Module at packages/cli/src/core/ (has index)", added 14 thin copies of
+modules already written up under other ids, and touched about 100 files. Discovery and
+`knowledge add` now take separate paths for this reason — a person adding a description means to
+replace the old one, and discovery never does.
+
 To add several entities at once, pipe YAML documents (separated by `---`) to
 `aidlc knowledge add --stdin`. A `tags:` string there means what `--tags` means: comma-separated.
 **Every document is checked before any is written**, and a run that fails writes nothing. That rule

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.81.0",
+  "version": "1.82.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",