Org-OS reserve API 预览
这页把 Org-OS 当前最值得先联调的 reserve API 收成可直接看的 JSON 预览,方便我们先把组织测评和 API 平台这两条主线接稳。
当前收法
先只开放 Org-OS 的 reserve 结构和轻量提交回包:让我们先把 1 分钟体检、团队邀请、仪表盘、报告和咨询骨架都能通过 API 看清楚,不提前暴露聚合公式和正式写库逻辑。
GET /api/org-os
先按 mode 切换 reserve 结构:overview / checkup / invite / dashboard / report / consult / pricing / flow。
overview
curl -X GET "http://localhost:3000/api/org-os?mode=overview"
checkup
curl -X GET "http://localhost:3000/api/org-os?mode=checkup"
invite
curl -X GET "http://localhost:3000/api/org-os?mode=invite"
dashboard
curl -X GET "http://localhost:3000/api/org-os?mode=dashboard"
report
curl -X GET "http://localhost:3000/api/org-os?mode=report"
consult
curl -X GET "http://localhost:3000/api/org-os?mode=consult"
pricing
curl -X GET "http://localhost:3000/api/org-os?mode=pricing"
flow
curl -X GET "http://localhost:3000/api/org-os?mode=flow"
GET /api/org-os?mode=checkup
先看 1 分钟体检的脱敏题目、公开输出骨架和当前结果页主次动作。
{
"success": true,
"data": {
"source": "org_os_private_server_only",
"mode": "checkup",
"questions": [
{
"id": "ORG_Q01",
"prompt": "最近 30 天里,团队的重要决定更像是:",
"options": [
{
"label": "A",
"text": "大家都知道为什么这么定"
},
{
"label": "B",
"text": "只有少数人知道为什么这么定"
},
{
"label": "C",
"text": "决定经常反复改,团队跟不上"
}
]
},
{
"id": "ORG_Q02",
"prompt": "跨部门协作更常见的状态是:",
"options": [
{
"label": "A",
"text": "协作边界清晰,推进顺畅"
},
{
"label": "B",
"text": "能推进,但经常要反复沟通"
},
{
"label": "C",
"text": "彼此甩锅,推进很慢"
}
]
},
{
"id": "ORG_Q03",
"prompt": "团队遇到问题时更像:",
"options": [
{
"label": "A",
"text": "先讨论原因和调整动作"
},
{
"label": "B",
"text": "先看谁负责,再决定怎么办"
},
{
"label": "C",
"text": "表面没事,私下情绪很重"
}
]
},
{
"id": "ORG_Q04",
"prompt": "老板和团队之间更常见的是:",
"options": [
{
"label": "A",
"text": "理解基本同步,执行差异小"
},
{
"label": "B",
"text": "方向理解差不多,但执行常走样"
},
{
"label": "C",
"text": "老板在讲一套,团队在做另一套"
}
]
},
{
"id": "ORG_Q05",
"prompt": "如果现在要判断是否建议做组织审计,你的直觉更接近:",
"options": [
{
"label": "A",
"text": "组织还算健康,只需轻调"
},
{
"label": "B",
"text": "局部有问题,值得进一步诊断"
},
{
"label": "C",
"text": "已经明显失真,建议尽快做组织审计"
}
]
}
],
"output": {
"orgHealthLevel": "中风险组织",
"auditRecommendation": "建议做组织审计",
"summary": "当前组织更像处在局部失真与协作摩擦叠加阶段,值得进一步进入团队邀请测评与聚合诊断。",
"focusSignals": [
"决策传导偏弱",
"协作边界反复拉扯",
"局部出现虚假和谐风险"
],
"nextActions": [
"先完成团队体检基础问答",
"再获取 Lead_ID 并邀请核心成员测评",
"最后进入组织仪表盘 reserve 结构查看"
]
},
"keepPrivate": [
"组织聚合公式",
"位阶断层阈值",
"CEO 孤岛指数权重",
"Toxic Flow 内部推导"
],
"conversion": {
"exampleLabel": "当前页属于 1 分钟体检结果,不是完整组织报告",
"exampleSummary": "这一步的目标不是立刻讲完所有问题,而是先让老板确认“确实有结构风险”,再继续进入组织报告预览;只有风险已经明显失控时,再直接抬深度组织审计。",
"primary": {
"label": "继续看组织报告预览",
"reason": "先让老板看一版公开报告,再决定是否继续进入标准版咨询,转化更顺。"
},
"secondary": {
"label": "如果已经失控,直接看深度组织审计",
"reason": "当体检结果已经明显偏红,再把深度组织审计抬到前面。"
},
"tertiary": {
"label": "生成团队测评链接",
"reason": "如果想知道问题更像出在哪些人和结构,就继续走团队邀请链。"
}
}
}
}GET /api/org-os?mode=dashboard
再看组织仪表盘 schema、公开模块和当前报告承接动作。
{
"success": true,
"data": {
"source": "org_os_private_server_only",
"mode": "dashboard",
"dashboardSchema": {
"summary": "组织仪表盘当前先把公开 schema 和展示模块定住,后面再把正式聚合引擎与图表实现接进来。",
"modules": [
{
"key": "health",
"title": "模块 A:组织健康度",
"description": "先看一致性、信任度和进化力,作为老板最先看到的组织健康总览。",
"outputs": [
"一致性",
"信任度",
"进化力",
"人效等级"
]
},
{
"key": "formation",
"title": "模块 B:阵型热力图",
"description": "用位阶和四力形成团队阵型视图,先收 schema,不提前承诺正式图表细节。",
"outputs": [
"X 轴:四力",
"Y 轴:位阶",
"气泡:成员",
"风险颜色层"
]
},
{
"key": "isolation",
"title": "模块 C:CEO 孤岛指数",
"description": "这是首页重点模块,直接解释老板是不是已经成为唯一大脑。",
"outputs": [
"孤岛等级",
"指令失真提示",
"是否建议优先处理权力结构"
]
},
{
"key": "collision",
"title": "模块 D:风险对撞机",
"description": "先显示高冲突组合和结构性摩擦对,帮助团队快速看懂冲突源头。",
"outputs": [
"冲突对",
"冲突描述",
"当前业务影响"
]
},
{
"key": "toxic_flow",
"title": "模块 E:负性传播路径",
"description": "先把 source → path → result 的公开结构定住,后面再接正式传播链分析。",
"outputs": [
"source",
"path",
"result",
"业务损失提示"
]
},
{
"key": "action_engine",
"title": "模块 F:操盘建议",
"description": "输出人 / 结构 / 机制 / 风险四类建议,保证最后一定落到可执行动作。",
"outputs": [
"People",
"Structure",
"Mechanism",
"Simulation 180 天预测"
]
}
],
"publicOutputs": [
"组织健康度摘要",
"CEO 孤岛指数",
"冲突对",
"负性传播路径",
"操盘建议"
],
"keepPrivate": [
"位阶断层内部公式",
"四力冲突判定细节",
"Toxic Flow 推导逻辑",
"180 天模拟权重"
]
},
"conversion": {
"exampleLabel": "当前页属于公开示例报告",
"exampleSummary": "先用一版示例组织报告让老板快速感到“说得准”,再把人带向标准版咨询;只有风险已经明显失控时,再把深度组织审计抬到前面。",
"primary": {
"label": "先预约 Org-OS 标准版",
"reason": "对大多数已经完成体检、愿意继续看的团队,先进入 L2 标准版最稳。"
},
"secondary": {
"label": "如果已经失控,直接看深度组织审计",
"reason": "当老板已经明显感到组织快失控,再把 L3 深度版抬为更强动作。"
},
"tertiary": {
"label": "先回仪表盘继续看结构",
"reason": "如果还想先确认问题落在哪些结构模块,再回仪表盘预览。"
}
},
"flow": {
"summary": "当前先把 Org-OS 从官网首页到咨询承接的完整顺序收成一条连续路径,后面继续沿这条路径补真实表单、聚合引擎和组织报告。",
"steps": [
{
"id": "org_flow_1",
"title": "首页转化入口",
"description": "先用老板语言打痛点,讲清这是组织 CT 扫描,不是 HR 测评工具。",
"href": "/org-os",
"focus": [
"首屏痛点",
"核心模块",
"L1-L3 分层",
"转化 CTA"
]
},
{
"id": "org_flow_2",
"title": "1 分钟体检",
"description": "再用 5 个问题快速判断当前组织是否值得继续进入组织审计。",
"href": "/org-os/checkup",
"focus": [
"5 个问题",
"组织健康等级",
"是否建议做组织审计",
"Lead_ID 预留"
]
},
{
"id": "org_flow_3",
"title": "体检结果页",
"description": "先把说得准、问题严重、需要继续测这三层转化感受打出来。",
"href": "/org-os/checkup/result",
"focus": [
"三大指数",
"刺穿结论",
"风险预警",
"裂变 CTA"
]
},
{
"id": "org_flow_4",
"title": "Lead_ID 承接",
"description": "把轻量体检结果接成可继续邀请团队的组织诊断线索入口。",
"href": "/org-os/lead/lead_orgos_demo_001",
"focus": [
"Lead_ID",
"团队元数据",
"当前问题",
"下一步邀请链"
]
},
{
"id": "org_flow_5",
"title": "团队邀请链",
"description": "把邀请核心成员、收样本和准备组织聚合的路径讲清楚。",
"href": "/org-os/invite/lead_orgos_demo_001",
"focus": [
"状态流转",
"角色",
"邀请顺序",
"ready_for_audit 预留"
]
},
{
"id": "org_flow_6",
"title": "组织仪表盘预览",
"description": "再展示 CEO 孤岛指数、风险对撞机和操盘建议这些核心模块。",
"href": "/org-os/dashboard",
"focus": [
"6 个模块",
"公开输出块",
"黑盒边界",
"下一步报告预览"
]
},
{
"id": "org_flow_7",
"title": "组织报告预览",
"description": "把组织报告摘要和 L1/L2/L3 分流承接收成前台可看的骨架。",
"href": "/org-os/report/lead_orgos_demo_001",
"focus": [
"公开报告摘要",
"当前推荐 L2",
"产品分流",
"升级理由"
]
},
{
"id": "org_flow_8",
"title": "标准版咨询",
"description": "把愿意正式进入组织诊断的用户接到 L2 标准版咨询页。",
"href": "/org-os/consult/standard",
"focus": [
"适合谁先进入",
"交付块",
"价格锚点",
"最短咨询路径"
]
},
{
"id": "org_flow_9",
"title": "深度组织审计",
"description": "把已经明显失控或需要陪跑的团队接到 L3 深度版承接页。",
"href": "/org-os/consult/deep",
"focus": [
"升级时机",
"高利润层交付",
"180 天路径",
"预约入口"
]
}
],
"checkpoints": [
"先确认官网首页能不能在 3 分钟内讲清楚为什么值得继续",
"再确认 1 分钟体检和结果页能不能让老板产生继续测的冲动",
"然后确认组织仪表盘和组织报告预览是否把 L1/L2/L3 分流讲明白",
"最后确认标准版咨询和深度组织审计两条转化口已经接住"
]
}
}
}POST /api/org-os
当前先支持 1 分钟体检 reserve 提交:回轻量 risk state、Lead_ID、结果页骨架和 Org-OS -> AI 教练 handoff。
提交体示例
{
"mode": "quick_check_submit",
"answers": {
"ORG_Q01": "C",
"ORG_Q02": "B",
"ORG_Q03": "C",
"ORG_Q04": "C",
"ORG_Q05": "B"
}
}curl 示例
curl -X POST "http://localhost:3000/api/org-os" \
-H "Content-Type: application/json" \
-d '{"mode":"quick_check_submit","answers":{"ORG_Q01":"C","ORG_Q02":"B","ORG_Q03":"C","ORG_Q04":"C","ORG_Q05":"B"}}'返回示例
{
"success": true,
"data": {
"source": "org_os_private_server_only",
"mode": "quick_check_submit",
"result": {
"state": "high",
"leadId": "lead_orgos_high_906021",
"answered": 5
},
"stateCard": {
"title": "⚠️ 你的组织已进入“隐性失控状态”",
"subtitle": "表面在运转,但核心结构正在崩塌",
"badge": "基于 MindOS 组织心智模型生成"
},
"dashboards": [
{
"title": "CEO 孤岛指数",
"level": "高",
"color": "red",
"summary": "你是团队唯一的大脑"
},
{
"title": "组织内耗指数",
"level": "中",
"color": "yellow",
"summary": "协作成本正在上升"
},
{
"title": "结构承载能力",
"level": "低",
"color": "red",
"summary": "当前结构无法支持扩张"
}
],
"insight": "你现在的忙,不是在推动公司,而是在填组织结构的坑",
"conversion": {
"exampleLabel": "当前页属于 1 分钟体检结果,不是完整组织报告",
"exampleSummary": "这一步的目标不是立刻讲完所有问题,而是先让老板确认“确实有结构风险”,再继续进入组织报告预览;只有风险已经明显失控时,再直接抬深度组织审计。",
"primary": {
"label": "继续看组织报告预览",
"reason": "先让老板看一版公开报告,再决定是否继续进入标准版咨询,转化更顺。"
},
"secondary": {
"label": "如果已经失控,直接看深度组织审计",
"reason": "当体检结果已经明显偏红,再把深度组织审计抬到前面。"
},
"tertiary": {
"label": "生成团队测评链接",
"reason": "如果想知道问题更像出在哪些人和结构,就继续走团队邀请链。"
}
},
"lead": {
"href": "/org-os/lead/lead_orgos_high_906021",
"conversion": {
"summary": "Lead_ID 承接页的作用不是结束在这里,而是把轻量体检结果接成可继续进入组织报告和团队邀请的组织线索。",
"primary": {
"label": "继续看组织报告预览",
"reason": "先把公开组织报告看一遍,再决定是否继续进入标准版咨询。"
},
"secondary": {
"label": "继续补团队邀请信息",
"reason": "如果已经准备好拉团队一起测,就继续进入邀请链。"
}
}
},
"coachHandoff": {
"orgStep": "1 分钟体检结果",
"orgRiskLevel": "高风险",
"orgNextStepHint": "先看组织报告预览,再决定要不要继续进入 Org-OS 标准版。",
"orgConsultTier": "deep",
"orgCoachHint": "当前更适合先按深度组织审计这条高风险承接继续。",
"auditSummary": "任务链 orgos-checkup-lead_orgos_high_906021 · 别把组织问题先归因为执行差 · 脱敏 executive_safe",
"parentTaskId": "orgos-checkup-lead_orgos_high_906021",
"targetIds": [
"lead_orgos_high_906021",
"founder-current"
],
"dataSource": "assessment_checkup",
"snapshotCadence": "weekly",
"maskingMode": "executive_safe",
"blindSpotTitle": "别把组织问题先归因为执行差",
"founderBelief": "团队执行跟不上战略",
"diagnosis": "当前更像阶段错配、承载力不足或结构边界失真。",
"correctedStrategy": "先回报告确认断层和承载力,再决定是否推进标准版或深度审计。",
"leadId": "lead_orgos_high_906021",
"inviteStatus": "",
"scope": "",
"stage": ""
}
}
}