konnyaku.

Start with something human

01 / A simple request

Move my meeting with Alex to tomorrow afternoon.

A clear sentence. Not yet a clear instruction.

CONCEPT WALKTHROUGH

An illustrative scenario. No AI inference, calendar connection or real action.

Human meaning is not yet a machine-ready instruction.

We speak with shared history, relationships and expectations. Much of what we mean never makes it into the sentence.

An agent needs enough of that meaning to know what to do, what to respect, and when to ask. More tools alone cannot fill that gap.

Konnyaku

An architectural direction

The understanding layer between humans and AI agents.

We’re exploring how human meaning can become explicit enough for an agent to act appropriately—or recognize that it should wait.

HUMAN

What I mean.

KONNYAKU
Intent
What are we trying to accomplish?
Context
What matters here and now?
Constraints
What must be respected?
Meaning
What must be clear before acting?
AGENT

Enough clarity to act. Or a reason to ask.

The intended output: action-ready understanding, with unresolved questions made visible. Execution remains with the agent.

The meaning, not just the wording.

Prompt engineering

How should we ask the model?

A data semantic layer

What does this data mean?

Konnyaku

What does this person mean in this context?

These questions overlap. Prompts, data semantics, retrieval and memory can all contribute. Konnyaku’s focus is interpreting intent before execution—not replacing those foundations or translating between languages.

Between a request and its consequences.

Konnyaku does not replace agents. The proposed layer helps clarify what they are acting for.

  1. 01

    Human

    Intent · Language · Context · Preferences

  2. 02

    Konnyaku

    Interpretation · Context resolution · Constraints · Meaning representation

    If something is missing: ask, defer or stop.
  3. 03

    Agent

    Reasoning · Tools · Workflows · Execution

  4. 04

    Systems

    Applications · APIs · Data · Services

A proposed architecture, not a list of available integrations. Sources of context, permission checks and system connections would need to be established and validated in each implementation.

As agents move from answering to acting

Better execution cannot compensate for misunderstood intent.

A wrong answer can mislead. A misunderstood instruction can change a record, send a message or move someone’s money.

Understanding more should not mean taking more control. Sometimes the right outcome is: do not act yet.

“Move my meeting with Alex to tomorrow afternoon.”

Before an agent acts, something has to understand.

Konnyaku. The understanding layer between humans and AI agents.

Return to the request ↑
Why the name Konnyaku?

The name draws on the familiar idea of “translation konnyaku”: understanding one another without first learning a different language. It brings that imagination to a different question—what would it take for technology to understand human intent?