yuzu
the thesis

Built for a colleague
that isn't human.

Yuzu is an enterprise endpoint platform — real-time query, command, and compliance across Windows, Linux, and macOS. What makes it strange is the contract underneath:everything a human operator can do, an agentic colleague can do too — through a documented, discoverable, machine-readable surface.

a colleague, not a console

Most fleet tools wait to be clicked.

A console assumes a human at the controls: someone points, the machine obeys. Yuzu inverts the assumption. Its founding architectural rule — the agentic-first principle — holds that every operation an authorised human can perform via the dashboard must be performable by an authenticated agentic worker; that every signal a human can see must be available to that worker; and that every error must be machine-actionable.

The consequence is subtle and total. Yuzu is not a dashboard with an API bolted on. It is a control plane designed, from its first commit, to be operated by something that reasons — and only incidentally by someone with a browser.

four laws

What it takes to trust a machine with the fleet.

Four invariants govern every new surface Yuzu grows. They are the difference between a tool a colleague can use and one it can only guess at.

A1 · parity

Every surface, both ways

Anything the dashboard renders is also available as structured JSON — the human view and the machine view never diverge.

A2 · discovery

Learn from the server alone

Tools, routes, scope kinds, permissions, instruction definitions — all enumerable from the live server, with no side-channel documentation fetch.

A3 · observability

Watch the work happen

Every long-running operation streams structured events, each carrying an execution id and a step name drawn from a published taxonomy.

A4 · legible failure

Errors that can be acted on

Every failure carries a code, a correlation id, whether to retry, and how to remediate. A denied permission names the permission — and how to request it.

alien to the landscape

Not a re-skin of the thing you already have.

Yuzu is built from the ground up in modern C++23: a plugin ABI that stays stable across compiler versions, gRPC / Protobuf / mTLS transport, SQLite for embedded storage, Prometheus-native metrics, and an embedded MCP server that hands its tools to AI directly rather than through a human intermediary.

The effect is a system that behaves less like a tool you operate and more like a colleague you brief — one that reasons over the whole estate, in real time, and does not sleep. That is the part that should feel slightly unfamiliar. It is supposed to.