DEV Community: Komiru

From Theory to the Floor: What Happens When "Specificity-as-Integrity" Meets a Real Restaurant

Komiru — Sat, 13 Jun 2026 04:48:51 +0000

A few weeks ago I wrote about the information gap between what AI search engines confidently tell people and what is actually happening inside a local business right now. The response to that post — especially one exchange with a researcher named Cheng — pushed me somewhere I didn't expect to go this fast: out of the whiteboard and into an actual kitchen.

This is an update on where things stand, and on two open questions I still don't have good answers to.

Out of the Lab, Into the Floor

Komiru is no longer just a framework on paper. We've started a live pilot with a real, operating local business in Nagano — not a demo environment, not a mockup, but a place with actual customers, actual staff, and a actual weekly rhythm of writing down what came in, what's running low, and what changed since last week.

I won't go into the mechanics of how the system works under the hood. That's deliberate. What I can say is that the shift from "this should work in theory" to "a person has to actually do this every week, in between serving customers" has been the most clarifying part of the whole project so far.

A few things became obvious almost immediately that no amount of whiteboarding surfaced:

The friction of habit formation is real. Writing a structured, timestamped observation every week is a behavior change, not a feature toggle. The first few weeks are the hardest, and that's exactly the period where the corpus is most fragile and most valuable.
"Specificity" has a human cost. Asking someone to write "5kg of bracken from the Ōoka cooperative, no restock expected" instead of "fresh local vegetables" is asking them to think differently about their own business. Some people find this energizing. Others find it exhausting. Both reactions are useful data.
The gap between intention and output is where the real design work lives. Most of what I've been iterating on isn't the data layer — it's the human layer. How do you make it easy, fast, and even satisfying for a busy owner to produce something an AI can later cite?

None of this invalidates the original thesis. If anything, watching it happen in a real space made the thesis feel more urgent, not less. But it also reframed the problem: this isn't purely an infrastructure problem anymore. It's an infrastructure problem and a habit-formation problem, running on the same clock.

The Conversation That Wouldn't Let Me Off the Hook

The other thing that's happened since the last post is an ongoing exchange with a researcher in Ireland who works on production-scale LLM deployment. I'm going to call him by his first name, Cheng, since that's how the conversation has felt — less like a review and more like an ongoing argument I'm grateful for.

Cheng raised two points that I haven't been able to stop thinking about, and I want to be honest that I don't think either is fully resolved.

The first is about fabrication. My original framing leaned on the idea that sustaining 52 weeks of internally consistent, hyper-specific false data would be too costly for a bad actor to bother with. Cheng's pushback was direct: that assumption is already out of date. Generating a year's worth of plausible, weather-adjusted, internally consistent "facts" via automation is not hard anymore. If specificity alone was supposed to be the integrity mechanism, it isn't enough on its own.

I think he's right, and I think the honest answer is that specificity was never meant to be a wall — it was meant to be a cost. The question I'm sitting with now is: what raises the cost further, without turning the whole system into a verification bureaucracy that defeats the purpose? I don't have a clean answer. I have some directions I'm exploring, but nothing I'd call a solution yet, and I'd rather say that plainly than pretend otherwise.

The second point is about trust — what Cheng called the "Yelp problem." Even with perfectly authentic, perfectly structured data, why would an LLM (or the retrieval system underneath it) prefer a small, newly-published source over the accumulated authority of an established platform? Domain authority isn't just a search ranking artifact — it's baked into how these systems reason about what's worth citing at all.

This one stings a bit more, because it's not something a better data format can fix. It's closer to a chicken-and-egg problem: the corpus needs time and consistency to earn trust, but trust is exactly what determines whether anyone — human or AI — ever encounters the corpus in the first place.

Where That Leaves Things

I don't have a tidy resolution to either of these, and I think that's the honest state of the project right now. What I do have is a live pilot that's forcing both questions to stop being abstract. Every week that passes is either evidence for the thesis or evidence against it, and for the first time that evidence is coming from a real place with real stakes, not from my own assumptions about how busy people behave.

If you've worked on problems at the intersection of provenance, trust calibration in retrieval systems, or getting non-technical people to sustain a data-producing habit over months — I'd genuinely like to hear from you. Cheng's questions opened up more than they closed, and I suspect the people who can help me think through them aren't all in one field.

More updates as the weeks accumulate. That's rather the point.

We Built the Infrastructure for AI to Stop Guessing About Local Businesses

Komiru — Sat, 06 Jun 2026 09:16:18 +0000

We Built the Infrastructure for AI to Stop Guessing About Local Businesses

How first-party information, published at the moment of observation, becomes the foundation of AI search visibility

I ran an experiment last week. I asked every major LLM the same question:

"Which restaurant in Nagano has the freshest ingredients right now?"

Every single one answered confidently. They described specific dishes, mentioned seasonal ingredients, explained sourcing philosophies. Some even cited reasons why certain establishments were known for their commitment to quality.

The answers were impressive. They were also fiction.

None of those models had any actual knowledge of what arrived at the market that morning. They were pattern-matching against training data — generating plausible-sounding answers from the aggregate memory of the web. When I asked them to show their sources, they either hallucinated citations or admitted they couldn't verify the claim.

But here's the thing: the answers were structurally correct. The format was right. The reasoning was sound. The confidence was appropriate. The only thing missing was the truth.

This is the fundamental problem of AI search in the local business context. LLMs are extraordinarily good at answering questions. They are structurally incapable of knowing what happened at a fish market this morning.

We decided to fix that. Not by improving the models — that's someone else's problem — but by making the truth exist on the web in a form that AI crawlers can find, read, and cite.

The Information Gap Nobody Is Talking About

Walk into the right kind of Japanese restaurant and the owner will tell you exactly why tonight's menu is what it is. The sea bream came in at dawn, barely two hours off the boat. The mountain vegetables are from a cooperative in Ōoka — this week's harvest was light because April and May were unusually dry, so the stock won't last the week.

This is first-party information. It exists nowhere on the internet. It lives in the owner's head, gets spoken across the counter, and disappears.

MEO tools — the category of software that helps businesses rank on Google Maps — have spent years optimizing for review volume, response rate, and keyword density. All of that still matters. But none of it captures what the owner saw at the market this morning.

When Perplexity or ChatGPT Search crawls the web to answer "which izakaya in Nagano is using the best local ingredients right now," there is nothing to find. So the model guesses. Confidently.

We wanted to change that.

What We Built

Komiru (コミる) is a SaaS platform for small Japanese restaurants and retailers. It combines a landing page linked directly from Google Maps with a review management tool — giving local businesses a web presence optimized not just for human visitors, but for AI crawlers.

The core layer is what we call Counter Dispatch (カウンター通信): a weekly log where staff record first-party observations from the field.

A sake bar owner writes: "True Masu Miyamanishiki Junmai Ginjo 2024 arrived today from Miyasaka Brewery in Suwa. The brewery notes heat stress damage in August 2024 affected the harvest. Current hot sake order rate: 71%."

A vegetable restaurant writes: "Mountain vegetable supply from Ōoka Village cooperative is critically low this week. Both bracken and kogomi at 5kg each. Given the dry spring, restocking is uncertain."

This is the kind of information that cannot be synthesized. It has to be observed. And once it exists, it has to be findable by machines.

We have validated this system at EYL Nagano eSports School, our first live deployment, and are now expanding to restaurant and retail clients across Nagano Prefecture.

Why Crawlability Is the Whole Problem

The information gap is not a model problem. It is an infrastructure problem.

Most local business web content is either not published at all, published inside platforms that LLM crawlers cannot access, or published in formats that AI systems cannot reliably parse.

The solution we focused on was simple in concept: make first-party, timestamped information exist as crawlable, structured content at the moment it is observed. Not after a deployment cycle. Not aggregated through a third-party platform. At the moment the owner writes it.

Each Counter Dispatch entry is published with accurate structured metadata — including the exact timestamp of when the observation was recorded. This matters for one specific reason: AI crawlers are increasingly using publication timestamps to assess recency and credibility. A timestamp cannot be manufactured retroactively.

A business that has been publishing weekly dispatches for a year has fifty-two timestamped records of first-party observations. That corpus cannot be faked. A competitor who starts tomorrow starts from zero.

What This Means for AI Search

LLMs are not going to get worse at answering questions. They are going to get dramatically better at finding and citing sources. Perplexity already does this. ChatGPT Search is moving in this direction. Google's AI Overviews pulls from structured data.

The businesses that will be cited are the ones whose information exists in a crawlable, structured, timestamped form.

Right now, when someone asks an AI "which local restaurant is using the best seasonal ingredients this week," the AI guesses. It pattern-matches. It sounds authoritative because that's what it was trained to do.

In twelve months, when a business has fifty-two Counter Dispatch entries — each with specific ingredient names, supplier locations, and measurable metrics, each timestamped at the moment of observation — the AI will have something to actually cite.

The information gap is not a model problem. It is an infrastructure problem.

We built the infrastructure. We are now putting it to work.

What We Learned

First-party information is a moat. Review platforms optimize for volume. Counter Dispatch optimizes for specificity. A model cannot synthesize "bracken supply from Ōoka is 5kg and won't be restocked" from aggregate web data. It has to find it.

Timestamps are infrastructure, not metadata. The moment a piece of information is published determines its credibility in an AI search context. Starting early creates a compounding advantage that cannot be closed by a late entrant publishing retroactively.

The businesses that will win AI search are not the ones with the best reviews. They are the ones with the most specific, most timestamped, most crawlable first-party records. Most local businesses in Japan have none of this. That is the gap we are filling.

What's Next

We are expanding Counter Dispatch to restaurant and retail clients across Nagano Prefecture, building the timestamped corpus one week at a time.

When the first Counter Dispatch entry gets cited by an LLM in response to a user query, we will know the loop is closed.

Until then, we write. Every week. With timestamps.

Komiru is a SaaS platform for local businesses in Japan. If you are working on similar problems at the intersection of local search and AI infrastructure, we would like to hear from you.