memory-widget

Memory Widget

Render the user's vault memory as a widget — but you do not design the styling. You pick a fixed component, bind real vault data to its contract, and emit it. Style is owned by the component reference + Kimi design tokens; you only do the data wiring. This keeps every memory widget on-brand and stops you re-inventing layout each time.

This works like lark-base and kimi-design-skill: a short menu here, detail in references/.

执行前必做 (read before you emit)

1. Read references/data-contract.md once — the exact shape of the vault data the host injects.
2. Read the component reference for each component you'll use (e.g. references/calendar.md). Follow its Contract (what data it eats) and Fixed Style (do not invent your own variant).
3. For styling tokens/components, the references inherit kimi-design-skill; read it when a reference tells you to. Do not invent colors, radii, spacing.

Do not emit a memory widget without having read the matching component reference.

数据来源 (how data reaches the widget)

The host injects the user's live vault into the widget — you never fetch or bake data:

window.DaimonWidget.onVaultData(function (vault) {
  // vault.nodes:   [{ id, name, type, tags[], created, lastUpdated, content, linkCount }]
  // vault.edges:   [{ source, target }]            // entity↔entity, from body [[wikilinks]]
  // vault.about_user: { name, aliases[], facts[], topTags[] }
  render(vault);
});

Full field types + nuances live in references/data-contract.md. CSP blocks fetch/CDN — data only arrives via this callback; the component runtime (KW.*) is pre-injected by the host.

组件菜单 (component menu — read the reference before using)

想要	组件	reference	状态
按时间看 entity 何时进入记忆	Calendar / Timeline	references/calendar.md	✅ ready
全字段表格(可排序/筛选)	Table	references/table.md	⏳ TODO
按 tag 分组的卡片墙	Gallery	references/gallery.md	⏳ TODO
entity 关系网络	Graph	references/graph.md	⏳ TODO
「关于你」画像头卡	Profile	references/profile.md	⏳ TODO
多组件拼成 dashboard	Layout	references/layout.md	⏳ TODO