Hrishikesh “Hrishi” Bhat

I help people see the system inside difficult problems and turn it into a way forward.

I design clearer decisions and operating systems, especially where important judgment is still hidden inside people and processes.

Hrishi Bhat looking calmly toward the camera
Problem solver · AI systems builder · operator

An illustrative diagnostic, not a client case study

One problem, unpacked

A proposed solution becomes useful after we examine the work beneath it.

  1. Automation is a proposed solution, not yet a diagnosis.

  2. Reveal the work

    • Actors
    • Inputs
    • Waits
    • Handoffs
    • Rework
    • Exceptions
    • Decisions
    • Approvals

    What does slow mean?

    • Long total duration?
    • Excessive waiting?
    • Repeated clarification?
    • Too many approvals?
    • Unclear ownership?
    • Inconsistent judgment?
    • Rework?
    • Known
    • Believed
    • Missing
    • Needs measurement
  3. Hidden judgment

    • Decisions being made from memory
    • Context that is not represented in the workflow
    • Different reviewers applying different criteria
    • Exceptions with no explicit path

    The governing constraint

    • Queues and approval boundaries
    • Rework caused by unclear decisions
    • Intake
    • Explicit decision rules
    • Standard path
    • Exception path
    • Human-review boundary
    • Completed work
    • Feedback loop
Step 1 of 5Initial framing

Automation is the last step. Understanding is the first.

How I contribute

Three ways I contribute

Clarify the decision

I make evidence, assumptions, uncertainty, incentives, and trade-offs visible so disagreement becomes something we can examine.

Evidence and assumptions are separated before trade-offs lead to a decision.
In practice

At Sherlock, rule design and escalation paths made validity, severity, and duplicate judgments open to challenge.

A defensible decision has visible reasons.

Design the system

I turn recurring coordination and judgment into clear ownership, rules, workflows, exception paths, and review boundaries.

An intake moves through explicit rules, with a separate exception path and human review.
In practice

Agent-led researcher matching and AI-native bug-bounty operations redesigned the work around the tool.

A tool becomes useful when the work around it has been redesigned.

Teach the model

I explain the structure behind an answer so people can use, question, and improve it independently.

A model becomes practice, then travels into independent use.
In practice

Eight years teaching physics, Python, and Java at Sattva Academy made transfer the test of understanding.

A useful explanation travels without the teacher.

Ideas tested in practice

Three places the method became real

Teaching

Situation

I founded and ran Sattva Academy for eight years, teaching physics, Python, and Java while carrying curriculum and institutional operations.

Hidden system

The real test was not whether a learner could repeat an answer. It was whether they could recognize the same structure when the surface changed.

What I changed

I made the reasoning visible, connected lessons to practice, and designed the surrounding schedule and curriculum to support independent use.

What it taught me

An explanation is complete when someone can use, question, and adapt the model without depending on the teacher.

Security operations

Situation

Across 250+ security engagements, including more than 100 audit contests at Sherlock, decisions carried technical consequences with money and trust at stake.

Hidden system

Validity, severity, and duplicate judgments depended on criteria that had to remain credible when researchers and clients disagreed.

What I changed

I designed rules, judging practices, and escalation paths that put the standard and the reasons for a decision in the open.

What it taught me

Trust under disagreement comes from inspectable reasoning, not artificial certainty or confidence in a single reviewer.

AI-native workflows

Situation

At Spearbit and Cantina, I worked on agent-led researcher matching and AI-native bug-bounty operations across intake, triage, coordination, and payout.

Hidden system

Generating text was not the bottleneck. Ownership, context, handoffs, exceptions, and the boundary for human judgment governed the work.

What I changed

I designed agents around coherent responsibilities, enabling researcher matching to complete in a couple of hours and routine coordination to move with less friction.

What it taught me

AI becomes useful when the workflow changes and ambiguous decisions still have an explicit human-review path.

A working lens

Questions I keep returning to

  1. Evidence

    What do we actually know, and what are we merely assuming?

  2. Judgment

    Where is judgment happening without being named?

  3. Boundary

    What should technology carry, and what should remain human?

  4. Transfer

    Can another person use the model without me?

Beyond the immediate problem

Attention is part of the work

Physics taught me to look for underlying models. Teaching taught me to transfer them. Moving through software, security, and AI systems taught me to enter unfamiliar disciplines without pretending to know them too soon.

For sixteen years, meditation has been an operating practice. Yoga and philosophy deepen the same habit: notice assumption, stay with uncertainty, and protect the attention difficult work requires.

I care about systems because they shape what people must hold in their heads. A good system carries repeatable coordination while leaving meaningful judgment with the person who has the context to use it.

Physics

Find the model

Teaching

Make it transferable

Software

Build the mechanism

Security

Make judgment defensible

AI systems

Redesign the work

Bring me something difficult

Bring me the problem that still feels tangled.Let us find the system underneath it.

Tell me what is happening, who it affects, and what you have tried. You do not need a polished brief.

  • A decision that keeps circling
  • A workflow held together by tacit coordination
  • A process that produces inconsistent judgment
  • An AI initiative that has not changed how work happens
  • An unfamiliar domain that needs mapping before action