01
专业现实读取Professional Reality Reading
先围绕现实证据、边界、未知项与相邻知识做专业级的梳理与解释。A professional reading of reality evidence, boundaries, unknowns and adjacent knowledge.
专业服务Professional services
解释与介入必须具有明确边界。Interpretation and intervention must have visible boundaries.
PHI OS 专业服务不应该只是旧 hero 上再叠一层卡片。它应该清楚说明：什么是知识、什么是 Ask、什么是 secondary lens、什么是专业判断、什么需要 handoff，以及服务如何继续。PHI OS professional services should clearly separate knowledge, Ask, secondary lenses, professional judgment, handoff and continuity instead of layering more cards on a legacy hero.
服务矩阵Service matrix
按照所需的专业解释与跟进程度选择服务。Choose the service according to the required depth of interpretation and follow-through.
02
个人运行投射Personal Runtime Projection
把 Personal Runtime 作为第二层解释视角，用于现实相关问题，但不把它变成证据或诊断。Use Personal Runtime as a secondary interpretive lens without turning it into evidence or diagnosis.
03
财务现实导航Financial Reality Navigation
围绕现金流、资产、负债、保险、目标与约束做 dated reconstruction 与 professional navigation。Use dated financial reconstruction to support accountable professional navigation.
04
整合式 Runtime ReviewIntegrated Runtime Review
把现实、projection、专业资料与已采取行动的结果放回同一条 review continuity 中。Bring reality, projection, professional evidence and resulting actions back into one review continuity.
05
后续跟进Follow-up continuity
当现实改变时，服务也可以继续版本化地更新，而不是一次性结束。When reality changes, the service can continue in a versioned way rather than ending after one session.
06
明确 handoffExplicit handoff
当问题需要医疗、法律、税务、牌照或其他 regulated judgment 时，PHI OS 明确 handoff，而不是模糊越界。When the issue requires medical, legal, tax, licensed or other regulated judgment, PHI OS hands off explicitly rather than crossing the boundary quietly.
Boundary
不是 generic chatNot generic chat
Professional service 页面不应该长得像一个聊天结果页。用户需要看见的是 scope、process、materials、outputs 与 boundaries。A professional service page should not look like a chat result. Users need scope, process, materials, outputs and boundaries.
Process
可继续的工作流Continuable workflow
Consent → intake → review → interpretation → consultation → follow-up，形成连续性。Consent → intake → review → interpretation → consultation → follow-up.
Responsibility
责任必须可见Responsibility must stay visible
解释者是谁、依据是什么、哪些仍未知、哪些需要 handoff，都必须对用户可见。The interpreter, the grounding, the unknowns and the handoff point all need to remain visible.