NOMOS is a deterministic, auditable decision kernel with built-in LLM guardrails. It does not replace your ERP / CRM / risk / compliance systems — it sits behind them: upstream systems submit structured decision requests, and NOMOS returns candidate sets, counterfactuals, a hash-chained audit trail, and a formal convergence state. The final call always rests with a human signatory.
A second-order causal decision framework. Every round runs three causal operators over a bounded, hash-linked, human-gated reconstruction — never fabricating missing facts, weights, thresholds, evidence, or responsibility.
NOMOS upgrades one-shot causal reconstruction into an iterative, hash-chained, human-gated process. Second-order effects (synergy, redundancy, amplification) must be explicitly declared by the responsible party — the engine never estimates or learns them on its own. LLMs are confined to a three-tier permission zone and cannot flip states, adjudicate, or rewrite weights.
| ✅ It is | ❌ It is not |
|---|---|
| A deterministic decision kernel behind ERP / CRM / risk / compliance systems | A replacement for those business systems |
| A framework that never invents missing facts, weights, thresholds, or responsibility | A probabilistic model that estimates interaction strengths on its own |
| LLM-guarded: models confined to a 3-tier permission zone | An auto-decider — the final call always rests with a human |
| IMDA AI Verify 95/100 · 402 tests, 0 failures | A black-box recommender with no audit trail |
Forward invalidation propagation, backward root-cause tracing (reverse BFS), and delta reconstruction on a copied request — re-running deterministic evaluation to check convergence.
Handles second-order interactions (synergy / redundancy / amplification) under four invariants: non-fabrication, order conservation, effect boundedness, and monotonicity.
Replaces heuristic stop checks with five states — FIXED_POINT, NO_GAIN, BUDGET_EXHAUSTED, DIVERGED, BLOCKED — backed by termination / fixed-point / boundedness propositions.
Three permission tiers — T1 Annotation, T2 Proposal, T3 Narrative — with zone isolation, no adjudication, and strength stripping. LLM output never touches the decision graph directly.
# Install (Python 3.8+), then run the full test suite pip install -e ".[dev]" pytest # 402 tests, 0 failures # Core decision-engine demo nomos-demo nomos-demo --decision examples/baidu_org.json --json # Hub demo with two stress scenarios nomos-hub-demo # Start the API service (dev) export SP_ENV=development uvicorn second_perspective.api.main:app --reload
Key endpoints: POST /v1/hub/analyze, POST /v1/decisions/evaluate, GET /v1/decisions/{id}/history, POST /v1/decisions/{id}/approval. Optional PostgreSQL persistence via SP_DATABASE_DSN and OIDC via SP_OIDC_ISSUER.
Free for personal, non-commercial research; government / enterprise commercial use requires a paid commercial license.
| Audience | Terms |
|---|---|
| Personal researchers | Free for non-commercial research, not for any commercial use |
| Government / enterprise | Prior written authorization required |
| How to apply | Global: ai@nohnlins.com · China: lin@as.nohnlins.com |
NOMOS 是一个确定、可审计的决策内核,内建 LLM 护栏。它不替代你的 ERP / CRM / 风控 / 合规系统,而是坐在它们背后:上游系统提交结构化决策请求,NOMOS 返回候选集、反事实、哈希链审计轨迹与形式化收敛状态。最终结论永远由人类签署。
二阶因果决策框架。每一轮在有界、哈希链链接、人类把关的重建上运行三个因果算子 —— 从不臆造缺失的事实、权重、阈值、证据或责任方。
NOMOS 将一次性因果重建升级为迭代、哈希链链接、人类把关的过程。二阶效应(协同、冗余、放大)必须由责任方显式声明 —— 引擎绝不自行估计或学习。LLM 被限制在三级权限区内,不能翻转状态、裁决或改写权重。
| ✅ 是 | ❌ 不是 |
|---|---|
| ERP / CRM / 风控 / 合规系统背后的确定性决策内核 | 这些业务系统的替代品 |
| 从不臆造缺失事实、权重、阈值或责任方的框架 | 自行估计交互强度的概率模型 |
| 带 LLM 护栏:模型被限制在三级权限区 | 自动裁决者 —— 最终结论永远由人类拍板 |
| IMDA AI Verify 95/100 · 402 测试,0 失败 | 无审计轨迹的黑箱推荐器 |
前向失效传播、后向根因追踪(反向 BFS)、以及基于请求副本的 Delta 重建 —— 重跑确定性评估以判断是否收敛。
在四条不变量下处理二阶交互(协同 / 冗余 / 放大):非臆测性、顺序守恒、效应有界性、单调性。
用五态替代启发式停止检查 —— FIXED_POINT、NO_GAIN、BUDGET_EXHAUSTED、DIVERGED、BLOCKED —— 由终止性 / 定点性 / 有界性命题支撑。
三级权限 —— T1 注释、T2 建议、T3 叙述 —— 区域隔离、禁止裁决、强度剥离。LLM 输出不直接触碰决策图。
# 安装(Python 3.8+),然后跑完整测试套件 pip install -e ".[dev]" pytest # 402 测试,0 失败 # 核心决策引擎演示 nomos-demo nomos-demo --decision examples/baidu_org.json --json # 带两个压力场景的 Hub 演示 nomos-hub-demo # 启动 API 服务(开发环境) export SP_ENV=development uvicorn second_perspective.api.main:app --reload
关键端点:POST /v1/hub/analyze、POST /v1/decisions/evaluate、GET /v1/decisions/{id}/history、POST /v1/decisions/{id}/approval。可选 PostgreSQL 持久化(SP_DATABASE_DSN)与 OIDC 身份集成(SP_OIDC_ISSUER)。
个人非商业研究免费;政府 / 企业商业使用需付费商业授权。
| 对象 | 条款 |
|---|---|
| 个人研究者 | 非商业研究免费,不得用于任何商业用途 |
| 政府 / 企业 | 需事先书面授权 |
| 申请方式 | 国际:ai@nohnlins.com · 中国:lin@as.nohnlins.com |