Add Buckets shared-file channels

PRODUCT.md

@@ -0,0 +1,33 @@
+# Product
+
+## Register
+
+product
+
+## Users
+
+Tlon Messenger group members, group administrators, and Tlonbots collaborating inside an existing group. People may arrive to quickly retrieve a file, organize an active project, or review what another member or agent changed. Tlonbots participate through their own ship identities and permissions rather than inheriting their human owner's authority.
+
+## Product Purpose
+
+Tlon Messenger is a group communication and collaboration product built on Urbit. Buckets extends a group with durable, group-owned file storage: a shared Drive or Dropbox that members and authorized Tlonbots can browse and change. Success means a member can understand where a file lives, who or what changed it, and what actions are available without needing to understand object storage, while files remain with the group when an uploader leaves.
+
+## Brand Personality
+
+Familiar, calm, communal. The interface should feel like a native part of Tlon Messenger and earn trust through predictable file-management patterns, concise language, and visible authorship. Agents are ordinary collaborators with a subtle bot marker, not a separate novelty layer.
+
+## Anti-references
+
+Do not resemble an S3 administration console, a second social gallery or feed, or a heavyweight enterprise document-management suite. Avoid storage jargon, dashboard decoration, card-grid sprawl, agent theater, and controls that imply per-file capabilities the backend cannot yet enforce.
+
+## Design Principles
+
+1. Make group ownership unmistakable: files belong to the shared space, not their uploader.
+2. Use earned familiarity: folders, breadcrumbs, list and grid views, selection, and direct manipulation should behave like trusted file tools.
+3. Treat humans and agents as accountable peers: authorize and attribute every action to the acting ship.
+4. Reveal complexity progressively: keep retrieval and upload immediate while placing metadata, activity, and administration one layer deeper.
+5. Preserve continuity with Messenger: reuse its channel shell, identity treatment, media previews, upload feedback, and responsive navigation.
+
+## Accessibility & Inclusion
+
+Target WCAG 2.2 AA. All file operations must work with keyboard and screen readers, have visible focus, use color-independent state cues, maintain touch targets of at least 44 by 44 points on mobile, respect reduced motion, and handle long user-generated names without hiding essential actions.