Part One · The Company

What we build.

Reshimu builds runtime governance infrastructure for autonomous AI agents. We sit between the agent and the action — classifying every proposed call, every output, every delegation — and we decide, in single-digit milliseconds, whether the system should be allowed to proceed.

We exist because autonomous agents don't fail loudly. They fail quietly, in the background, ten delegations deep into a session that has forgotten what it was for. They call DELETE. They hallucinate APIs that don't exist. They interpret ambiguous instructions five different ways and ship the most convenient one. The audit trail tells you what happened. It does not tell you what to do next.

So we build the layer that intervenes before the damage. Four runtime classifiers — scope, grounding, irreversibility, ambiguity — sit at every level of an agent hierarchy. They are deterministic where they have to be. They are fast. They write every decision to a queryable audit trail. And they assume, by default, that a system which cannot pause is a system which cannot be trusted.

Part Two · The Founder

Why this exists.

Shimon Rosenberg portrait — natural light, environmental, not a headshot
Placeholder · Section 1 — Origin
Early background. How I came to think about systems, what I worked on before this, what kind of problems I gravitate toward. Roughly 200–300 words.
Placeholder · Section 2 — The Intersection
The moment I realized Chassidus and AI alignment were asking structurally the same question: how does intent survive delegation? Roughly 300–400 words. This is the section that earns the whole page.

The Tzimtzum is the original alignment problem. Infinite intent contracts to make space for created action — and the question is whether the trace of that intent persists.

Placeholder · Section 3 — The Moment
What specifically triggered building Reshimu. The actual incident, the specific agent failure, the conversation, the deadline that didn't get met. Roughly 200–300 words. Be concrete.
Placeholder · Section 4 — The Bet
Why runtime governance specifically — not training-time, not prompt engineering, not after-the-fact audits. Why this layer is the one that has to exist. Roughly 300–400 words.
Placeholder · Section 5 — Now
What we're building, who it's for, who I want to hear from. End with an invitation. Roughly 150–250 words.
Part Three · The Name

Why Reshimu?

In Kabbalistic cosmology, the Reshimu is the impression — the trace that remains after a contraction. When infinite light withdraws to make space for creation, it does not disappear entirely. A faint residue persists. That residue is what keeps every created thing connected to its source.

We named this company after that concept because it describes exactly what we build: a system that ensures every agent output, at every level of delegation, remains traceable back to the original human intention that set it in motion.

The impression that keeps the system honest.

There is more to this than infrastructure.
→ Read the Source Materials