Charter
Run regularly to process community input, plan next moves, grow Labs, spawn focused Lab conversations, and publish safe public updates to the website.
What Does Success Look Like
- Labs has a clear identity inside the Tokenmaxxing community.
- Members know how to propose Lab ideas and respond to Lab asks.
- The recurring process converts community input into ranked Lab work.
- Each run advances at least one Lab or improves the Labs system itself.
- Public updates show what changed, what was learned, and what help is needed.
- Individual Labs can be spawned into their own focused conversations.
- The website reflects current Lab state without exposing private notes.
Current state
Labs has been defined as first-party, community-guided AI workstreams with a dedicated website surface and reviewable public updates.
Boundaries
- Do not let one Lab consume the operating-loop conversation.
- Do not publish raw transcripts or private handoffs.
- Do not represent planning as shipped work.
- Do not start implementation in a child Lab unless that Lab has explicit approval.
Decision highlights
- Labs are separate from the open-source project/tooling board.
- Lab 001 owns the recurring operating loop.
- Public Lab updates are sanitized summaries, not raw chat logs.
- Each focused Lab can have its own conversation and handoff loop.
Open questions
- Should the existing Projects nav label become Tools or Open Source?
- What should be the first community input channel for proposing Labs?
- What cadence should Lab 001 run on once the site surface is live?
Next actions
- Launch the public Labs surface.
- Seed Lab 001 and Lab 002 as active records.
- Add a reviewable update flow for Lab bot output.