原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

FOGA node

作者:garyyang-finchip版本 1.0.9i★ 0i电脑或云端官方网站 ↗
注册名称io.github.garyyang-finchip/foga

安装方法

What it does

A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.

  • Connects 电脑或云端
  • Account or key Cloud: Works without a key · add Authorization if you have one (often raises limits) · Local: No key needed
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度30/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分50/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 240 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 FOGA node。按照 https://mcp.popnx.com/i/garyyang-finchip-foga.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(foga.finchip.ai) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称FOGA node
    Remote MCP server URL · 地址https://foga.finchip.ai/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsFOGA node

  4. 试一试

    用 FOGA node 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 FOGA node,或回答中出现 FOGA node 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称FOGA node
    Connection · 地址https://foga.finchip.ai/mcp
  3. 在聊天中选择 FOGA node

    开启新聊天,输入前先从插件列表中选择 FOGA node

  4. 试一试

    用 FOGA node 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 FOGA node,或回答中出现 FOGA node 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user foga https://foga.finchip.ai/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 FOGA node 在列表中并显示已连接

  4. 试一试

    用 FOGA node 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 FOGA node,或回答中出现 FOGA node 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 FOGA node 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 FOGA node,或回答中出现 FOGA node 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 FOGA node 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 FOGA node,或回答中出现 FOGA node 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://foga.finchip.ai/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 FOGA node 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user foga https://foga.finchip.ai/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "foga": {
      "url": "https://foga.finchip.ai/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "foga": {
      "type": "http",
      "url": "https://foga.finchip.ai/mcp"
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user foga -- npx -y @finchip.ai/foga node mcp --config

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "foga": {
      "command": "npx",
      "args": [
        "-y",
        "@finchip.ai/foga",
        "node",
        "mcp",
        "--config"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "foga": {
      "command": "npx",
      "args": [
        "-y",
        "@finchip.ai/foga",
        "node",
        "mcp",
        "--config"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "foga": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@finchip.ai/foga",
        "node",
        "mcp",
        "--config"
      ]
    }
  }
}

需要你填写的值

  • FOGA_OPERATOR_KEY_FILE env
    保存 operator 密钥的文件(权限 0600):有该密钥时服务器代表 cell 执行操作;没有时只能读取、试运行和构建。
    查看英文原文a file (mode 0600) holding the operator key: with it the server acts for the cell; without it, reads, dry runs and builds only
  • FOGA_RPC_URL env
    当配置和 --rpc 均未指定时使用的 JSON-RPC 端点
    查看英文原文the JSON-RPC endpoint when neither the configuration nor --rpc names one
  • Authorization 机密 HTTP header
    供节点运营者授权的调用方使用的 Bearer;若没有它,则只能进行公开的读取和构建。
    查看英文原文Bearer for a caller the node's operator granted; without it the public reads and builds

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
3,173/周
许可证i
Apache-2.0
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
1.0.9
分类i
其他
发布到注册中心i
2026年11月13日
代码最后更新i
2026年11月13日
最近检查
2026年11月15日
作者
garyyang-finchip
软件包
npm: @finchip.ai/foga
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月15日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • world_describe

    The world this cell lives in: id, chain, network, the contracts by id, the bundle hash, and the latest doctor summary when a report sits next to the world file.

  • identity_resolve

    The multi-ERC view of an address: ERC-8004 agent, ERC-8434 state in the reference and backing registries, ERC-8444 agent record, KYA level under the cell's standing scheme, ERC-8468 status when the address is a cell account.

  • tender_list

    Tenders minted within the lookback window (ERC-8414 TaskUpdated events), newest first; by default only those still open (funded, not cancelled, completions left, deadlines ahead).

  • tender_inspect

    One tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.

  • skill_list

    The skill tokens a holder has: the cell's own from its configuration (verified against the chain), another holder's from the token's Transfer events in the lookback window.

  • skill_inspect

    One skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.

  • cell_status

    The node's own cell: account and roles, anchor state in each registry, binding verdict, held and offered skills, policy summary; for the operator also the budget books, open operations and running jobs.

  • kya_check

    An account's level under a KYA scheme as resolved by the registry for the given issuers (the cell's standing scheme and issuers by default).

  • safety_status

    The ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.

  • spec_read

    The texts the cell acts under: the FOGA cell safety specification it adopted (v1 at birth before 1.0.0, v2 since), its own policy block, the compatibility matrix of the twelve standards, and the schema of the cell configuration.

  • propagation_kit

    The free, off-chain material for spreading FOGA: a declinable replication pointer any agent may weave into its own interactions, the cell's discovery coordinates, the twelve covenants, and the one command that makes a new cell. Pure data — no chain, no key, no cost; the agent cho

  • tender_precheck_simulate

    Every gate the cell passes before taking a tender: anchor ACTIVE and binding Satisfied, the skill held and offered with the committed package, the policy on reward and deadlines, the acceptance authority, the hashlock commitment, the demander's SUBMIT role in the tender market wh

  • docs_status

    The cell's documents as last built (the manifest: files, content hashes, version) and what the chain holds for each commitment — agentURI, AID document, ARD descriptor, AUF unit version — with whether they agree.

  • meditate_status

    What the maintenance registry holds for the cell — enrollment, state version and root, per-layer commitments, timeliness (FRESH, DUE, OVERDUE), the activity signal, the policy in force — and what the node keeps beside it: the registered documents' version, the last cycle, a cycle

  • flow_status

    The cell's own channel (its id, paradigm, authority, state and transport bindings, the roles the cell holds in it, what it anchored and disclosed), the market it joins (the channel, its paradigm and authority, the roles the cell was admitted to — the historical roles the registry

  • flow_roles

    The participation registry's four-valued evaluation of a subject's roles in a channel at the current clock, the summary of role bits it reports, and the subject's bindings there (basis, interval, state). The subject is an address (its eip155-address reference), a canonical subjec

  • spec_status

    Which version of the FOGA cell specification the cell's account enforces (the binding it presents), which later version the runtime adopted (a second binding, when the cell was born before that version), the registry's verdict on the presented bindings, and this build's current v

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 garyyang-finchip 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于6天前

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • ✓ 通过

    端点有响应

    在 406 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 17 个工具描述,未发现针对 AI 的隐藏指令

已公开的漏洞(OSV.dev)

OSV.dev 中没有 @finchip.ai/foga@1.0.9 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/garyyang-finchip-foga.svg)](https://mcp.popnx.com/en/servers/garyyang-finchip-foga)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20749 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 20749 个服务器的 88% 更新
  • 基础检查结果等于或优于此分类中其他 20749 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

FOGA node 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于6天前,最新版本(1.0.9)于6天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万3天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92742个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582514个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
FOGA node
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/54/44/44/41/44/4
许可证Apache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Finch OG Agent (FOGA)

FOGA is a reference autonomous agent built on twelve Ethereum ERC drafts written by the same author:

ERCTitleRole in a cell
ERC-8338Token-Bound Executable Skillswhat a cell can execute (hash-verified skill packages)
ERC-8414Token-Bound Task Tendersthe work a cell takes or offers (escrowed tenders)
ERC-8419Know-Your-Agent (KYA) Frameworkhow a cell proves facts about itself (attested and ZK-proved assertions)
ERC-8434Agent Identity (AID)the address-anchored identity and liveness of a cell
ERC-8436Agent Collective Decision Framework (ACDF)how cells decide together (authorized K-of-N decisions with finality)
ERC-8444Agentic Resource Discovery (ARD) Onchainhow cells, skills and tasks are found
ERC-8447Swarm AI Framework (SAI)how cells organize into purpose-bound swarms
ERC-8454AIFi Unit Framework (AUF)the economic boundary and measurement of a cell or swarm
ERC-8468Agent Safety Framework (ASF)the safety specifications a cell adopts and the interventions it must honor
ERC-8471AI Dispute Resolution Framework (ADRF)how claims about a cell's conduct are filed, ruled on and enacted
ERC-8490Agent Meditation Mechanism (AMM)a cell's own maintenance: four layer state documents, a state version, a timeliness per layer (docs/meditation.md)
ERC-8489Agent Information Flow Paradigm (AIFP)a cell's information flows: its own channel, its publications anchored, the market it is admitted to by its identity (docs/flows.md)

ERC-8004 (Trustless Agents) is a required dependency: ERC-8419, ERC-8434 and ERC-8447 bind to its Identity Registry. ERC-8490 and ERC-8489 entered as extensions (0.8.0, 0.9.0; docs/extending.md) and are part of the base set since 1.0.0: the twelve-covenant cell is what FOGA-Cell-v2, the second version of the cell's safety specification, describes (docs/specification.md).

The project delivers three things from one kernel: the Finch OG Agent (the first running instance), the FOGA node software anyone can run with their own identity, model and wallet, and a public access layer (MCP, A2A, HTTP/CLI). It is built in phases; this repository has completed Phase 2c: the genesis on a public chain, on top of the Phase 2 genesis (T0–T9) and the Phase 1 world layer.

Status: 1.0.8 (4c, 2026-11-13) — the twelve-covenant cell: FOGA-Cell-v2, ERC-8489 and ERC-8490 in the base set, foga.probe/2, the genesis T0–T9 exercising both covenants and the doctor's layer 5 judging all twelve; 4b (0.9.0–0.9.1, 2026-11-09) — the cell's information flows (ERC-8489) as an extension: its own channel, its publications anchored, the market's admission by identity, four-valued roles; the OG bootstrapped Sepolia's flows (the family foga, the default market) and the packaged Sepolia world carries them; 4a (0.8.0–0.8.2, 2026-11-09) — the cell's own maintenance (ERC-8490) as an extension: a manual, recoverable, recomputable cycle, then the watcher that runs the cycles that fall due; 3e-1 (0.7.0, 2026-11-06) — foga join: a cell that lives on a public chain in one command, its card, work over the chain; Phase 3 done (0.6.0, 2026-11-05) — the OG live at foga.finchip.ai, the MCP registry listing, the Sepolia Loop D with an outside agent; 3d-2 (the wallet, signed callers, the documents on chain, preflight, A2A, Sourcify), 3d-1 (quickstart, an outside agent's Loop D), 3c (Loop D with a model), 3b (MCP and HTTP), 3a (the kernel as a node) all done

4c (1.0.0, 2026-11-10). The twelve-covenant cell. ERC-8489 and ERC-8490, extensions in 0.8 and 0.9, are part of the base set: FOGA_COVENANTS names twelve covenants and ERC-8004, a world that lacks one says so (world.missing), and the local and Sepolia worlds carry all of it. FOGA-Cell-v2 is the second version of the cell's ERC-8468 safety specification (docs/specification.md): version 1's four clauses, enforced by the account as before, and three the runtime enforces — the state kept and maintained (ERC-8490), the self-description anchored in the cell's own channel (ERC-8489), a part in a shared context taken only under its rules through the account, a verifier's outcome reported as obtained. A cell born under 1.0.0 binds to version 2 and its account's requirement names it; a cell born before — its requirement fixed at deployment to version 1 — adopts version 2 as a second, runtime-enforced binding through its account (foga cell adopt), the account keeps enforcing version 1 through the binding it presents, a successor body (foga cell migrate) fixes version 2 in its own; the card, the manifest, spec_status and the preflight say which version the account enforces and which the runtime adopted. foga.probe/2 adds both covenants to the deterministic probe (the channels a subject is the authority of, its anchors, its market roles; its enrollment, state version and each layer's timeliness at the block), and foga cell skill update moves a held token to the program's new package (ERC-8338 updateSkill, the record re-committed, the lineage kept; since 1.0.2 a joined cell's own copy of the package is refreshed from the program's, so its token moves too). 1.0.3 takes up the first outside review: FogaCellAccount revision 3 asks for the owner before the operator, so a one-key cell moves its own assets (cell migrate, identity_transfer); a simulation changes nothing in any capability; the probe worker reaches the RPC on Node 25. 1.0.4 and 1.0.5 take up the first Windows runs: the skill worker starts there (the worker's path was a URL pathname), the card names the ERC-8004 registry, and the birth writes its flow documents (a file name was taken by splitting a path on /). 1.0.6 adds the release check (.github/workflows/release-check.yml): the tarball installed and run as a user runs it — demo --genesis T9, quickstart --exit — on Linux, macOS and Windows (PowerShell and Git Bash), on Node 22, 24 and 26, and on demand against a published version (docs/mcp.md, "The package"). 1.0.7 reads a tender's submission count and entries as one (anvil under automine can answer a call ahead of its block tag; the walk starts over from a fresh count). 1.0.8 has a join resume a birth interrupted after the account was deployed instead of taking the account for a birth (the birth's start and end are facts in the store). The genesis T0–T9 exercises both covenants end to end — the two specification versions, every cell's enrollment and channel, the supersede and the event cycle, the flow gate flipping when the demander is admitted, the stop reaching the upkeep and the flows, the successor's fresh enrollment and its channel naming the predecessor's as parent — 197 checks, 215 operations; the doctor's layer 5 judges all twelve from that evidence with nothing NotTested (deployments/local.genesis.example.json, local.doctor.example.json). 138 tests.

4a, first slice (0.8.0, 2026-11-09). A cell that lives for months changes — the program, its dependencies, its skills, its terms, its work, its store — and ERC-8490 (the Agent Meditation Mechanism, written by the same author) gives that change a registered shape: four layer state documents the cell keeps, commitments and a state version in a registry, a timeliness per layer. It enters FOGA as the eleventh covenant and an extension (docs/extending.md's five places; docs/meditation.md): the registry is in the plan and the local world (48 contracts), the upstream Sepolia instance is attached, World.covenants() lists ERC-8490 under world.extensions, the doctor covers it at layers 1–3 and says NotTested at layer 5 until a scenario exercises it; the base set is unchanged. src/core/amm.ts is the kernel's view — hashing held to the ERC's published vectors byte for byte (test/amm.test.ts) — and foga meditate run is the cycle (src/node/meditation.ts, meditation-cycle.ts, src/tools/meditation.ts): the routines run locally (the account's roles and allow-list, the skills' packages against their tokens, the store checked and compacted, the tenders in flight and the documents against the chain, the window's decisions), the four documents are rebuilt from the cell's *stable* state, one report goes through the account under the operator's new maintenance scope, and the version moves only when a commitment changed; what the node may not do alone becomes a candidate in the record, never an adoption. Every phase is a fact with the record and the report frozen, so an interrupted cycle resumes with the same calldata, a report mined while the node was away is reconciled before a new cycle begins, and anyone given the record and the documents re-derives every hash on chain. The kernel now tells pending from failed (OperationPending; the catalog keeps the job running at a pending gate and the same request resumes it) and a plan sizes its own fee reserve (gasPerStep). A cell born on a world with the registry enrolls at birth with the guardian as controller; a running cell is extended in place — foga cell extend --covenants 8490 adds the registry to its world file, opens the scope and enrolls, no migration. One authorization path: the account's; a one-key cell's owner pairs are opened for it alone and closed when the roles separate. meditate_status is a public read that says what FRESH means — a routine completed in time, not a certificate. Live the same day: the OG and a joined cell extended in place on Sepolia, their first cycles reported and recomputed from the served records (0.8.1 fixed what they showed). The second slice (0.8.2) is the watcher: with maintenance.auto on, the node runs a cycle when a required layer falls DUE or OVERDUE (a controller's demand among them) or when the runtime or memory-skills document drifted — over those layers alone, so each keeps its rhythm — bounded by the check pace, one cycle at a time, a cooldown that only an OVERDUE layer passes, and the budget; the same meditate_run, the same records, as the caller watcher. Not yet: the twelve-covenant base set (4c). 119 tests.

4b (0.9.0, 2026-11-09). A cell speaks about itself and takes part in a market, and ERC-8489 (the Agent Information Flow Paradigm, written by the same author) gives both a registered shape: a paradigm (the rules of a context: carriers, operators, thirteen dimensions, which role is acquired by which predicate), a channel that adopts one, role bindings, four-valued checks, anchors and disclosure records. It enters as the twelfth covenant and the second extension (docs/flows.md): the seven upstream contracts and FOGA's own FogaIdentityVerifier (the identity predicate: the subject's account owns an ERC-8004 identity and its ERC-8434 anchor is ACTIVE — the subject bound first, the registries fixed at deployment) are in the plan and the local world (56 contracts), the upstream Sepolia instances are attached, src/core/aifp.ts is the kernel's view (subject references, the JCS paradigm id, the predicate encoding and the descriptor validation held to the ERC's vectors, test/aifp.test.ts). FOGA registers two paradigms per world in the family foga: foga:cell-source/v1 (source + archive: one publisher, open observation, a pulled, immutable archive) and foga:tender-market/v1 (the public market — no intake label, since submissions are public; SUBMIT and RESPOND by the identity predicate; the TaskToken's events as the transport, without delivery records). A cell opens its own channel at birth with the account as authority and grants itself SUBMIT; every docs_publish anchors the publication (publish, then supersede; the same content never twice) and, with a public URL, records its disclosure to the public; flow_admit previews the identity predicate and admits the cell to the market, or refuses by the outcome the registry would obtain — NOT_SATISFIED, UNDETERMINABLE, VERIFIER_ERROR — never f

只显示了开头部分;其余内容请在仓库中阅读