3.3 KiB
Community Environments
This directory contains environments contributed by the community. These environments demonstrate various use cases and extensions of the Atropos framework.
Available Environments
1. Lean Proof Environment (lean_proof_env/)
Author: GabinFay Purpose: Testing Language Learning Models (LLMs) on Lean theorem proving tasks
A comprehensive environment for evaluating LLMs on formal mathematical reasoning using the Lean theorem prover. Features include:
- Support for custom problem datasets or MiniF2F benchmark
- Integration with Lean 4 theorem prover
- Configurable difficulty levels and problem sets
- Automated proof validation
Requirements: Lean 4 installation, OpenAI API key
2. Router Environment (router_env/)
Author: GabinFay Purpose: Multi-agent routing and coordination system
A sophisticated environment for testing agent routing and coordination capabilities. Includes:
- Multiple specialized agents (calendar, contact, Gmail, telephony, etc.)
- Model Contextualized Protocol (MCP) tools integration
- Spotify, Google Maps, and Perplexity integrations
- Complex multi-turn conversation handling
Features:
- Telephony agent with inbound/outbound call handling
- Calendar and contact management
- Memory and calculation agents
- Router agent for intelligent task delegation
3. Philosophical RLAIF Environment (philosophical_rlaif_env.py)
Author: GabinFay Purpose: Reinforcement Learning from AI Feedback (RLAIF) for philosophical reasoning
An environment focused on training models for deep philosophical inquiry and reasoning. Features:
- Deep thinking prompts with systematic reasoning processes
- Preference learning for philosophical depth and nuance
- Multi-perspective analysis and assumption questioning
- Evaluation of response quality for philosophical discussions
Capabilities:
- Generates paired responses for preference comparison
- Uses judge models to evaluate philosophical depth
- Tracks preference consistency and reasoning quality
- Supports WandB logging for training insights
Contributing
To contribute a new environment to the community collection:
- Fork the repository and create a new branch
- Add your environment to this
community/directory - Include comprehensive documentation:
- README with setup instructions
- Requirements file for dependencies
- Example usage and configuration
- Follow naming conventions:
- Use descriptive directory names for complex environments
- Single file environments should have descriptive names
- Test thoroughly before submitting
- Submit a pull request with a clear description
Environment Standards
Community environments should:
- Include clear documentation and setup instructions
- Specify all dependencies in requirements files
- Provide example configurations and usage
- Follow the AtroposBaseEnv pattern for consistency
- Include appropriate error handling and validation
Support
For questions or issues with community environments:
- Check the individual environment's README first
- Open an issue in the main repository
- Tag the environment author if possible
These environments are community contributions and may have different maintenance levels and support compared to core Atropos environments.