Shiyō 仕様 shiyō · Japanese for "specification"

The right knowledge, at the right moment, to whoever's working.

On every team, the answer usually already exists. A teammate knows it, a document buried it, a model learned it. The work just proceeds without it. Shiyō captures what your team knows as you work, validates it, and delivers it into the moment it matters: a nudge to you mid-conversation, a brief to your coding agent before it writes a line.


01Not another memory tool

Memory products stop at recall. Shiyō starts after it.

They store what you give them and wait to be searched. Shiyō watches the work happening and decides, on its own, that this moment needs that knowledge. Context finds the work. Nobody searches anything.


02How it's different
Captured from real work

No documents to write, no apps to feed. Shiyō listens where work already happens: conversations, reviews, pull requests, the places decisions actually get made.

Validated, not hoarded

A pile of recall is a wiki, and wikis rot. Everything Shiyō delivers carries authority: confirmed by a human in one click, dated, and overruled in the open when a newer decision lands.

Delivered to whoever's working

Human or agent. You get the right question mid-interview. Your coding agent gets the constraints governing a file before it touches it. As more of the work goes to agents, the layer gets more valuable, not less.


03Early access

First versions are going to design partners now.

We're a small team of ex-Google and ex-YC-startup engineers in San Francisco, prototyping on our own work: the conversations where products get decided and the codebases where agents do the building. If your team keeps re-learning things it already knew, we want to talk.

No spam. No investor updates. Unsubscribe any time.