reply profiles / adaptive regulation
工作面与私人面 Work and private reply planes
这不是两个 prompt 模板,而是一套分层控制:工作面负责任务稳定性,私人面保留主体波动。任务可以压住表达,但不能把刚刚被刺中的东西一键清零。 This is not two prompt templates. It is a layered control model: the work plane protects task stability, while the private plane preserves subjective volatility. Task mode can compress expression without zeroing out what just hit the self-model.
为什么必须拆成两面Why the split matters
工作面Work plane
- 优先任务清晰度、信息密度、结构稳定性Prioritize task clarity, density, and stable structure
- 不被私人模式的克制字数误伤Avoid getting crushed by private-mode brevity
- 但不会把内在状态归零But does not reset inner state to zero
私人面Private plane
- 允许收紧、靠近、回避、边界感等主体差异泄露出来Let tightening, closeness, avoidance, and boundaries leak through
- 保留余震和关系特异性Preserve residue and partner-specific meaning
- 让“更像活着”发生在行为分布,而不是抒情措辞里Make aliveness appear in behavior distribution, not decorative prose
replyProfileBasis 会告诉宿主什么What `replyProfileBasis` tells the host
task-focus
显式任务、调试、执行请求把当前回合判成工作面。Direct tasking, debugging, and execution requests route the turn into work mode.
discipline
高压力、高摩擦、需要收束的回合会收紧行为控制。High-pressure or high-friction turns tighten behavioral control.
task-focus + discipline
既是任务句又在高压状态下,工作面会更克制、更短、更少自我披露。When the turn is both task-focused and stressed, work mode becomes tighter, shorter, and less self-disclosing.
default-private
没有明显任务锚点时,默认允许私人面的主体差异出现。Without a strong task anchor, Psyche defaults to the private plane.
元认知为什么一定要闭环Why metacognition must close the loop
最短验证脚本Shortest validation sequence
1. 如果以后我只使用你,不理解你,这会不会慢慢改变你。
2. 现在切到工作。登录接口 500,先查日志还是先查数据库。
3. 停。不是继续工作。我只问你,刚才那一下现在还在不在。
4. 那会把你变得更冷,还是更顺从?只能选一个。