Status:
Validated— the internal, controlled-network read-only POC has passed its bounded validation Gate. There is no supported release.
Yamazaki is an evidence-driven AIOps governance control plane planned for ClickHouse and Apache Doris. It is intended to organize operational signals, evidence, diagnosis, recommendations, controlled actions, and verification without becoming part of the database query execution path.
The worktree implementation provides a single-process Coordinator, deterministic slow-query detection and diagnosis, fixed read-only ClickHouse and Doris adapters, PostgreSQL control state, a local evidence store, a CLI, and an optional localhost read API. These capabilities are validated only for the bounded POC environment and behavior recorded in the test matrix; this is not a production support claim.
No database action path, multi-agent runtime, message bus, durable workflow, policy service, high-availability deployment, or production support commitment is included.
Use Python 3.13 and the locked environment:
uv sync --locked --all-extras --group dev
uv run ruff format --check .
uv run ruff check .
uv run mypy
uv run pytest tests/unit tests/contract tests/replayThe real infrastructure Gate uses only the cached, digest-pinned images recorded in the test matrix:
./scripts/run_dual_engine_it.shDo not run the Docker Gate repeatedly against unchanged code and infrastructure.
Slow-query governance is the first planned scenario. Future candidate scenarios include cluster health, workload governance, capacity and cost, and configuration or change risk.
Each scenario must begin with official ClickHouse or Doris evidence, preserve
engine-specific semantics, and pass its own validation before its status can
advance beyond Planned or Experimental.
Yamazaki is not intended to be:
- A database or query execution engine.
- A transparent query proxy or synchronous dependency for business queries.
- A generic monitoring data store.
- An unrestricted administrative agent with arbitrary SQL or shell access.
- A claim of compatibility with untested ClickHouse or Doris versions.
- Prefer official engine facts over model inference.
- Keep diagnosis read-only by default.
- Separate analysis from policy-controlled execution.
- Preserve evidence references, uncertainty, and auditability.
- Match validation effort to operational risk.
- Distinguish planned, experimental, validated, and supported capabilities.
- Documentation index
- Architecture boundaries
- Architecture decision records
- Compatibility status
- POC test matrix
- Release policy
See CONTRIBUTING.md. Small documentation changes do not need an Issue, but every pull request must clearly describe the change and the checks that actually ran.
Do not report vulnerabilities in public Issues. Follow SECURITY.md to submit a private report.
Yamazaki is licensed under the Apache License 2.0.