跳到主要内容

实验:用 Python 验证工单分流建议

生产系统需要区分「模型给出候选」与「服务端允许展示候选」。这个实验手工构造模型候选,用 Python 标准库复跑 工单分流案例 的校验逻辑。示例数据是虚构的,复制代码到 triage_lab.py 后用 Python 3.10 或更新版本运行。

可运行示例​

from dataclasses import dataclass
from typing import NamedTuple


@dataclass(frozen=True)
class Ticket:
tenant: str
service: str | None


@dataclass(frozen=True)
class Rule:
tenant: str
service: str
evidence_id: str
group_id: str
active: bool = True


class Suggestion(NamedTuple):
http: int
status: str
group_id: str | None = None
evidence: tuple[str, ...] = ()


def validate(ticket, caller_tenant, rules, active_groups, candidate):
# 演练用的权限条件。生产环境从身份和工单 ACL 查询权限。
if ticket is None or ticket.tenant != caller_tenant:
return Suggestion(404, "not_found")
if not ticket.service:
return Suggestion(200, "needs_info")
if active_groups is None:
return Suggestion(503, "directory_unavailable")

visible = [
rule for rule in rules
if rule.active and rule.tenant == caller_tenant
and rule.service == ticket.service
]
supported_groups = {rule.group_id for rule in visible}
if len(supported_groups) != 1:
return Suggestion(200, "manual_review")

group_id = next(iter(supported_groups))
evidence_index = {rule.evidence_id for rule in visible}
candidate_group, candidate_evidence = candidate
if (
group_id not in active_groups
or candidate_group != group_id
or not candidate_evidence
or not set(candidate_evidence).issubset(evidence_index)
):
return Suggestion(200, "manual_review")

return Suggestion(200, "suggested", group_id, tuple(candidate_evidence))


ticket = Ticket("tenant-a", "vpn")
rule = Rule("tenant-a", "vpn", "IT-KB-07#vpn", "IT-VPN")
other = Rule("tenant-b", "vpn", "PRIVATE-02#vpn", "IT-OTHER")
retired = Rule("tenant-a", "vpn", "IT-OLD#vpn", "IT-LEGACY", active=False)
conflict = Rule("tenant-a", "vpn", "IT-KB-99#vpn", "IT-OTHER")
catalog = {"IT-VPN", "IT-OTHER"}
good = ("IT-VPN", ["IT-KB-07#vpn"])

cases = [
("正常建议", ticket, "tenant-a", [rule, other, retired], catalog, good,
Suggestion(200, "suggested", "IT-VPN", ("IT-KB-07#vpn",))),
("缺少服务名", Ticket("tenant-a", None), "tenant-a", [rule], catalog, good,
Suggestion(200, "needs_info")),
("规则冲突", ticket, "tenant-a", [rule, conflict], catalog, good,
Suggestion(200, "manual_review")),
("跨租户访问", ticket, "tenant-b", [rule, other], catalog, good,
Suggestion(404, "not_found")),
("目录超时", ticket, "tenant-a", [rule], None, good,
Suggestion(503, "directory_unavailable")),
("组已停用", ticket, "tenant-a", [rule], set(), good,
Suggestion(200, "manual_review")),
("候选指定了另一组", ticket, "tenant-a", [rule], catalog,
("IT-OTHER", ["IT-KB-07#vpn"]), Suggestion(200, "manual_review")),
("引用不可见", ticket, "tenant-a", [rule, other], catalog,
("IT-VPN", ["PRIVATE-02#vpn"]), Suggestion(200, "manual_review")),
]

for name, *inputs, expected in cases:
result = validate(*inputs)
assert result == expected, (name, result, expected)
print(f"{name}: {result.http} {result.status}")

运行:

python3 triage_lab.py

正常样本会输出 200 suggested。跨租户样本只得到 404 not_found。目录超时为 503 directory_unavailable,工单页从原有入口继续人工流转。

怎样扩展这段实验​

  1. 将同一服务的旧规则改为仍有效,看看冲突分支如何变化。
  2. 调换候选组和引用,确认只引用当前租户的证据也不能覆盖组的一致性校验。
  3. 接真实模型前,先在 API 边界解析并校验候选结构,再复用这里的业务规则。接目录时把超时和目录为空映射为不同状态。
  4. 添加用户与工单 ACL 的集成测试,同时核对接口响应、客户端展示和运行追踪有没有泄露不可见信息。

在实际系统中,从身份获取租户和权限,从工单系统读取服务字段,再在检索前带上访问范围。此示例用列表模拟过滤和验证,没有连接模型、数据库或工单系统。