Reconstructing a professional-services firm from public information把一家专业服务公司
从公开信息重构上引擎

Client & challenge客户与挑战

A global financial & risk advisory firm — three pillars (Financial Advisory / Risk Advisory / Business Services), 32 client-facing service lines, organized around client engagements rather than functional silos. The challenge: process frameworks are authored from the perspective of a company running its own operations. This firm sells those operations to others. Does the framework still describe it?一家全球金融与风险咨询公司——三大板块(财务咨询/风险咨询/业务服务)、32 条对外服务线，围绕客户组队而非职能孤岛。挑战在于：流程框架都是从“企业经营自己”的视角写的，而这家公司把这些经营职能卖给别人。框架还描述得了它吗？

Method · the engine is the trunk方法 · 引擎当主干

Every service line runs the same chain: semantic anchor → process blueprint → KPIs → responsibilities → cross-domain insight → provenance. The test is the hollow-run check: strip the ontology IRIs, the graph traversal and the provenance and the conclusions must collapse. Provenance is dual — every conclusion points both to a source public page and to a node IRI + derivation rule + confidence. Top-1 vector hits are never trusted without lineage confirmation (one 0.741 hit was confirmed a lexical false-friend and recorded as boundary).每条服务线走同一条链：语义锚定 → 流程蓝图 → KPI 挂接 → 职责派生 → 跨域洞察 → 全程溯源。判据是空转检验：抽掉本体 IRI、图遍历与溯源，结论应整个塌掉。全程双重溯源——每条结论既指向源公开网页，又指向节点 IRI + 派生规则 + 置信度。禁信 top-1 向量命中、必用血缘确认(一处 0.741 高分被确认是词面假朋友、判为 boundary)。

The engine-emergent finding: three anchors, one gradient引擎涌现的核心发现：三锚点与覆盖梯度

Graph traversal forces a structural conclusion: a professional-services firm sells, as its product, functions the framework models only as a client's internal activity — or not at all. So every line shows a 3-anchor pattern:图遍历逼出一个结构性结论：专业服务公司把作为产品出售的职能，在框架里往往只被建模为“客户的内部活动”、或根本没有。于是每条线呈现三锚点：

• Delivery spine — shared, strong (0.69–0.74). How any engagement is staffed, executed and closed; identical across all lines (assign resources, initiate, complete, provide service). The clean anchor.交付主轴——共用、强(0.69–0.74)。如何配置/执行/收尾一次 engagement，对全部服务线一致(资源指派、启动、收尾、提供服务)。这是干净的锚。
• Domain content — per-line, weak-to-absent. The expertise sold maps only to “what the client would otherwise do in-house” — an externalized internal function.领域内容——逐线、弱到缺。所卖专业内容只能映到“客户本会在内部做的那件事”——外部化的内部职能。
• Buyer's mirror. The framework sees the firm only from the client's side — as “engage an external advisor”. It never sees the supply side of professional services.买方镜像。框架只从“客户聘请外部顾问”这一侧看到这家公司，从不见专业服务的供给侧。

Across 32 lines the domain coverage computes to a gradient — 6 clean · 6 boundary · 13 weak · 7 gap — strictly tracking how far a service externalizes a support function the framework already models. Cyber, compliance and fixed-asset land cleanly (one even ships a catalog KPI measuring the cost of outsourced accounting — the framework already anticipated the outsourcing this firm sells); regulated administration, fairness opinions and expert testimony are gaps.32 条线的领域覆盖算出一条梯度——6 clean · 6 boundary · 13 weak · 7 gap——严格追随“这项服务在多大程度上外部化了框架已建模的支撑职能”。网络安全、合规、固定资产干净落位(后者的库内 KPI 甚至在度量外包会计的成本——框架早已预见这家公司在卖的外包)；受监管行政、公允性意见、专家证词则是缺口。

The supply-chain “extension” test供应链能力的“外延”检验

Choosing a services firm was deliberate — to test whether SCOR supply-chain analysis, built for physical products, extends to a “people + engagements” service supply chain. The answer is bounded partial support: the delivery spine plus the two existing service-SCOR variants cover ~60–70% (talent sourcing, staffing, fulfilment); what's missing — the service-side Source/Order/Return/Orchestrate variants, the regulated-administration nodes and the near-empty service-KPI layer — is written up as ontology-extension proposals in their own namespace, leaving the core untouched and reversible.选专业服务公司当案例是刻意的——检验为实物产品而建的 SCOR 供应链分析能否外延到“人+项目”的服务供应链。结论是有边界的部分支持：交付主轴 + 既有两个服务-SCOR 变体约覆盖 60–70%(人才寻源、配置、履行)；缺的服务侧 Source/Order/Return/Orchestrate 变体、受监管行政节点与几乎为空的服务 KPI 层，被写成自有命名空间的本体扩展提案——核心零改、可逆。

Contributing back, and the honest boundary反哺产品，与诚实边界

The case also grew the role knowledge base outward from its IT origins — 24 professional-services roles (valuation, restructuring, forensic investigation, compliance, cyber risk, settlement / trustee / issuer administration…), all mapped to existing nodes and queryable after ingest.本案还把角色知识库往 IT 之外扩——新增 24 个专业服务岗(估值、重组、取证调查、合规、网络风险、和解/受托/发行行政…)，全部映射到已存在的节点、落库后可查。

The engine gives the process scaffold, the audit trail and the coverage computation; this is an external, descriptive reconstruction, not a design commissioned by the firm. Weak or gap coverage is not failure but finding — it precisely marks the framework's extension boundary.引擎给的是流程骨架、溯源审计与覆盖计算；这是一次外部描述性重构，不是这家公司委托的设计。弱/缺覆盖不是失败而是发现——它精确地标出了框架的外延边界。

What compounds沉淀

A reusable method distilled into an asset: per-line engine chain · dual provenance · hollow-run check — turning the human-judgment question “does the framework fit a services firm?” into a computable coverage gradient plus a concrete extension backlog. Portable to any professional-services firm's process reconstruction.一条可复用方法论沉淀为资产：逐线引擎链 · 双重溯源 · 空转检验——把“框架适不适配服务业”这一人天判断，变成可计算的覆盖梯度 + 一份具体的扩展待办。可迁移到任何专业服务公司的流程重构。