---
type: Meta
tier: 00_INDEX
strand:
- onboarding
audience:
- all
difficulty: beginner
prerequisites: []
tags:
- federation
- arifos
- geox
- a-forge
- navigation
sources:
- GEOX.md
- Concept_Deployment_Architecture.md
- arifos_forge.md
last_sync: '2026-04-10'
confidence: 0.93
---

# Federation: The Three Wikis

This is the gateway page for the three-wiki system.

If arifOS is the constitutional core, the full knowledge system still has three distinct organs:
- **arifOS** for governance and runtime law
- **GEOX** for Earth-domain grounding
- **A-FORGE** for VPS infrastructure and operational machine reality

## One system, three roles

| Wiki | Role | Main question it answers |
|------|------|--------------------------|
| **arifOS** | constitutional/runtime core | what is allowed, how the system is governed |
| **GEOX** | Earth witness | what is physically true in geoscience |
| **A-FORGE** | infrastructure forge | what is running, how it is wired, and how to operate it |

## Mental model

```text
A-FORGE -> machine, services, deployment, recovery
arifOS   -> governance, floors, verdicts, execution boundaries
GEOX     -> Earth truth, physics, basin/domain reasoning
```

They are not duplicates.
They are one federated stack.

## How to navigate

### Start in arifOS when
- the question is about authority, floors, verdicts, or tool boundaries
- the issue is about what an agent may claim or do
- you need the constitutional/runtime frame first

### Jump to GEOX when
- the issue is geological, physical, spatial, or subsurface
- the answer must be grounded in Earth materials, wells, basins, or seismic interpretation

### Jump to A-FORGE when
- the issue is VPS state, containers, ports, services, topology, deploys, logs, or recovery
- the question is operational rather than constitutional or domain-scientific

## Federation routes

- arifOS -> GEOX through [[GEOX]] and deployment/integration pages
- arifOS -> A-FORGE through [[arifos_forge]] and [[Concept_Deployment_Architecture]]
- GEOX -> arifOS through floor/governance dependence
- A-FORGE -> arifOS through execution/governance boundaries
- A-FORGE -> GEOX through the live VPS component topology

## Practical rule

When a task crosses all three, use this order:
1. **A-FORGE** for machine reality
2. **arifOS** for governance/verdict boundaries
3. **GEOX** for Earth-domain truth

That gives the cleanest stack:
**machine -> governance -> domain grounding**

## Related
- [[What-is-arifOS]]
- [[GEOX]]
- [[Concept_Deployment_Architecture]]
- [[arifos_forge]]
