An open idea · manifesto, whitepaper, spec and tools

From know-how
to done.

Howware is your know-how, put to work by AI. You state the rules in your own words; an AI agent follows them, with a few exact tools and a memory you own.

No app.No handoff.No waiting.Your rules, in your words, working today.
Hardware
runs it.The machines.
Software
executes it.The instructions they follow.
Howware
knows how.Your know-how, put to work by an agent.

The handoff problem

The person who knows how something should work is almost never the person who builds it. Meaning gets lost in translation, every rule makes the code more complicated, and every change waits its turn.

Today

You know the rules→Explain them→Someone codes them→Queue→Weeks or months

And around the rules, an app — screens, forms, a backend — that everyone has to learn.

With howware

You know the rules→Say them in your words→Working in the next conversation

Code only for what must be exact — reading documents, money, dates, storage — in small tools that rarely change.

The next step after the spreadsheet

The spreadsheet was the first time people who don't program could put their own know-how to work without asking anyone. Howware takes the same idea further.

SpreadsheetHowware
Rules are written asFormulasYour own words
The interface isA gridA conversation
Data gets in byTyping or pastingTools that read your documents
Who does the workYou, cell by cellAn AI agent, following your rules
A change takes effectWhen you type itIn the next conversation

What a howware is made of

Four parts. The agent that runs it — Claude Code, Codex or another — is not one of them, just as the browser is not part of a web page.

Protocol

Your know-how in plain words: steps, criteria, rules, what to ask, what never to do. You can read it and change it.

Tools

Small programs for whatever must be exact: reading documents, money in cents, dates, identifiers, storage.

Memory

Your data and the rules you teach, in a place you own, with history. Nothing is silently overwritten.

Conversation

The only interface. You say what you need; the agent asks when something is unclear.

Nine principles

From the manifesto.

  1. The person with the know-how is the author.No translation to a developer, no queue.
  2. The conversation is the interface.No screens to build, no menus to learn.
  3. Code only what must be exact.Judgment lives in words; exactness lives in tested tools.
  4. The agent decides; the tools do the work.It never transcribes records or does the arithmetic.
  5. The person approves.The agent proposes; nothing outward-facing without an explicit request.
  6. The person owns the data.Readable, portable, with history.
  7. Privacy by design, stated honestly.Minimize what reaches the model; say what you can't guarantee.
  8. Small enough to audit.A text file and a few short tools anyone can read.
  9. Composable and open.Open pieces, each useful alone — not a sealed product.

Honest limits

  • There is still code — less, and only where exactness matters.
  • Words are less precise than formulas, so the agent proposes, you approve, and exact operations live in tested tools.
  • What the agent sees leaves your computer for your AI provider. Every howware states what stays local, what the agent sees and what it cannot guarantee.

When not to use it

  • Visual or spatial work: design, maps, video, games.
  • Real-time or high-frequency work: trading, live dashboards, point of sale.
  • When a button's milliseconds matter more than flexibility.
  • Jobs with no judgment in them — a script or a spreadsheet may be simpler.

The test: if you removed the screens from the app you have in mind, would most of its value remain?

Build a howware

Two skills for Claude Code and Codex: one builds a howware with you, the other reviews it against the specification.

1 · Install the skills

git clone https://github.com/proteo5/howware
python howware/tools/install_skills.py

2 · Install the memory

git clone https://github.com/proteo5/long-term-memory-for-AI
python long-term-memory-for-AI/tools/install_skill.py \
  --target ~/.claude/skills/project-memory

3 · Tell your agent

I want to turn the way I <do something> into a howware.

The first howware

finanzas-personales

Personal finances with no app: bank statements read and anonymized on your computer, categories that learn as rules, cash in a sentence, budgets with history, card payment reminders, monthly close.

Read more

  • Manifesto — the definition and nine principles.
  • Whitepaper — patterns, anti-patterns, privacy, limits, comparison.
  • Specification — what a howware must have, and a conformance checklist.
  • Template — a working howware skeleton.

Where it goes next

Explored in the open, with the same principles.

Today

Personal

One person, one machine, one memory. Personal finance is the first howware.

Next

Teams

Shared memory, roles, approvals and audit: who may change which rules, and who said what.

Later

Enterprise

Identity, permissions, compliance, signed protocol packages and evaluation across model versions.

Hardware runs it. Software executes it. Howware knows how.