Pin portal v0.2.3 - attended-bucket lint, first-nav fix; document the rule

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-25 15:38:08 +02:00
parent 1ff3c971ad
commit bd19da9959
2 changed files with 8 additions and 1 deletions
@@ -212,6 +212,13 @@ review resource's transitions — fireable by whoever holds one specific
 record's `?chain=` link plus its matching email (the unsubscribe
 pattern).

+**Attended buckets** (lint-enforced): every `record_as` bucket must be
+read by some `kv` resource in this repo (a desk or listing) — or its
+`aggregates.yaml` entry must carry `attended_by: <who/what consumes
+it>` naming the automation that does. A bucket nothing reads fails
+lint, so no publicly collected answer can land where no one will ever
+see it.
+
 ## Routing: the tree is the router

 The `questions/` directory tree is the URL tree — `index.yaml` names