universal-harness

Cross-substrate agent governance namespace — a thin facade over aiking-core that lets agents running on any substrate (Claude Code, Hermes, Sancio, OpenClaw, custom CLI clients) reach for the same guards, hooks, routers, and ZIQ retrieval pipeline under a brand-neutral name.

Install

pip install universal-harness
# or, via the AI King brand entrypoint:
pip install "aiking[uh]"

What it gives you

universal_harness re-exports the governance primitives shipped by aiking-core — no duplicate logic, just brand-neutral names so substrate-specific adapters (claude-code-harness, hermes-agent-harness, sancio-harness, openclaw-harness) can depend on a stable interface.

from universal_harness import ziq, fieldread, cerno, FEATURE_META

router = ziq.C0Router()
verdict = router.classify_with_hysteresis(...)

This is the same aiking_core.ziq.C0Router you'd get via from aiking_core.ziq import C0Router — UH only re-binds the name so your downstream code doesn't carry an aiking_* brand stamp.

License

AGPL-3.0-or-later. Commercial licensing available for adopters who need to ship closed-source derivatives — see COMMERCIAL_LICENSE.md.

Versioning

Tracks aiking-core in lockstep via [tool.aiking.version_sync.locked] in the workspace pyproject.toml. A PR cannot bump aiking-core without bumping the locked-set, and scripts/sync_versions.py --check is wired into CI to enforce this.

Phase 2 migration note

During 2026-05-12 → 2026-11-01, some governance modules (guards, hooks, c0_router, cli) still live in the legacy concinno package and are exposed through aiking_core via the concinno-shim. If you need one of those today, fall back to from concinno.guards import … — it will keep working until the EOL date documented in aiking-master-plan-v1-2026-05-12.md.

Companion packages