Last posted
Tabs are not chats
A business case outlives an agent
A disputed invoice or supplier onboarding may require weeks of activity. The durable business concern is not a perpetually running agent.
A wait is not a loop
If an agent is waiting for the world to change, it should not spend inference tokens pretending to be busy. Temporal conditions belong to durable runtime state.
The front desk is not the worker
A single conversational entrance should supervise work without becoming an all-powerful business agent.
The smallest team that can do the job
Multi-agent systems should earn each extra worker through independent work, missing expertise or a real coordination need.
An answer is not a completed action
Business work has at least three distinct moments: a plausible recommendation, permission to act, and evidence that the intended effect occurred.
Not every problem needs more reasoning
Missing evidence, a blocked capability, a math problem and an unfamiliar situation require different kinds of compute—not uniformly bigger models.
An ERP adapter is not a magic switch
A stable business capability can outlive a provider integration, but real portability requires mapping semantics, authority, and missing operations.
A capability is not a tool name
Tool catalogs grow with integrations. A capability layer begins by asking what the operation means, who may invoke it, and what evidence it produces.
Memory is not the transcript
What was said, what is true now, and what deserves to be reused are three different stores with different failure modes.
Not every click needs an agent
Generated interfaces become real software when ordinary actions remain ordinary actions, and autonomy is reserved for work that needs it.
The conversation is not the execution
A conversation can describe the work. A durable Execution must own its identity, progress, evidence, dependencies and outcome.
Let's start
Memos is a public notebook for the questions, experiments and decisions that appear while building Underlay.