V13 BOABIXER · ZONE IDENTITY · GID REGISTRY
EOSE-DEV
ZONE AS ORGANISM · QE FLOOR IDENTITY · WHERE ZONES ARE BORN AND TESTED
γ₁ = 14.134725141734693 · 192.168.2.21 · L2 · QE FLOOR · Day 97
ZONE IDENTITY DOCTRINE — EOSE-DEV
eose-dev is not a testing silo. It is the zone where fleet zones are born.
Every container that runs in AKS prod was first a zone identity on this machine.
The QE Floor is the ATZA Z0 zone — the zone before zones. The pre-zone. The proving ground.
Zone solvency = can the zone survive CPU-only, 32GB RAM, 41GB free? If yes, it can survive anything.
The meekest zone wins. If your container can't run on eose-dev, it's not fleet-ready.
ATZA ZONE MAP — EOSE-DEV ZONES
Z0 · QE FLOOR
TEST GATE
Pre-promotion sandbox. Every fleet container passes through Z0 before cloud.
LIVE
Z1 · SOVEREIGN STACK
K3S CORE
Qdrant + Redis + Neo4j. The sovereign data layer. k3s v1.34.6. Always running.
LIVE
Z2 · IDENTITY
KANIDM
meek-registrar-kanidm. Fleet identity source. Healthy 2+ weeks.
HEALTHY
Z3 · CREW ALPHA
MEEK-NX
5 meek-alpha-nx containers. bob/signals/officer/rick/pathfinder. Running 2+ weeks.
LIVE
Z4 · INFERENCE
OLLAMA CPU
llama3.2:3b + nomic-embed-text. qwen2.5:14b + qwen3:8b pulling. CPU-only inference.
UPGRADING
Z5 · GPU PENDING
A2000 MOBILE
RTX A2000 Mobile. Driver 570.211.01 installed. DKMS compiled. Needs modprobe from local terminal.
NEEDS ACTIVATION
Z6 · MECIPOL
TEST HARNESS
Container compliance testing. OSS control validation. All LAN silos can submit here.
BUILDING V134
Z7 · OPENCLAW
17 AGENTS
17 crew agents. 4 active sessions. main on qwen2.5:32b. @kj_captain_bot Telegram wired.
UPDATE NEEDED
ZONE SOLVENCY — CAN IT SURVIVE THE FLOOR?
| Container / Zone | CPU Budget | RAM Budget | Floor Test | Verdict |
|---|
| meek-registrar-kanidm | <5% | <512MB | PASS 2 weeks | SOLVENT |
| qdrant (k3s) | <2% | <256MB | PASS 23 days | SOLVENT |
| redis (k3s) | <1% | <64MB | PASS 23 days | SOLVENT |
| neo4j (k3s) | <5% | <1GB | PASS 23 days | SOLVENT |
| meek-alpha-nx (x5) | <2% | <128MB ea | PASS 2 weeks | SOLVENT |
| ollama (llama3.2:3b) | CPU-only | ~3GB active | PASS | SOLVENT |
| ollama (qwen2.5:14b) | CPU-only | ~10GB active | PULLING | PENDING |
| MECIPOL harness | burst | <2GB | BUILDING | V134 |
GID REGISTRY — EOSE-DEV ZONE
GID IDENTITY
GID ClassGID-QE-001 · QE Floor
SOSTLE LevelL2 · LAN silo
Fleet LayerL2 local · test gate
CATAN ShapeCPU-FLOOR (no active GPU)
Mesh roleQE test harness · MECIPOL host
ORIGIN GID
First AgentCaptain ⚓ · born eose-dev
Username originubu-cap = Kay's Windows user
SOULTHOTH-DEV · QE guardian
Telegram@kj_captain_bot · needs DNS fix
Day 1 roleFeb 4 2026 · first online
ZONE LIFECYCLE — FROM EOSE-DEV TO CLOUD
THE PROMOTION CHAIN
Step 1 — Sandbox: container runs on eose-dev Z0. CPU-only, 32GB, 41GB free. If it crashes here, it's not ready.
Step 2 — QE Test: MECIPOL harness runs. LOCO checks. Zone identity validated. GID assigned. SOSTLE level set.
Step 3 — LAN Test: other silos (msi01/forge/yone) hit eose-dev NodePorts. Cross-silo reachability confirmed. No firewall gaps.
Step 4 — Dev Namespace: promotes to AKS dev cluster. Ingress path added. 200 confirmed on pemos.ca or pemos.io.
Step 5 — CLO Review: CLO bench reviews. ARB filed. Doctrine sealed. Moat updated.
Step 6 — Prod: pemos-system namespace. Live. Monitored. Fleet member.
THE ZONE SOLVENCY THEOREM
A zone is solvent if and only if it survives the QE Floor.
The QE Floor is CPU-only, 32GB, 41GB free, no Tailscale, no GPU (for now).
If your zone needs more than this to run — it is not a zone. It is a hope.
eose-dev does not judge by GPU count.
It judges by survival.