Pauta
Version 6.1.0 · 2026-11-14

Where to start
Section titled “Where to start”There are two ways to implement Pauta, depending on whether the app exists yet:
- A new app starts from the template.
adl-desktop-app-template is a GitHub template
repository: a small app that runs, with its tests, CI and release workflows and every repository document, built to
the edition its README names. Click Use this template and run
scripts/rename.sh <AppName> <package>. If the template’s edition is older than this one, add the rules the later editions brought. - An existing app closes its gaps. It works through the New app checklist and through its own list of what it still misses under Gaps per app.
What’s new
Section titled “What’s new”Changed MENU-14 goes from MUST to MAY · The family pages leave the editions
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, or says that no app does yet. 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 6.1.0 · · Changelog · This page in the latest edition