菜单
Keep the Lore knowledge graph in sync after changing dawn-field-theory code, experiments, or structure. Use when moving or renaming experiments and documents, after a reorganization, or when updating an FDO or typed node — including the body-replacement and truncation traps.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/dawnfield-institute/dawn-field-theory --skill dft-lore-sync命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create or modify an experiment in dawn-field-theory so it passes the structure validator and records results honestly. Use when adding an experiment, adding scripts or results to one, writing a journal entry, or pre-registering a claim before running it.
Rules for anything under papers/ in dawn-field-theory — published packages, DOIs, and citation metadata. Use before editing, moving, reformatting or repackaging any paper, running a repo-wide sweep that could touch papers/, or answering a question about which DOI to cite.
Run the dawn-field-theory CI gates and regenerate generated artifacts in the correct order. Use before committing or opening a PR in this repo, or when CI reports a generated file is stale, link rot grew, or the structure validator failed.
基于 SOC 职业分类
正在显示 SKILL.md
| name | dft-lore-sync |
| description | Keep the Lore knowledge graph in sync after changing dawn-field-theory code, experiments, or structure. Use when moving or renaming experiments and documents, after a reorganization, or when updating an FDO or typed node — including the body-replacement and truncation traps. |
After any change that moves, renames, adds or removes experiments or documents, update the affected Lore nodes in the same piece of work. Vault drift is the top source of stale documentation, and a stale graph is worse than no graph because Bert answers from it.
Search the graph before starting a topic, too: lore_search(query, grade?). Trust grades:
curated/source are authoritative, reference is useful but flagged for rebuild (the
physics lives here), legacy is GRIM-era history.
kronos is retired. Never write through kronos_* tools.
This trips people up — a path change must be applied to whichever store holds it.
| Store | Path field | Shape |
|---|---|---|
| FDO | source_paths | [{repo, path, type}], path is repo-relative — no dawn-field-theory/ prefix |
| Typed | slots.sources | strings with the dawn-field-theory/ prefix |
Update FDO frontmatter with lore_update(id, fields={...}); update typed slots with
lore_update_slots. Both merge — they do not replace the node.
1. lore_update(body=...) REPLACES the entire body. There is no append mode. To edit a
body you must have the whole current body first.
2. lore_get truncates bodies at 8KB. So the obvious sequence — lore_get, edit the
returned body, lore_update(body=...) — silently commits a truncated record for any node
over 8KB.
Fetch the full body over the HTTP API before writing one back:
GET https://home.griminfra.com/bert/lore/api/fdo/{id}
PUT same endpoint
milestone6-planning-seed has a body of 8191 characters — one byte under the boundary.
Do not assume a node is small enough.
If you only need to change frontmatter, use fields= and never send a body at all.
That is the safe path and avoids both traps entirely.
Issue them one at a time. Parallel calls against the lore MCP face are unreliable here.
Sessions also go stale after a container restart — reinitialize rather than retrying a failing call.
Read the node back and check for a string you just wrote. A successful tool response is not proof the content is what you intended, especially after a body replacement.
For a bulk migration, verify every path resolves on disk afterward rather than trusting the count of nodes updated.
Lore runs on mesh-host CT106, http://192.168.8.230:8103 (MCP at /mcp, mesh-bearer
header required — the workspace .mcp.json carries it), and through the platform edge at
https://home.griminfra.com/bert/lore/api/.
The git mirrors lore-vault/ (FDO) and lore-vault-typed/ (typed) are rendered
mirrors, committed by a 15-minute cron on CT106. Postgres is truth. A local mirror clone
that looks stale is usually just unpulled — check git fetch && git status -sb before
concluding the sync is broken.