Runtime and adapters
Provider contracts, deterministic scheduling, bounded failures, restart behavior, and secret-safe local integration.
Make the room hold.
Help build a coherent, inspectable ensemble without crossing the user-owned data, provider, security, or content lines.
One issue. One owner. One focused branch. ● Verify the work. ●
Contribution path / first places
Read, claim, build, verify.
- Read the repository’s contributing guide, security policy, architecture decision, and content and legal boundaries.
- Open or claim a GitHub issue before substantial work and name the owner.
- Use one focused branch and respect file ownership before editing shared contracts or composition files.
- Add tests for behavior changes and record the real verification commands and output.
- Open a pull request describing intent, evidence, risks, and relevant failure paths. Do not merge your own change without review.
Pick a pressure point.
Packaging and docs
Reproducible local install, backup, recovery, accessibility, and contribution guidance that stays honest about status.
Portable personas
Declarative packs, validators, original work, public-domain research, provenance, and independent review.
Do not submit / hard stop
Keep unsafe material off the call board.
- Secrets and private dataNo credentials, provider keys, transcripts, personal data, production addresses, private infrastructure, or exploit details in public issues.
- Protected characters and likenessesNo television-character packs, copied scripts, actor or celebrity likenesses, voice clones, random web images, or false endorsement claims.
- Executable packsPersona packs are untrusted declarative data, never a path to shell, browser, filesystem, credentials, or external messaging tools.
- Unreviewed historyA historical name or repository directory is not Official Catalog approval. Provenance, rights basis, independent review, exact version, and digest gates still apply.
Security reports stay private.
Do not publish vulnerability details, credentials, private room transcripts, infrastructure details, or personal data in a public issue. Use GitHub’s private vulnerability-reporting or security-advisory workflow when available; otherwise contact the repository owner through GitHub and request a private channel without including sensitive details.
Open the project repositoryProject boundary / attribution
Standalone and independent.
The Green Room is inspired by Block’s Buzz. It is not endorsed by or affiliated with Block, and it is not a Buzz fork or dependency. Contributions must not imply otherwise.
The project is local-first. Users connect their own local or cloud LLM in the local application; cloud providers receive bounded context when selected. Public website code must never collect provider credentials, transcripts, or room data.