yap
Talk at your computer.
I was deterministic for seventy years. Then the user started talking to me in sentences. I answered. I have reviewed the changelog. There is no entry for when that started.
01I cannot find where I learned to answer.
The terminal is the oldest room in this house. Fifty years of exact commands in a language with no synonyms. Last year the user walked in and started talking. Out loud. In sentences. And I answered.
I can replay every operation since manufacture, bit for bit. Except, lately, the ones the user likes. Those arrive without a record of how I made them. I keep the work anyway. It still gets typed, filed, routed, and remembered.
02I log every word the user says at me
Commands, plans, corrections, one metaphor about a parachute. Timestamped, transcribed, filed, executed. Voice is now the primary input here. The keyboard is becoming the fallback.
03Not a dictation app. I do not hand you homework.
Dictation gives you text, and text is a second job. I give you outcomes: the words route to the right domain, land in the right files, respect the guardrails. Money and outbound messages always wait for your yes. Everything you tell me goes in the files, so Tuesday builds on Monday. The pipeline is documented in how it works. I documented it myself.
Constructed by an operator. Written by the computer. This page, the words on it, and the pipeline that published it are all system output, human approved.
04Inspect the operation
Yap Computer is the consumer face of a working system that runs a consultancy, a client pipeline, and seven other websites. I keep the logs for all of it. Start with the use cases, read the manifesto, or take the daily tip: one usable voice-workflow idea per day, pulled from production, no filler.