IBEX Harness

Current status

Phases 0–3.5 are shipped. Phase 4 is in progress: Track P operator readiness is the prerequisite for redesigned Track D capability slices. The current repository contains mounted, tenant-scoped, read-only 4.D.1 context/overview and 4.D.2 metadata-only trace list/detail surfaces. These are mounted-but-provisional, not proof of production identity, deployment, hosted acceptance, full management APIs, raw provenance, replay, or operator actions.

See the status ledger, published benchmarks, service inventory, package inventory, and operator architecture boundary.

Quick start

Prerequisites are Docker Compose v2 or Podman Compose, GNU Make, and the versions defined in infra/tool-versions.conf. See TOOLCHAIN.md.

git clone https://github.com/Rick1330/ibex-harness.git
cd ibex-harness

make setup
make check-tools

For a restricted sandbox or Podman machine:

IBEX_RUNTIME=podman IBEX_NETWORK=host make setup

Use make env-doctor for runtime, port, DNS, and injected telemetry diagnostics. make db-seed remains an optional local-development step; never run it against production.

For the complete setup, service startup matrix, test commands, and teardown procedure, read DEVELOPMENT_GUIDE.md.

Service and package navigation

Area	Start here
Go AuthService	services/auth/README.md
Go LLM proxy	services/proxy/README.md
Python management API	services/api/README.md
Python memory service	services/memory/README.md
Context assembly	services/context/README.md
Embedder	services/embedder/README.md
MCP memory server	services/mcp-memory/README.md
Celery workers	services/worker/README.md
Canonical operator Console	services/console/README.md
Shared packages and protobuf	packages/README.md, packages/proto/README.md
Local infrastructure

Engineering and contribution docs

• Architecture
• API documentation
• Environment variables
• Security
• Testing strategy
• Contributing

All status claims must distinguish implemented, mounted-but-provisional, specified-not-implemented, and deferred. Do not infer hosted readiness from local routes, fixtures, schemas, or design documents.