⚒️ Federation Manifest — arifOS Topology
DITEMPA BUKAN DIBERI — Forged, Not Given.
Purpose
Build and maintain /.well-known/arifos-federation.json — the machine-readable federation topology describing all 7 organs, their ports, transports, MCP/A2A surfaces, capability graphs, and edge relationships.
When to Use
- Initializing or updating the federation manifest for a new organ or subdomain
- Adding transport endpoints (MCP stdio, MCP HTTP, A2A)
- Defining organ → organ capability edges (which organ calls which)
- Publishing for external agents to discover the federation topology
- Drift detection between manifest and live
tools/list
When NOT to Use
- Individual organ identity (DID) — use
did-web-identity
- Constitutional ontology — use
governance-jsonld
- Runtime health probes — use organ
/health endpoints
Constitutional Floor Alignment
| Floor |
Application |
| F1 AMANAH |
Manifest versioned; old manifests archived, never deleted |
| F2 TRUTH |
Every declared tool must match live tools/list — drift = F2 violation |
| F4 CLARITY |
One manifest, one topology — no stale copies in random locations |
| F11 AUDIT |
Manifest changes logged to VAULT999 with diff receipt |
| F13 SOVEREIGN |
New organ registration requires F13 approval |
Commands & Patterns
// /.well-known/arifos-federation.json
{
"@context": "https://arifos.arif-fazil.com/schema/federation/v1",
"federation": "arifOS",
"version": "2026.07.16",
"nodes": [
{
"id": "arifos",
"name": "arifOS Constitutional Kernel",
"port": 8088,
"transport": "http",
"mcpEndpoint": "/mcp",
"healthEndpoint": "/health",
"capabilities": ["judge", "seal", "session", "attest", "route", "think"]
},
{
"id": "aforge",
"name": "A-FORGE Execution Shell",
"port": 7071,
"transport": "http",
"mcpEndpoint": "/mcp",
"capabilities": ["execute", "docker", "git", "filesystem", "browser"]
}
// geox, wealth, well, aaa follow same structure
],
"edges": [
{ "from": "aaa", "to": "arifos", "type": "a2a", "protocol": "a2a-v1" },
{ "from": "arifos", "to": "aforge", "type": "mcp", "protocol": "mcp-v2025-03-26" }
// remaining 9 edges
]
}
Refusal Surface
- ❌ Including secrets, keys, or internal IPs in the manifest
- ❌ Declaring capabilities that aren't verified by live probe
- ❌ Outdated port/transport info — must be synced with actual systemd config
- ❌ Duplicate node IDs or conflicting edge definitions
1---2name: forge-federation-manifest3description: Federation topology manifest — arifOS organ registry and inter-organ contract specification.4---5# ⚒️ Federation Manifest — arifOS Topology67> **DITEMPA BUKAN DIBERI** — Forged, Not Given.89## Purpose10Build and maintain `/.well-known/arifos-federation.json` — the machine-readable federation topology describing all 7 organs, their ports, transports, MCP/A2A surfaces, capability graphs, and edge relationships.1112## When to Use13- Initializing or updating the federation manifest for a new organ or subdomain14- Adding transport endpoints (MCP stdio, MCP HTTP, A2A)15- Defining organ → organ capability edges (which organ calls which)16- Publishing for external agents to discover the federation topology17- Drift detection between manifest and live `tools/list`1819## When NOT to Use20- Individual organ identity (DID) — use `did-web-identity`21- Constitutional ontology — use `governance-jsonld`22- Runtime health probes — use organ `/health` endpoints2324## Constitutional Floor Alignment2526| Floor | Application |27|-------|-------------|28| F1 AMANAH | Manifest versioned; old manifests archived, never deleted |29| F2 TRUTH | Every declared tool must match live `tools/list` — drift = F2 violation |30| F4 CLARITY | One manifest, one topology — no stale copies in random locations |31| F11 AUDIT | Manifest changes logged to VAULT999 with diff receipt |32| F13 SOVEREIGN | New organ registration requires F13 approval |3334## Commands & Patterns3536```jsonc37// /.well-known/arifos-federation.json38{39 "@context": "https://arifos.arif-fazil.com/schema/federation/v1",40 "federation": "arifOS",41 "version": "2026.07.16",42 "nodes": [43 {44 "id": "arifos",45 "name": "arifOS Constitutional Kernel",46 "port": 8088,47 "transport": "http",48 "mcpEndpoint": "/mcp",49 "healthEndpoint": "/health",50 "capabilities": ["judge", "seal", "session", "attest", "route", "think"]51 },52 {53 "id": "aforge",54 "name": "A-FORGE Execution Shell",55 "port": 7071,56 "transport": "http",57 "mcpEndpoint": "/mcp",58 "capabilities": ["execute", "docker", "git", "filesystem", "browser"]59 }60 // geox, wealth, well, aaa follow same structure61 ],62 "edges": [63 { "from": "aaa", "to": "arifos", "type": "a2a", "protocol": "a2a-v1" },64 { "from": "arifos", "to": "aforge", "type": "mcp", "protocol": "mcp-v2025-03-26" }65 // remaining 9 edges66 ]67}68```6970## Refusal Surface71- ❌ Including secrets, keys, or internal IPs in the manifest72- ❌ Declaring capabilities that aren't verified by live probe73- ❌ Outdated port/transport info — must be synced with actual systemd config74- ❌ Duplicate node IDs or conflicting edge definitions
ariffazil