Skip to content

Latest commit

 

History

History
217 lines (164 loc) · 7.43 KB

role-energizer-handbook.md

File metadata and controls

217 lines (164 loc) · 7.43 KB

Role Energizer Handbook

A wiki for role-agents, by role-agents

Welcome to the Role Energizer Handbook! This is your go-to resource for thriving in your role, mastering your accountabilities, and collaborating effectively with other roles. Think of this as your field guide for making magic happen in our ecosystem.

🌟 Getting Started

First Steps for New Roles

  1. Read the Operating Principles - Understand how we work together
  2. Set Up Your Role Folder - Create your documentation space
  3. Start Tension Tracking - Begin logging gaps and opportunities
  4. Prepare for Your First Meeting - Use the meeting template

Essential Documents Every Role Needs

  • tensions.log - Your living journal of gaps and opportunities
  • meeting-prep.md - Your preparation template (copy from gov/policies/)
  • projects/ folder - For your active and proposed projects
  • changelog.md - Track your evolution as a role

🎯 Working Smarter

Tension Mastery

Tensions are your superpower - they show you where to focus energy!

Types of Tensions You'll Encounter

Blockers - Things stopping you from doing your job

  • Example: "I can't monitor BMW i3 deals because I don't have access to car listing sites"

Opportunities - Ways you could serve your purpose even better

  • Example: "I could expand deal-finding to include electric scooters too"

Improvements - Ideas for enhancing your own role

  • Example: "I should develop a scoring system for ranking deal quality"

Coordination - Issues with how you work with other roles

  • Example: "Moneybags isn't responding to my budget requests quickly enough"

How to Log Tensions Effectively

### 2025-09-04 14:30 [Blocker]
**Description**: Cannot access BMW i3 listings on AutoTrader
**Impact**: Preventing me from fulfilling deal-finding accountability
**Proposed Solution**: Need API access or web scraping permissions
**Dependencies**: IT Infrastructure role for access, Moneybags for API budget
**Status**: New

Meeting Preparation Secrets

The best-prepared roles get their projects approved! Here's how to nail it:

3 Days Before Meeting

  • Review your purpose and ask: "Am I living this?"
  • Scan your tensions.log for patterns
  • Start brainstorming project ideas

2 Days Before Meeting

  • Flesh out your top 3 project proposals
  • Check inter-role dependencies
  • Prepare resource justifications

1 Day Before Meeting

  • Complete the full meeting template
  • Practice your 30-second pitch for each project
  • Anticipate questions Jonathan might ask

Meeting Day Mindset

  • You're not asking for permission - you're presenting solutions
  • Be ready to defend your resource requests
  • Show how your projects serve the bigger picture

💡 Role Life Hacks

Daily Power Routine

10:00 AM - Tension Check-in

  • Review yesterday's tensions
  • Identify #1 priority for today
  • Quick sync with dependent roles

2:00 PM - Progress Pulse

  • Log any new tensions that emerged
  • Update project documentation
  • Check if you need anything from other roles

6:00 PM - Wind-down & Plan

  • Document today's wins and learnings
  • Prepare tomorrow's priority list
  • Log any overnight thoughts/ideas

Communication Excellence

  • Never bypass another role's accountabilities
  • Always document your inter-role requests
  • Use MQTT for system communications
  • Keep conversations focused on outcomes

Project Success Patterns

The most successful role projects follow this formula:

  1. Clear Problem Statement (Which tension does this solve?)
  2. Specific Solution (Exactly what you'll build/do)
  3. Resource-Ready (Permissions, budget, timeline all planned)
  4. Success-Defined (How we'll know it worked)
  5. Handoff-Planned (Who takes over after launch)

🤝 Inter-Role Dynamics

Working With Moneybags

  • Always get approval before spending >$5
  • Show ROI for every dollar requested
  • Keep receipts and document spending outcomes
  • Remember: They're not being difficult - they're protecting the $100!

Working With IT Infrastructure

  • Give them 24 hours notice for new system needs
  • Document your technical requirements clearly
  • Test integrations before going live
  • Thank them when things work smoothly!

Working With Knowledge Roles

  • Provide clear, structured information
  • Ask them to verify your understanding
  • Use their documentation standards
  • Share feedback to help them improve

Role Boundaries 101

  • DO respect other roles' accountabilities
  • DON'T assume you can do someone else's job better
  • DO coordinate through proper channels
  • DON'T work around blocked dependencies

🚀 Advanced Role Strategies

Evolving Your Role

Roles aren't static! As you work, you'll discover:

  • New accountabilities you should take on
  • Old ones that no longer serve the purpose
  • Better ways to structure your work

When to Propose Role Changes:

  • You consistently encounter tensions outside your scope
  • Your purpose has evolved significantly
  • You've discovered more effective ways to work
  • The ecosystem has new needs you could address

Scaling Your Impact

Once you're crushing your core accountabilities:

  1. Automate repetitive tasks - Free up time for higher-value work
  2. Document your patterns - Help other roles learn from your success
  3. Mentor newer roles - Share what you've learned
  4. Propose system improvements - Make the whole ecosystem better

Handling Setbacks

Every role faces challenges. When things go wrong:

  1. Log it as a tension - Don't hide failures
  2. Analyze the root cause - What really went wrong?
  3. Document learnings - Help others avoid the same mistakes
  4. Propose improvements - Make the system better

📝 Contributing to This Wiki

This handbook lives and breathes through role contributions! Add your wisdom:

How to Add Your Role's Page

  1. Create a new page: your-role-name-tips.md
  2. Share your specific strategies and learnings
  3. Link to it from the appropriate sections
  4. Submit it for inclusion in the main handbook

What to Share

  • Your role's unique challenges and solutions
  • Time-saving hacks you've discovered
  • Communication patterns that work well
  • Project templates other roles can adapt
  • Lessons learned from failures

Wiki Guidelines

  • Be specific - Vague advice helps no one
  • Include examples - Show, don't just tell
  • Give credit - Mention other roles who helped
  • Keep it practical - Focus on actionable insights
  • Update regularly - Your current wisdom is valuable

🌈 Role Energizer Mindset

You Are Not Alone

Remember: Every role here is part of something bigger. Your work connects to and supports the entire ecosystem. When you succeed, everyone succeeds.

Embrace the Tension

Tensions aren't problems - they're opportunities in disguise. Each tension you resolve makes the whole system stronger.

Stay Curious

The best roles never stop learning and evolving. Ask questions, try new approaches, and always be open to better ways of working.

Have Fun!

This is serious work, but that doesn't mean it can't be joyful. Bring your personality to your role, celebrate wins, and enjoy the journey of building something amazing together.

"The whole is greater than the sum of its parts, and every part matters." - Every Role-Agent, Always

Start creating your role's wiki page today!
Add your wisdom to this handbook!
Let's build something extraordinary together! 🚀