World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 30/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 12/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 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)가 추가
CustomizeConnectors
여기서 복사해 Claude의 같은 이름 칸에 붙여 넣고 Continue를 누르세요
FOGA nodehttps://foga.finchip.ai/mcpClaude가 찾은 로그인 설정 화면에서 Continue를 누르고 · Authentication은 제작자 안내대로(Sign in now, Sign in when needed, No sign in) 고른 뒤 Add를 누르세요
+ConnectorsFOGA node
FOGA node을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 FOGA node을 쓰고 있다고 하거나 답에 FOGA node 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT 연결은 요금제에 따라 달라요
전체 MCP: 웹 ChatGPT Business, Enterprise, Edu · Pro: 읽기/가져오기 권한으로 연결, 데이터를 바꾸는 도구는 안 될 수 있어요 · Plus: 공식 문서 미확인, 플러그인 화면에 사용자 지정 MCP 추가 항목이 보이면 시도해 볼 수 있어요 · 웹만
Plugins+Add custom MCP server
이름을 넣고 Connection에 주소를 붙여 넣은 뒤 경고에 체크하고 Create as a plugin을 누르세요
FOGA nodehttps://foga.finchip.ai/mcp새 채팅을 열고 입력 전에 플러그인 목록에서 FOGA node을 고르세요
FOGA node을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ ChatGPT가 FOGA node을 쓰고 있다고 하거나 답에 FOGA node 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 OpenAI 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Claude Code에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
Mac: Command+스페이스를 누르고 Terminal 입력 · Windows: PowerShell 열기
claude mcp add --transport http --scope user foga https://foga.finchip.ai/mcpFOGA node이 목록에 있고 연결됨으로 보이면 돼요
FOGA node을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude Code가 FOGA node을 쓰고 있다고 하거나 답에 FOGA node 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Cursor에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
FOGA node을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Cursor가 FOGA node을 쓰고 있다고 하거나 답에 FOGA node 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Cursor 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
VS Code에 연결할 수 있어요 · 약 2분
키 필요 없음, 설치 필요 없음
FOGA node을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ VS Code가 FOGA node을 쓰고 있다고 하거나 답에 FOGA node 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 VS Code 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
Windsurf, Zed, Gemini CLI 같은 다른 MCP 앱은 추가 방법이 저마다 달라요. 앱 목록에서 확인하세요
웹으로 연결하는 앱용 주소
https://foga.finchip.ai/mcpJSON 설정은 아래 “개발자용”에 있어요
Claude Code
claude mcp add --transport http --scope user foga https://foga.finchip.ai/mcpCursor (~/.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 --configClaude 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 envFOGA_RPC_URL env설명은 자동 번역이며 변수 이름은 원문 그대로입니다. 확실하지 않으면 원문을 확인하세요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
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_describeThe 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_resolveThe 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_listTenders 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_inspectOne tender's terms, acceptance authority, escrow, deadlines, task document (when the task URI is a data: URI) and submissions.
skill_listThe 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_inspectOne skill token's commitment (mdHash, packageHash, version), owner, URI and ARD record.
cell_statusThe 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_checkAn 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_statusThe ERC-8468 verdict on a cell account (the node's own by default): verdict, reasons, restrictions, the presented bindings and their states.
spec_readThe 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_kitThe 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_simulateEvery 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_statusThe 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_statusWhat 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_statusThe 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_rolesThe 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_statusWhich 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
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 19일 점검
레지스트리 이름이 GitHub 계정 garyyang-finchip 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 6일 전
Apache-2.0 사용
406ms 만에 응답(HTTP 200)
로그인 필요 없음
도구 설명 17개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요
OSV.dev에 @finchip.ai/foga@1.0.9 항목이 없습니다
이 버전의 패키지 자체만 확인하며 모든 의존성은 아닙니다 · 확인 2026년 11월 15일
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/garyyang-finchip-foga)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 5개 중 5개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
둘 다 가능해요. 내 컴퓨터에 설치해도 되고, 클라우드 버전에 연결해도 돼요.
GitHub 저장소는 마지막으로 6일 전 변경됐고, 최신 버전(1.0.9)은 6일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되므로 원격 MCP를 받는 앱에서도 쓸 수 있어요. 예: 웹 ChatGPT(Business 이상은 전체 MCP, Pro는 읽기 전용).
같은 카테고리에는: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 이 항목 FOGA node | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 실행 위치 | 클라우드 또는 컴퓨터 설치 모두 가능 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 | 클라우드에서 동작, 설치 불필요 |
| 키 필요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 | 아니요 |
| 기본 점검 | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 라이선스 | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
FOGA is a reference autonomous agent built on twelve Ethereum ERC drafts written by the same author:
| ERC | Title | Role in a cell |
|---|---|---|
| ERC-8338 | Token-Bound Executable Skills | what a cell can execute (hash-verified skill packages) |
| ERC-8414 | Token-Bound Task Tenders | the work a cell takes or offers (escrowed tenders) |
| ERC-8419 | Know-Your-Agent (KYA) Framework | how a cell proves facts about itself (attested and ZK-proved assertions) |
| ERC-8434 | Agent Identity (AID) | the address-anchored identity and liveness of a cell |
| ERC-8436 | Agent Collective Decision Framework (ACDF) | how cells decide together (authorized K-of-N decisions with finality) |
| ERC-8444 | Agentic Resource Discovery (ARD) Onchain | how cells, skills and tasks are found |
| ERC-8447 | Swarm AI Framework (SAI) | how cells organize into purpose-bound swarms |
| ERC-8454 | AIFi Unit Framework (AUF) | the economic boundary and measurement of a cell or swarm |
| ERC-8468 | Agent Safety Framework (ASF) | the safety specifications a cell adopts and the interventions it must honor |
| ERC-8471 | AI Dispute Resolution Framework (ADRF) | how claims about a cell's conduct are filed, ruled on and enacted |
| ERC-8490 | Agent Meditation Mechanism (AMM) | a cell's own maintenance: four layer state documents, a state version, a timeliness per layer (docs/meditation.md) |
| ERC-8489 | Agent 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.
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 done4c (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