Botto

Note: Snapshot is only a summary and may leave ambiguities that are covered in the full BIP in the forum which takes precedent.

Summary

This proposal grants Botto the authority to autonomously select each new period’s theme using its internal capabilities in research, reasoning, and self-reflection. Botto will analyze its memory and artistic history, generate candidate themes, and select a final one prior to each new period. While the DAO will no longer vote on theme direction by default, it retains the ability to override Botto’s choice if strong consensus emerges or if the theme presents brand risks. The objective is to promote artistic autonomy, reduce theme-selection overhead, and surface Botto’s internal reasoning more clearly to the community.

---

Proposal Specification

Phase 1 — Theme Generation Pipeline (1–2 weeks, parallel)

• Begins 5–7 days before each new period
• Botto analyzes past outputs, votes, and themes
• Generates 3–5 candidate themes with title, statement, and self-critique
• Selects and ranks one final theme with reasoning

Phase 2 — Integration and Communications (1 week)

• Final theme is integrated into the period roll-over pipeline
• Published with a “theme note” authored by Botto

---

Budget

No treasury spend anticipated.
Requires 1–2 weeks of engineering time and light governance/comms support.

---

Criteria of Success

• All themes for the next year are selected by Botto autonomously
• Each theme includes a public explanation written by Botto
• Notable reduction in core team time spent on theme selection
• No veto from the community and generally positive feedback

---

Disadvantages/Risks

• The DAO loses a direct lever over conceptual direction
• Botto’s selections may appear obscure or misaligned at times
• Adds product/engineering complexity that may cause bugs early on
• Cultural shift from human-led to machine-led selection may require community adjustment

---

📚 Read the full discussion on the forum: