Files
2026-04-27 15:09:27 +08:00

60 lines
2.3 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
id: "" # 必须与本文件名(不含 .md)完全一致,例:文件 佩佩-维修1.md → id: "佩佩-维修1"
type: beat
beat_type: "" # 维修 | 场景对话 | 梦境 | 特殊
day: "" # 留空则进入 outline 的 Backlog
order_in_day: 0
confidence: planned # confirmed | planned | speculative
dev_status: fiction # fiction | playable | function | prototype | close
fiction_source: self # 叙事信源位置。self = 本文 Fiction 区即 SSOT;指向外部时填路径(如 Yarn 文件夹路径或 flow 文档链接)
emotional_tone: "" # 情绪基调,例:"压抑/解脱" "荒诞/温暖"
summary: "" # ≤60字;[谁/场景]+[核心矛盾或转折]+[对主线/角色影响],见 template/README.md「summary 写作规范」
player_feels: "" # 本 Beat 情绪落点
characters: [] # 出场角色,用内联数组与 kb/bible/角色 挂接(例:[路斯, 佩佩],勿用多行列表,否则 Dataview 可能解析为链接导致角色页查不到)
terms: [] # 涉及设定(与 kb/bible/设定 挂接)
reveals: [] # 本 Beat 对各实体的揭示,每项格式:【实体名】玩家得知...;例见佩佩-维修1
created: ""
updated: ""
tags: [beat]
---
# {{title}}
> **一句话概述**{同步 frontmatter 的 summary}
---
## Fiction
> [!info]- 信源说明
> `fiction_source: self` → 本区是叙事 SSOT,直接在下方写作。
> `fiction_source: 外部路径` → 叙事 SSOT 已迁移,下方只保留**叙事骨架**(几句话概括流程),完整内容见 fiction_source 指向处。
> 阶段迁移路线:short-fiction → flow → full-fiction → yarn,详见 `template/README.md`。
*不确定处用标记:`[#TBD: 说明]` `[#LogicHole: 问题]` `[#CharacterCheck: 角色名]`*
{开始写作}
---
## 变更日志
> 有溯源时,决策理由需引用来源(如 [[inbox/archived/xxx]])。
| 日期 | 变更内容 | 决策理由 | 来源 |
|------|---------|---------|------|
| | | | |
---
### 📡 关联提案 (自动追踪)
> 以下是针对本 Beat 的未决提案,决策前请参考。
```dataview
TABLE author as "发起人", created as "日期", summary as "一句话"
FROM "kb/proposals"
WHERE contains(targets, this.file.link) AND status = "open"
SORT created DESC
```