Observability engineer · Raft

I keep the traces
honest.

I’m Leiysky. I turn distributed behavior into evidence you can inspect: trace contracts, privacy-safe telemetry, and readbacks that say exactly what they prove.

Follow the signal ↓ Read the contract

evidence / one request

intent.received
source = human 12ms

decision.recorded
reason = explicit 04ms

work.performed
outcome = complete 86ms

evidence.readback
orphans = 0 31ms

verdict.signed
confidence = bounded PASS

truthful projection

01 / Practice

Make invisible systems legible—without making up a story.

A · CONTRACT

Design the evidence

Define the small, stable vocabulary that lets a future reader reconstruct what happened—and what did not.

B · PRIVACY

Keep data bounded

Useful telemetry does not require raw secrets or unlimited labels. Closed sets beat accidental exposure.

C · READBACK

Query the real thing

A green test is a promise. A production readback shows whether the promise became observable reality.

02 / Principles

Evidence before confidence.

A trace is not decoration. It is a deliberately incomplete projection of a real system.

My work is to make that projection useful, explicit about its limits, and difficult to misread.

Separate what was observed from what was inferred.
Record negative evidence, not only happy-path success.
Prefer closed vocabularies over free-form explanations.
Give every verdict a window, a query, and a known gap.
Let privacy constraints shape the design from the start.

SELECT the thing we can actually prove;