DailyRecord Health

Auto-generated · 2026-06-11T02:06:04+08:00 · Root: 00-LifeOS/DailyRecord

Files
1048
Markdown records
Naming Consistency
90.9%
`YYYY_MM_DD` + `YYYY-MM-DD`
goals_assoc Non-empty
49.8%
522/1048
Recent-28 Assoc
33.3%
9/27 notes

GitHub Action Context

FieldValueMeaning
Workflowlocal/manual本页由哪条 Action 生成
Event-触发源(schedule / issue / manual)
Run ID-GitHub Actions run 唯一编号
Run URLN/A可直接回看日志与失败原因
Focus Date2026-06-10本轮管道采用的目标日期

Coverage by Phase

2016-2018-RessVR
456 · 43.5%
2025-独立实践期
335 · 32.0%
2024-zzxy
170 · 16.2%
2018-2022-JD
82 · 7.8%
2022-2024-Molly_AI
5 · 0.5%

Naming & Tasks

MetricValueMeaning
Date filename underscore652 (62.2%)`YYYY_MM_DD.md`
Date filename hyphen301 (28.7%)`YYYY-MM-DD.md`
Other filename patterns95 (9.1%)Need naming cleanup policy
Task lines (all)975`- [ ]` + `- [x]`
Tasks with date578 (59.3%)Due date coverage
Tasks with link407Evidence/source traceability
Tasks with tag413Topic/route routing
Strict-format tasks84 (8.6%)AGENTS target format coverage

Goal Tracking Signals

SignalValueInterpretation
goals_assoc field present1037 (99.0%)字段是否存在(不代表有值)
goals_assoc non-empty522 (49.8%)可用于对齐看板的有效关联数据
goals_time present0 (0.0%)时间投入看板可用性
focus_time present0 (0.0%)专注时长口径可用性
Recent 28d goals_time0/27 (0.0%)最近窗口的时间数据覆盖
Recent 28d goals_assoc9/27 (33.3%)最近窗口的关联有效率
Dataview latin path mismatch4拉丁舞总览是否存在路径失配风险

Top Associations

  1. 创造丰盈 · 391
  2. 效率工具 · 295
  3. 学习成长 · 212
  4. 分享传播 · 194
  5. 健康基石 · 122

Goal Tag Governance

MetricValueMeaning
Schedule files2参与统计的排期文件数
TODO items65排期条目总数
with #goal tag26 (40.0%)是否带主线目标标签
canonical #goal tag18 (69.2%)是否命中白名单(health/create/share/learn/tools)
non-canonical #goal tag8需要归一化映射的标签量
  1. #goal/feedback · 2
  2. #goal/tech · 2
  3. #goal/创作 · 1
  4. #goal/体验 · 1
  5. #goal/IP创作 · 1
  6. #goal/音乐 · 1

Action Plan

  1. 把本页当成 Action 发布后的体检门:若 Recent-28 的 goals_assoc_nonempty_pct 低于 60%,下周优先补记录口径,不做新看板。
  2. #goal/* 设白名单映射(health/create/share/learn/tools);非标准标签保留为次级标签但不进入主统计。
  3. 优先把 goals_time 做到最近 14 天覆盖率 ≥ 70%,再增强趋势图与预警策略。
  4. 当 Dataview 路径失配计数 > 0 时,先修查询路径,再做数据解释。