Pauta
Version 3.0.0 · 2026-11-07

Where to start
Section titled “Where to start”There are two ways to implement Pauta. A new app starts from
adl-desktop-app-template, a GitHub template repository: a small
runnable app with its tests, CI and release workflows and every repository document, built to the edition its README
names. Click Use this template, run scripts/rename.sh <AppName> <package>, then add any rule from a later
edition. An existing app works through the New app checklist and its own list under
Gaps per app.
What’s new
Section titled “What’s new”Changed Secrets and config safety are MUSTs · The checklist sets the level · One rule for readable text
Fixed Follow the system · Gaps per app · SET-15
How to read it
Section titled “How to read it”MUST A release blocker for a new app.
SHOULD Expected unless the app has a stated reason.
MAY A pattern worth copying when the app grows into it.
Every rule has a permanent ID, such as KBD-07, that links to the rule itself and is never reused. Under the rule,
Check says how to verify it in an app: by reading the code, by a named test, or by hand in the running app.
Reference names where Editora, or another app, does it. An app cites a rule by its ID and the edition it meets, and
anyone, person or coding agent, can audit it rule by rule. For coding agents, every edition serves
llms.txt, how to use these rules, and every
rule in one file as Markdown or
JSON.
Coding agents and LLMs explains them, and how to have an agent build to the rules or audit an
app against them.
When this guide and Editora disagree, check Editora’s code, then fix whichever is wrong.
The family
Section titled “The family”





Pauta 3.0.0 · · Changelog · This page in the latest edition