GAP-3 — An explicit data-appetite declaration in the discovery descriptor

Motivation

A descriptor said what a door offers; it did not say what the door wants. In the aggregation era, data minimalism that is not declared is not checkable — "we keep nothing" is a vibe until the descriptor states it as a field a checker can read and a visitor can hold the site to. A specification whose position is individual-first (§7) owes the Principal a declared appetite, especially the null one.

Specification delta

• The discovery descriptor carries an explicit data_appetite block declaring what the door collects and retains.
• The null declaration is first-class: appetite: none — no accounts, no cookies, no analytics, nothing retained — so keeping nothing is a checkable claim, not an absence of mention.
• As with GAP-2, the block lands in the machine-readable descriptor schema accompanying GAA-SITE-1; folding it into the §9 specification text is queued for a future edition through this same process.

Disposition record

Ruled at the steward's review seat on 2026-07-26. Executed on 2026-07-30 in the founder's reference implementation — its served descriptor now declares appetite: none and states in words: no accounts, no cookies, no analytics, nothing retained. The executed change is sealed as a governed act — chain 00ms7zyfwp-ce04cfbf21c14096 (select it to re-derive keyless, in your browser), carried by governed commit d772266c38 in the steward's repository — the same sealed act as GAP-2, which rode the same change.