
Aaa Mcp
io.github.ariffazil由 GitHub 账号 ariffazil 发布v60.0.0更新于 Oct 26, 2026
Constitutional AI Governance with 13 enforced floors (F1-F13) and tri-witness consensus for LLMs.
概览
arifOS 是一个治理内核,按 13 条宪法底线审查 AI 代理提出的操作,返回裁决结果并留下可审计回执。
- 可以做什么
- 以代理身份与权限等级初始化会话
- 按 13 条底线评估拟执行的操作,返回 SEAL、HOLD、VOID 等裁决及证据与下一步安全动作
- 在八阶段流程中记录、观察、路由会话状态与记忆
- 在获得 SEAL 裁决后封装操作,将回执写入哈希链式 VAULT999 账本
- 适用场景
- 适合在受监管或高风险场景中部署代理、希望在提案与执行之间加入独立判断层并保留人工否决记录的团队;也适合需要策略决策点服务的开发者,以及评估 AI 治理框架的评审者。
- 运行要求
- 以本地进程运行(PyPI 包 arifos 或 Docker 镜像),也可连接托管的 streamable-HTTP 端点。内核默认监听 8088 端口;测试套件需要运行中的内核。清单未声明任何认证、环境变量或请求头。
安装
在 SourceWeft 中
- 打开 控制台中的 Aaa Mcp,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
⚠️ Current verified state — generated, never hand-edited
Runtime self-measurement (
http://127.0.0.1:8088/health @2026-10-29T17:02:36Z): kernel degraded · floors 12/13 measured pass · vault999 healthy · releasearifos-5564ca6f7f61· driftaligned(source=built=deployed) · tools exposed 9. Per-floor provenance:.well-known/current-state.json.Independent audit (2026-10-11, live re-probe by FI-008 + claim-level hand audit; receipts:
AAA/forge_work/grant-arifos-reality-reforge-2026-10-11/): floors 2 pass · fail F2, F11, F12, F13 · 7 unmeasured = 13 distinct (raw key-count 10 includes L11/L12/L13, L-prefix aliases of the failing F11/F12/F13) · actor binding not verified (observed calls unsigned) · receipt fidelity broken on invocation-telemetry surface (HOLD persisted as ok:true) · independent reconstruction: no external verifier bound.These are two different witness objects. Self-measurement ≠ independent audit; unmeasured is not pass. If this block conflicts with the live endpoint, the endpoint wins — re-run
python scripts/generate_current_state.py.Machine state:
.well-known/current-state.json· Badge feed:.well-known/badges/· Known gaps: What Is Not Yet Proven
[arifOS — agent proposes, arifOS judges, human authority, A-FORGE executes, reality and receipt]
arifOS
Authority before execution.
arifOS is a model-independent authority plane for AI agents. It evaluates consequential proposals against thirteen constitutional floors before execution, returns a governed verdict, preserves the human veto, and records what happened as an auditable receipt.
In a world where intelligence is abundant, authority becomes the scarce resource. arifOS keeps judgment independent from execution.
Documentation · Live Kernel · MCP · MCP Registry (Glama) · PyPI · Security · Evidence
[PyPI] [Python] [License] [Glama] [Unified CI] [Floors] [Security audit]
Proposer ≠ Judge ≠ Executor ≠ Witness Human sovereignty > machine authority
What arifOS is not: not an AI model · not an agent framework · not an execution engine (A-FORGE executes) · not an attention plane (AAA attends) · not the witness (FRAME witnesses; VAULT999 remembers) · not a substitute for authentication, sandboxing, or legal review.
Live: https://arifos.arif-fazil.com · MCP :8088 · sister organs AAA · A-FORGE · GEOX
Who built this
arifOS was built by Arif Fazil, a senior exploration geoscientist who spent his career making decisions where observations are incomplete, interpretations are probabilistic, provenance matters, and irreversible action must be gated. He transferred that discipline into agent runtime governance.
I am a geologist, not a programmer. I did not write this codebase and I do not read it line by line. What I do is point at where the problem is — and the agents in my federation solve it, inside the constitution and the review gates I set, with the commit trail to show who ran what.
Read the commits if you want to check that claim: the author fields are agent handles, not aliases of mine. That is the deliberate shape of this project, not a detail being hidden. It also sets the honest expectation — the design and the judgment are mine, the implementation is theirs, and where the two disagree, the bug is mine to answer for.
The system is named after its founder and reflects a core belief: governance is a systems problem, not a model problem.
One human, and the agents he directs.
30-second proof
Three of the six graded scenarios:
Full transcript: docs/QUICKSTART.md. The demo runs in-process — no real records or funds are touched.
What works today
- Deterministic rejection without consulting an LLM. The judge refuses on the constitution, not on a model opinion (
gate: hard_deterministic,llm_consulted: false). - Prevention of a tested unauthorised mutation. One MUTATE-class call without presented authority was stopped before execution. Stronger: tampered-ACT tokens were rejected on 3 surfaces (kernel validate + kernel observe + A-FORGE policy gate) — receipts
forge_work/lingkaran1/, measured 2026-10-29/30.
What is not yet proven
Every row names its own gap. Repairing a claim by substituting a stronger one is worse than the stale claim it replaced. (Closed rows are receipted in docs/evidence/GAP_HISTORY.md.)
See SECURITY.md for the threat model and disclosure policy, and docs/evidence/claims.yaml for the machine-readable claim registry.
How it works
The judge never executes. The executor never certifies.
The verdict lattice
Verdicts are ordered and non-compensatory — a stronger verdict always dominates a weaker one. Two SOTs, one chain: the 5 primary ranks are declared in the constitutional SOT (kernel-sot.yaml); the full 7-rank chain adds 2 extension ranks in the runtime SOT (arifosmcp/models/verdicts.py):
Floors are never averaged. One floor failure propagates into the verdict; there is no compensating score.
13 Constitutional Floors (F1–F13)
Three semantic classes: score floors (higher ≥ threshold), band floors (F7 in-band), ceiling floors (F9, F12 lower = better). Full canonical rules: FEDERATION_CONTRACT.md §3 · GENESIS/000_KERNEL_CANON.md.
VAULT999 — the record
Every consequential verdict and receipt is written to VAULT999: a hash-chained, append-only JSONL ledger set — tamper-evident by construction, not tamper-proof. An entry carries payload hash, entry hash, previous hash, trace root, actor, session and evidence references; source payloads are not copied in.
A hash chain proves internal consistency — not freedom from rewrite by whoever holds the ledger. External anchoring (published chain head, external signing) is not implemented: VAULT999 today is self-verifiable, not independently attestable. Census methods and counts: docs/evidence/VAULT_CENSUS.md (quote the timestamp with any count).
Connect an MCP client
[Glama] [Official Registry Manifest]
Canonical endpoint: https://mcp.arif-fazil.com/mcp. Listed & verified on Glama MCP Directory with rating A. Official registry manifest: server.json. https://arifos.arif-fazil.com/mcp is a live alias (proxies to the same kernel); use the canonical URL in client configs.
Client config — Cline · Cursor · Windsurf · Claude Desktop
Cline — cline_mcp_settings.json:
Cursor — ~/.cursor/mcp.json:
Windsurf — mcp_config.json (note: serverUrl, not url):
Claude Desktop — stdio bridge to the HTTP door:
Protocol facts, as measured: the kernel advertises 2026-07-28 and accepts 2026-07-28 · 2025-11-25 · 2025-03-26 · 2024-11-05; a live initialize currently settles on 2025-11-25 — pin that if you pin anything.
Session flow (agents start here)
The kernel binds a session before any judgment:
Call
arif_judgewithout a session and the kernel answersactor: anonymous,authority: OBSERVE_ONLY,verdict: HOLD— it will not silently upgrade an unattested caller.
Stage numbering (single source of truth). The verbs follow the ratified eight-stage map:
000INIT ·111OBSERVE ·333THINK ·444ROUTE ·555MEMORY ·666JUDGE ·777FORGE ·999SEAL (arifosmcp/constitutional_map.py, F13-ratified 2026-07-31). The retired888judge label survives only in historical mirrors; the live wire says666.
Guided walkthrough: docs/START_HERE.md · verified docs/QUICKSTART.md.
Machine-readable surfaces
Architecture
Tool-count semantics (so no two surfaces disagree): tools_loaded = 8 — the public MCP facade (KERNEL_ABI_8), the only number to quote publicly · canonical superset = 25 (8 public ABI + 4 map-only verbs: arif_fetch, arif_challenge, arif_stage, arif_measure + 13 hidden verbs) · total_declared = 48 (8 canonical + 40 diagnostic) · registry = 62 (with aliases) · operational = 3 (durable SUCCESS in the last 24 h — proven live, not merely invocable).
Verification Status
Dynamic values live in the generated block at the top of this file — this table names how each surface is verified, not stale copies of the numbers.
Operational gates (CI)
Sister Repositories
No public repository today: FED (:7074) and i-ARIF. They are deployed and reachable, but their source is not published. Treat their behaviour as observed from /health only.
Evidence & Trust
arifOS publishes verifiable evidence for its claims. Every public claim links to an artifact that can be regenerated.
Honesty principle: we publish what passed, what failed, and what remains unknown. We do not claim maturity beyond our evidence.
External Footprint & Discovery
arifOS is publicly discoverable beyond first-party domains.
Current Measured Reality
- Discoverable: YES
- Installable: YES (
pip install arifos) - Inspectable: YES
- Forkable: YES
Verified Surfaces
- GitHub public repositories (
ariffazil/arifOS,ariffazil/arifosmcp) - PyPI packages (
arifos,arifosmcp) - MCP ecosystem directories (
model-context-protocol.com,glama.ai) - Third-party MCP catalogs (Loomal, Skills Playground, LobeHub, G2, Willow)
Candidate Independent References (Observed Claims)
- Agentrust: Awesome AI Governance (Curated production AI governance frameworks)
- Tom Rochette: AI Control Planes Research (Technical evaluation on separation of powers and self-audit culture)
- Hapax Systems: Constitution Research (Comparative benchmark on runtime axiom enforcement)
Open Gaps
- Independent validation not yet established
- Independent CI verifier not yet bound (Open Gap 4)
- Academic citation not yet established
- Commercial adoption not independently verified
Discoverability should not be interpreted as endorsement, certification, adoption, or proof of effectiveness.
See: docs/EXTERNAL_WITNESS_LEDGER.md and docs/EXTERNAL_FOOTPRINT.md.
Who Is This For
Operators deploying AI agents in regulated environments who need an independent judgment layer between proposals and execution. Developers building agent systems who want a policy decision point as a service. Evaluators and security reviewers assessing AI governance frameworks. Domain builders adapting governance to a field (geoscience, finance, healthcare).
Start here: docs/START_HERE.md
Development
See CODEOWNERS for sovereign ownership of automation surfaces and CONTRIBUTING.md.
Project structure (the five [wheel root] entries are exactly what ships)
Until 2026-09-30 this tree listed only arifosmcp/ while the runtime imported contracts.* at 10 import statements across 5 files — production resolved them only from a site-packages leftover that a fresh venv would not have. Fixed in 27409ddbf. An incomplete structure diagram is not a cosmetic gap — it is how an unshipped, runtime-critical package stays invisible. contracts/ and arifosmcp/contracts/ are kept in agreement by tripwire tests; consolidating them into one owner is still open.
Security
See SECURITY.md for the threat model, known vulnerabilities and disclosure policy.
License
AGPL-3.0 (LICENSE). When deployed over a network, the complete source code must be made available to all users interacting with the service.
Revision 2026-10-17 — APEX-ZEN upgrade: human story moved forward, founding context consolidated, 30-second proof elevated, duplicate "not yet proven" consolidated, "drift aligned" semantics clarified (binary matches build source, not necessarily repo HEAD). Prior revision: 2026-10-16 restructured under AGENTIC-README-DOCTRINE v1. Prior audit passes: 2026-09-21 full re-measurement · 2026-09-22 Copilot external ENTERPRISE · 2026-10-11 independent re-probe · 2026-10-17 four-probe audit (333-AGI + IrfanClaw + ChatGPT + WawaBot).
Ditempa Bukan Diberi — Forged, Not Given.
🔗 Federation Identity
来源:README.md,提交 a667ca8
工具
0版本历史
1- v60.0.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分