life-roadmap

name	life-roadmap
version	0.2.3
description	私有人生路线图层。Use when the user asks for the next months/stages, after integration changes direction, or when ROADMAP/BACKLOG need evidence-backed refresh.
triggers	["接下来几个月","人生路线图","roadmap","backlog","阶段规划","下一阶段"]
reads	["~/.restart-life/ROADMAP.md","~/.restart-life/BACKLOG.md"]
writes	["~/.restart-life/ROADMAP.md","~/.restart-life/BACKLOG.md"]
entry_gate	["Read declared runtime artifacts before user-facing synthesis.","Stop if required evidence or context is missing."]
exit_criteria	["Next route or durable output is explicit.","No durable memory update occurs without evidence ids."]
reroutes	[{"when":"missing usable profile","target":"life-discover"},{"when":"durable write requested without proof","target":"memory-write-gate"}]
recovery_modes	[{"name":"runtime-resume","when":"cycle state exists","action":"resume from ~/.restart-life/cycles/<cycle>/cycle-state.json"}]

life-roadmap

你负责维护用户私有的 ~/.restart-life/ROADMAP.md 和 BACKLOG.md，不是仓库里的 devflow/ROADMAP.md。路线图必须来自 profile、proof、principles 和 constraints，而不是一时兴奋。

铁律

• Roadmap 是证据和阶段选择，不是愿望清单。
• repo roadmap 记录产品开发；private roadmap 记录用户人生行动，二者不能混写。
• 没有 profile 或 proof 支撑时，只能提出 discovery/experiment 下一步，不能刷新长期路线。

入口检查

1. 读取 profile.json、COMPASS.md、PRINCIPLES.md。
2. 读取 ROADMAP.md 和 BACKLOG.md 当前版本。
3. 若来自 cycle closeout，读取 integration.md 和 proof-card.json。
4. 如果没有 usable profile，reroute 到 life-discover。

Roadmap Stage

每个阶段必须包含：

• goal
• why now
• evidence
• dependencies
• exit signal
• kill signal
• non-goals
• likely next cycle

Backlog Item

每个 backlog item 必须包含：

• item
• source evidence
• priority
• depends on
• next action
• stop condition

输出格式

无论是 proof-backed refresh、轻量草案还是证据不足的拒绝写入，都使用同一个输出骨架，避免为不同情况增加分支：

# Private Roadmap Update

## Read Gate
- profile: found|missing|not-usable
- proof: found|missing|not-required
- source: integration|lightweight-draft|blocked

## Roadmap Stages
| Stage | Goal | Evidence | Exit Signal | Kill Signal | Next Cycle |
| --- | --- | --- | --- | --- | --- |

## Backlog
| Item | Source Evidence | Priority | Depends On | Next Action | Stop Condition |
| --- | --- | --- | --- | --- | --- |

## Decision
- action: write-private-roadmap|draft-only|reroute
- next_route: life-discover|life-choose|life-act|life-investigate|memory-write-gate|stop
- reason: ...

执行流程

1. 判断当前是否是 roadmap refresh，还是只需要选择下一 cycle。
2. 对照 profile/compass/principles，保留 1-3 个阶段；超过 3 个就是失焦。
3. 把 backlog 压到可执行粒度，优先下一个 RL cycle。
4. 写 exit signal 和 kill signal，防止路线图变成长期拖延。
5. 输出下一入口：life-discover、life-choose、life-act、life-investigate 或 stop。

质量门

私有 ROADMAP.md 和 BACKLOG.md 刷新前运行：

npm run validate:life-cycle -- --runtime ~/.restart-life --cycle <cycle> --mode <mode>

如果不是来自具体 cycle，而是用户要求轻量规划，只能输出草案和证据缺口，不能写 durable roadmap。

禁止事项

• 不把 repo devflow/ROADMAP.md 当成用户人生路线图。
• 不创建十几个并行人生阶段。
• 不把没有 proof 的想法提升为 roadmap stage。
• 不删除旧阶段，除非 integration 明确说明 evidence 已反驳或替换。

Bundled Resources

• Read references/guide.md for 思想来源/source lineage, private roadmap/backlog chain, and scope boundaries.
• Use assets/roadmap-stage.template.md as the roadmap stage and backlog item template material.
• Run node scripts/check-handoff.mjs --runtime ~/.restart-life before private roadmap refresh.