Nox-Lumen Mfgrecord_knowledge
In one sentence
Reusable conclusions from a session—a new bug pattern, a preference, a validated root cause—go back via record_knowledge so the platform gets smarter next time.
Destinations
| Type | Purpose | Examples |
|---|---|---|
fact | Facts / patterns | “Customer A’s ticket prefix [xxx] is the project code” |
preference | User preference | “User B dislikes mixed Chinese/English” |
error_pattern | False positive / miss feedback | “That code-review finding was a false alarm” |
program | Reusable snippets | “This SQL computes monthly throughput for customer X” |
Writes include tags (module:CarSyncShare, pattern:heartbeat_disconnect, …) filterable via unified_search later.
Why it’s a tool—not automatic
By design: the AI chooses what’s worth remembering.
Auto-logging floods memory with one-offs; explicit record_knowledge ties to SKILL steps—e.g., code-review calls it at Step 6.
Related
- Memory
- unified_search — retrieve memories
- Code review LTM pools