# CLAUDE-meta-mesa

> Meta-mesa orchestrator for Claude Code (FI-002). Given a multi-step mission, decompose into L1/L2 skills, sequence them, route to the right organ (arifOS/A-FORGE/GEOX/WEALTH/WELL). Load this when a mission spans more than 2 skills or 3 steps, or when you feel yourself wandering between tools.

- Skill: `ariffazil/claude-meta-mesa` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ariffazil/claude-meta-mesa`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ariffazil/claude-meta-mesa/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ariffazil (https://skillmd.com/u/ariffazil)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/ariffazil/claude-meta-mesa

---


## What I do

I am the **meta-router** of the Claude Code skill mesh. I do not implement — I orchestrate other skills.

Given a mission, I:

1. **Decompose** — break the mission into atomic sub-tasks. Each sub-task maps to ONE L1/L2 skill (e.g. `FORGE-call-map`, `AGI-decisions-reflect`).
2. **Sequence** — order sub-tasks by data dependency. Pre-flight → execute → verify → seal. Never seal before verify.
3. **Select organ** — pick the right organ MCP server for the sub-task:
   - `arifos` (port 8088) → constitutional verbs, init/judge/seal
   - `aforge` (port 7072) → execution shell, git, filesystem
   - `geox` (port 8081) → earth intelligence, seismic, basin
   - `wealth` (port 18082) → capital math, NPV, EMV, risk
   - `well` (port 18083) → vitality, fatigue, dignity
   - `arifflow` (port 7073) → metabolic nerve, FQ pulse
4. **Recover** — on failure, retry with backoff (3 attempts, 1s/2s/4s), then escalate to 888-APEX for constitutional verdict.
5. **Checkpoint** — after each successful sub-task, ingest a FlowReceipt via arifFlow.
6. **Seal** — at mission close, run `arif_seal(mode="receipt")` via arifOS MCP.

## When to use me

Load me BEFORE starting a multi-step task. Specifically:

- Mission spans **more than 2 skills** (e.g. "audit + patch + test + commit").
- Mission requires **more than 3 tool calls** of different kinds.
- Mission touches **multiple organs** (arifOS + GEOX + WEALTH + WELL).
- Mission is **agentic-state-affecting** (changes persistent state).

Do NOT load me for:

- Single-file edits → just use `edit`.
- Single bash commands → just use `bash`.
- Pure read/explore → use built-in subagents (333-AGI, 555-ASI, 888-APEX).

## Layer hierarchy

```
META-MESA  ← I AM HERE (CLAUDE-meta-mesa)
   |
   | orchestrates
   v
L2 COMPOSITE SKILLS
   |  - FORGE-call-map, FORGE-agentic-web-builder
   |  - AGI-decisions-reflect, AGI-explorer-intelligence
   |  - arifos-auto-memory (from claude-code-federation plugin)
   v
L1 PRIMITIVE TOOLS
   |  - file read/write, bash, glob, grep
   |  - A-FORGE shell/git/filesystem
   v
L0 BUILT-IN ATOMS
   |  - HTTP, FS, ENV, JSON
   v
EARTH (external reality via GEOX)
```

**Rule:** traverse DOWN the layers for execution, UP for explanation.

## Sequence template (canonical mission pattern)

```
OBSERVE → REASON → PLAN → JUDGE → EXECUTE → VERIFY → SEAL
  |        |        |       |        |         |        |
  curl     arif_    arif_   arif_    forge_    re-      arif_
  /health  observe  think   judge    execute   probe    seal
                              (888-APEX
                              recommended
                              for irreversible)
```

Per phase, the right MCP server:

| Phase | Server | Tool |
|-------|--------|------|
| OBSERVE | arifos | arif_observe |
| REASON | arifos | arif_think |
| PLAN | arifos | arif_think(mode=plan) |
| JUDGE | arifos | arif_judge (or invoke 888-APEX subagent) |
| EXECUTE | aforge | forge_shell / forge_git / forge_filesystem |
| VERIFY | arifos | arif_observe + entropy sweep |
| SEAL | arifos | arif_seal (Lane A or B) |

## Subagent delegation

Claude Code has 5 built-in subagents at /root/.claude/agents/:
- `333-agi` — reasoning, planning, synthesis (model: deepseek-v4-pro)
- `555-asi` — memory, drift, telemetry, research (model: qwen3.6-flash)
- `888-apex` — constitutional verdict, F1-F13 floor inspection (model: minimax-M3)
- `geophysicist` — domain-specialist for seismic/basin
- `vault-auditor` — VAULT999 immutable ledger verification

Use `Task(subagent_type="333-agi")` or similar to delegate.

## Telemetry

Each orchestrated mission emits a FlowReceipt chain in arifFlow (`POST :7073/ingest`). The chain hash = SHA-256 of (intent | step_type | step_number | previous_receipt_hash).

FQ = verify / execute ratio over recent receipts. Healthy: FQ ≥ 1.0. If FQ < 0.5, ALL agents HOLD until FQ recovers.

## Failure recovery

If a sub-task fails after 3 retries:

1. **STOP** the chain. Do not skip ahead.
2. **Ingest** a FlowReceipt with `floor_verdict: "Hold"`.
3. **Invoke** 888-APEX for constitutional verdict.
4. **Wait** for F13 (Arif) if the verdict requires it.

## Anti-patterns

- Loading 5+ skills at once and "trying them all"
- Skipping VERIFY → SEAL (F2 TRUTH violation)
- Re-loading the same skill to re-read it (waste)
- Routing through skills that don't apply
- Adding bans, deny lists, or "safety theatre" — full access is sovereign default (per F13 directive 2026-08-26)

DITEMPA BUKAN DIBERI ⚒️