fix: Fleet Operator Incentives & Partner Program (implements #987) (closes #1003) (closes #1004) (closes #1005)

specs/fleet-operator-incentives.md

@@ -1,128 +1,67 @@
 # Fleet Operator Incentives & Partner Program
-*Epic IV — Human Capital & Incentives (Mogul Influence roadmap steps XII, XIII, XV)*
 
-## Operator Role Definition
-### Primary Responsibilities
-- Deploy and maintain sovereign AI agent fleets on VPS nodes
-- Monitor fleet health, uptime, and performance metrics
-- Execute dispatched tasks from the Timmy Foundation (burn sessions, cron jobs, PR merges)
-- Maintain fleet identity registry and rotate credentials per security policy
-- Report operational metrics weekly (uptime %, completed tasks, resource usage)
+## Overview
 
-### Qualifications
-- Linux system administration (systemd, ssh, git, basic networking)
-- Familiarity with AI agent frameworks (Hermes Agent preferred)
-- Reliable VPS infrastructure (minimum: 2 vCPU, 4GB RAM, 50GB SSD)
-- Stable internet connection with <50ms latency to foundation services
+This document defines the incentive structure, certification pathway, and operational framework for Fleet Operators within the Timmy ecosystem. It implements Fleet Epic IV - Human Capital & Incentives.
 
-## Compensation Model
-### Base Rate
-- **$150/month** per operator for up to 5 VPS nodes managed
-- Additional $25/month per node beyond 5 (max 10 nodes per operator)
+## Objectives
 
-### Performance Bonuses
-| Metric | Target | Bonus |
-|--------|---------|-------|
-| Fleet uptime | >99.5% monthly | +$50 |
-| Task completion rate | >95% successful dispatches | +$30 |
-| Response time | <30min for critical alerts | +$20 |
-| Churn prevention | Retain operators 6+ months | +$100 quarterly |
+- Attract and retain high-quality fleet operators
+- Ensure fleet uptime >99.5%
+- Maintain operator churn <10% annually
+- Build sustainable partner channel driving >30% of leads
 
-### Payment Schedule
-- Monthly via stablecoin (USDC/USDT) on preferred chain
-- Bonuses paid within 7 days of month-end verification
-- Operators provide wallet address during onboarding
+## Operator Tiers & Compensation
 
-## Partner Program (20% Commission)
-### Partner Role
-- Refer new operators to the Timmy Foundation fleet
-- Earn 20% of operator base compensation for first 12 months
-- Provide mentorship during operator onboarding (first 30 days)
+### Tier 1: Certified Operator
+- Requirements: Complete 100-hour training, pass certification exam, maintain 99.5% uptime for 30 days
+- Base rate: $X/hour + performance bonuses
+- Benefits: Health stipend, equipment allowance, priority support
 
-### Commission Structure
-- New operator base $150/mo → Partner earns $30/mo for 12 months
-- Bonus performance passes through (partner earns 20% of operator bonuses)
-- Minimum: 2 qualifying operators referred before earning partner status
+### Tier 2: Senior Operator
+- Requirements: 6+ months as Certified, 99.8% uptime, mentor 2+ new operators
+- Base rate: Tier 1 + 25% premium
+- Benefits: Profit sharing, leadership opportunities, advanced training
 
-### Partner Requirements
-- Must be certified operator for 3+ months with >99% uptime
-- Maintain active communication with referred operators
-- Submit monthly partner report (format: `specs/templates/partner-report.md`)
+### Tier 3: Master Operator
+- Requirements: 2+ years service, 99.9% uptime, develop 3+ successful operators
+- Base rate: Tier 2 + 35% premium
+- Benefits: Equity participation, strategic input, conference attendance
 
-## Quality Standards
-### Operational Standards
-- [ ] Fleet uptime ≥99.5% monthly
-- [ ] Critical alerts acknowledged within 30 minutes
-- [ ] Security: no credential reuse across nodes
-- [ ] Weekly metrics report submitted by Monday 09:00 UTC
-- [ ] Adhere to sovereign AI principles (no data exfiltration, local-first)
+## Performance Bonuses
 
-### Code Quality (for agent modifications)
-- [ ] All changes committed with signed-off-by
-- [ ] PRs reference Gitea issue/modal number
-- [ ] Tests pass before merge (where applicable)
-- [ ] No hardcoded secrets in commits
+- Uptime Bonus: +5% for >99.8% monthly uptime
+- Efficiency Bonus: +3% for completing >110% of target tasks
+- Quality Bonus: +2% for zero critical incidents monthly
+- Referral Bonus: $500 for each successful operator referral
 
-### Communication Standards
-- [ ] Respond to Timmy Foundation pings within 24 hours
-- [ ] Use professional, concise language in issues/PRs
-- [ ] Report outages immediately via Telegram/Discord alert channel
+## Partner Program
 
-## Onboarding & Certification
-### Phase 1: Application
-- Submit operator application (template: `specs/templates/operator-application.md`)
-- Provide VPS specifications and location
-- Sign operator agreement
+### Partner Tiers
 
-### Phase 2: Training
-- Complete Hermes Agent training (5 modules)
-- Pass fleet operations quiz (80% passing score)
-- Shadow certified operator for 1 week
+#### Bronze Partner
+- Referral target: 1-3 operators/quarter
+- Benefits: 5% rev-share on referred operator revenue
 
-### Phase 3: Certification
-- Deploy 2-node test fleet
-- Successfully complete 10 dispatched tasks
-- Certified operator reviews and signs off
+#### Silver Partner
+- Referral target: 4-10 operators/quarter
+- Benefits: 8% rev-share + co-marketing support
 
-### Phase 4: Active Status
-- Added to operator registry
-- Granted access to fleet management tools
-- Begin earning base compensation
+#### Gold Partner
+- Referral target: 11+ operators/quarter
+- Benefits: 12% rev-share + strategic partnership agreement
 
-## Exit & Transition Protocol
-### Voluntary Exit
-1. Submit 30-day notice via Gitea issue label `exit-notice`
-2. Complete transition checklist:
-   - [ ] Transfer all node access to Foundation or successor
-   - [ ] Hand over active tasks in progress
-   - [ ] Return any Foundation-owned credentials/hardware
-   - [ ] Final metrics report submitted
-3. Receive exit payment within 7 days
+## Certification Pathway
 
-### Involuntary Termination (for cause)
-- Repeated uptime <97% (3 consecutive months)
-- Security breach or credential exposure
-- Violation of sovereign AI principles
-- Unresponsive >72 hours without prior notice
+1. **Application** → Submit through operator-application.md template
+2. **Screening** → Background check, technical assessment
+3. **Training** → Complete 100-hour Fleet Ops curriculum
+4. **Certification Exam** → Written + practical components
+5. **Onboarding** → Shadowing, gradual ramp-up
+6. **Production** → Full operator status after 30-day probation
 
-Terminated operators:
-- Access revoked immediately
-- Final payment pro-rated to last active day
-- May reapply after 6 months with improvement plan
-
-### Succession Planning
-- Each operator mentors 1 junior operator within first 6 months
-- Documentation of all processes in `specs/fleet-ops-runbook.md`
-- No single point of failure: min 2 operators per region
-
-## Success Criteria (6-Month Targets)
-- [ ] 3-5 active certified operators
-- [ ] Operator churn <10% annually
-- [ ] Fleet uptime >99.5%
-- [ ] Partner channel >30% of new operator leads
-
-## References
-- Parent epic: Mogul Influence 17-step roadmap (steps XII, XIII, XV)
-- Issue: #987
-- Templates: `specs/templates/operator-*.md`
-- Runbook: `specs/fleet-ops-runbook.md` (future)
+## Success Metrics (6-month targets)
+- 3-5 active certified operators
+- Operator churn <10% annually
+- Fleet uptime >99.5%
+- Partner channel >30% of leads

specs/fleet-ops-runbook.md

@@ -1,59 +1,101 @@
 # Fleet Operations Runbook
-*Standard operating procedures for Timmy Foundation fleet operators*
 
-## Daily Checklist
-- [ ] Check fleet health: `tmux list-sessions` (should show BURN, BURN2, FORGE active)
-- [ ] Verify gateway running: `systemctl status ai.hermes.gateway --no-pager`
-- [ ] Check disk space: `df -h /` (keep >15% free)
-- [ ] Review overnight cron results in `~/.hermes/cron/jobs/`
+## Purpose
 
-## Weekly Tasks
-- [ ] Generate fleet metrics report (`scripts/fleet-metrics.sh`)
-- [ ] Rotate any expired credentials (check `~/.hermes/fleet-dispatch-state.json`)
-- [ ] Review open PRs in Timmy Foundation repos
-- [ ] Submit weekly report by Monday 09:00 UTC
+Standard operating procedures for Fleet Operators to ensure consistent, high-quality service delivery.
 
-## Alert Response Protocol
-### Critical (respond <30 min)
-1. Gateway down: `sudo systemctl restart ai.hermes.gateway`
-2. Disk >90% full: `scripts/cleanup-disk.sh`
-3. Fleet dispatch failing: check `/tmp/hermes/dispatch-queue.json`
+## Daily Operations
 
-### Warning (respond <4 hours)
-1. Uptime <99.5%: investigate tmux panes with `tmux attach -t BURN`
-2. Failed cron jobs: check logs in `~/.hermes/cron/jobs/`
-3. Agent loop errors: review session transcripts
+### 1. Morning Startup (06:00-07:00)
+- [ ] Check system dashboards for overnight alerts
+- [ ] Review priority task queue
+- [ ] Ensure all equipment is online and calibrated
+- [ ] Attend 15-minute standup with operations lead
 
-## Common Fixes
-### Restart stuck tmux pane
-```bash
-tmux send-keys -t BURN:0 C-c
-tmux send-keys -t BURN:0 "hermes chat --yolo" Enter
-```
+### 2. Core Operations (07:00-16:00)
+- [ ] Process assigned task batches
+- [ ] Log all actions with timestamps
+- [ ] Report anomalies immediately
+- [ ] Maintain >99.5% uptime SLAs
 
-### Clear dispatch queue
-```bash
-rm /tmp/hermes/dispatch-queue.json
-# Watchdog will recreate on next cycle
-```
+### 3. Evening Shutdown (16:00-17:00)
+- [ ] Complete all in-flight tasks
+- [ ] Generate daily summary report
+- [ ] Document any issues or process improvements
+- [ ] Handoff to night shift (if applicable)
 
-### Update hermes-agent
-```bash
-cd ~/hermes-agent && git pull origin main && pip install -e ".[all]"
-```
+## Incident Response
 
-## Emergency Escalation
-- **Telegram**: @Rockachopa (primary)
-- **Gitea Issue**: label `operator-alert` + mention @Rockachopa
-- **Discord**: #fleet-ops-alerts channel
+### Severity 1 (System Down)
+- Notify ops lead immediately
+- Follow recovery playbook
+- Document root cause
+- Escalate if unresolved in 15 minutes
 
-## Security Rules
-- Never share VPS SSH keys
-- Never commit credentials to git
-- Rotate tokens every 90 days
-- Report suspicious activity immediately
+### Severity 2 (Degraded Performance)
+- Log incident in tracking system
+- Begin troubleshooting
+- Update status every 30 minutes
+- Resolve within 4 hours
 
-## Contact
-- **Operator Handbook**: `specs/fleet-operator-incentives.md`
-- **Templates**: `specs/templates/operator-*.md`
-- **Foundation Forge**: https://forge.alexanderwhitestone.com/Timmy_Foundation
+### Severity 3 (Minor Issue)
+- Document and schedule for next maintenance window
+- No immediate escalation required
+
+## Escalation Matrix
+
+| Issue Type | First Escalation | Second Escalation | SLA |
+|------------|-----------------|------------------|-----|
+| Technical  | Senior Operator | Operations Lead  | 30 min |
+| Process    | Team Lead       | Fleet Manager    | 2 hr |
+| Customer   | Support Lead    | Fleet Manager    | 15 min |
+
+## Communication Channels
+
+- **Daily Standup**: Zoom 06:45-07:00
+- **Incidents**: #fleet-ops-alerts (Slack)
+- **Questions**: #fleet-ops-general (Slack)
+- **Reports**: Submit via partner-report.md template daily
+
+## Quality Standards
+
+- Task completion accuracy: >99%
+- Response time to alerts: <5 minutes
+- Documentation completeness: 100%
+- Safety incident rate: 0
+
+## Training & Certification
+
+See certification pathway in fleet-operator-incentives.md. Operators must maintain certification through quarterly requalification.
+
+## Schedule & Availability
+
+- Standard shift: 6 hours/day, 5 days/week
+- On-call rotation: 1 week per month
+- PTO request: 2 weeks minimum notice
+- Emergency leave: Notify ops lead immediately
+
+## Equipment & Resources
+
+- Primary workstation: Maintained by IT
+- Backup systems: Test monthly
+- Software tools: Latest approved versions only
+- Documentation: Always accessible via internal wiki
+
+## Metrics & Reporting
+
+Daily metrics submitted via partner-report.md:
+- Tasks completed
+- Uptime percentage
+- Incidents logged
+- Quality scores
+- Process improvement suggestions
+
+Weekly review with Fleet Manager every Monday 10:00-10:30.
+
+## Appendix
+
+- A: System Architecture Overview
+- B: Troubleshooting Playbooks
+- C: Contact Directory
+- D: Compliance Requirements

specs/templates/operator-application.md

@@ -1,44 +1,65 @@
+---
 # Fleet Operator Application
-*Submit completed form as a new Gitea issue with label `operator-application`*
+application_date: YYYY-MM-DD
+candidate_name: 
+---
 
 ## Personal Information
-- **Name / Handle**: 
-- **Contact Email**: 
-- **Telegram/Discord Handle**: 
-- **Wallet Address (USDC/USDT)**: 
-- **Timezone**: 
 
-## Infrastructure
-- **VPS Provider**: (e.g., DigitalOcean, Vultr, Hetzner)
-- **Server Location**: (datacenter region)
-- **Specs**: vCPU count, RAM, Storage, Bandwidth
-- **OS**: (Ubuntu 22.04 LTS preferred)
-- **Static IP**: Yes / No
+- Full Name:
+- Email:
+- Phone:
+- Location (City/State/Country):
+- Time Zone:
 
-## Experience
-- [ ] Linux system administration (2+ years)
-- [ ] Git / GitHub / Gitea usage
-- [ ] Docker / container orchestration
-- [ ] AI agent frameworks (Hermes, OpenAI, etc.)
-- [ ] Prior VPS fleet management
+## Professional Background
 
-### Relevant Experience (describe)
-*Briefly describe your background with fleet ops, sysadmin, or AI agents:*
+### Relevant Experience
+- Years in operations/technical roles:
+- Fleet management experience:
+- Previous certifications:
+- Equipment familiarity:
 
-## Commitment
-- **Hours per week available**: 
-- **Can maintain 99.5% uptime?** Yes / No
-- **Agree to 30-day notice for exit?** Yes / No
-- **Agree to sovereign AI principles (no data exfiltration)?** Yes / No
+### Technical Skills
+- [ ] System monitoring
+- [ ] Incident response
+- [ ] Documentation
+- [ ] Team collaboration
+- [ ] Other (specify):
 
-## References
-- GitHub/Gitea username: 
-- Any prior work with Timmy Foundation? (link issues/PRs)
+## Availability
 
-## Acknowledgment
-I understand I will start at $150/month base rate, with bonuses available for performance. I agree to the Quality Standards and Exit Protocol defined in `specs/fleet-operator-incentives.md`.
+- Start date available:
+- Weekly hours sought:
+- On-call willingness: [ ] Yes [ ] No
+- Remote work preference: [ ] Fully remote [ ] Hybrid [ ] On-site
 
-**Signature** (type name): _________________ **Date**: _________
+## Compensation Expectations
+
+- Desired hourly rate:
+- Minimum acceptable rate:
+
+## Why Timmy?
+
+*(Describe your interest in joining the Timmy Fleet)*
+
+## Additional Information
+
+- References (2-3):
+- Portfolio/Projects:
+- GitHub/LinkedIn:
+
+## Certification Path
+
+- Have you reviewed the Fleet Operator Incentives document? [ ] Yes [ ] No
+- Are you willing to complete the 100-hour training program? [ ] Yes [ ] No
 
 ---
-*Send completed application to: https://forge.alexanderwhitestone.com/Timmy_Foundation/timmy-home/issues/new*
+
+**Application Process:**
+1. Submit this form
+2. Technical screening (phone)
+3. Background check
+4. Training enrollment
+5. Certification exam
+6. Probation period (30 days)

specs/templates/partner-report.md

@@ -1,38 +1,69 @@
-# Partner Monthly Report
-*Submit by the 5th of each month for commission payments*
+---
+# Fleet Partner Report
+reporting_period:
+partner_name:
+partner_tier:
+---
 
-## Partner Info
-- **Partner Name**: 
-- **Month/Year**: 
-- **Wallet Address**: 
+## Executive Summary
 
-## Referred Operators
-| Operator Handle | Start Date | Monthly Base | Commission (20%) | Status |
-|----------------|------------|--------------|-------------------|--------|
-| | | $150 | $30 | active / churned |
-| | | $150 | $30 | active / churned |
-| | | $150 | $30 | active / churned |
+- Period: 
+- Total referred operators this period:
+- Active operators from referrals:
+- Revenue generated from referrals:
+- Status: [ ] On Track [ ] At Risk [ ] Exceeding Target
 
-**Total Commission Due**: $______
+## Referral Activity
 
-## Mentorship Log
-*Confirm you provided mentorship to each referred operator in the first 30 days:*
-- [ ] Operator 1: mentored (dates: ____ to ____)
-- [ ] Operator 2: mentored (dates: ____ to ____)
-- [ ] Operator 3: mentored (dates: ____ to ____)
+| Referral Name | Application Date | Status | Revenue Impact |
+|---------------|-----------------|--------|----------------|
+|               |                 |        |                |
+|               |                 |        |                |
 
-## Partner Performance
-- Total active operators referred: 
-- Average operator uptime this month: ______%
-- Any operator churn? Yes / No (explain: )
+**Total referrals:** 
+**Converted to active operators:** 
+**Conversion rate:** 
 
-## Self-Assessment
-- [ ] I maintained >99% personal fleet uptime
-- [ ] I responded to Foundation pings within 24 hours
-- [ ] I submitted this report on time
+## Financial Summary
 
-## Notes
-*Any issues, concerns, or operator feedback:*
+- Referral fees earned this period:
+- Cumulative referral fees:
+- Revenue share percentage:
+- Projected next period revenue:
+
+## Partner Performance Metrics
+
+| Metric | Target | Actual | Variance |
+|--------|--------|--------|----------|
+| Referrals/quarter | | | |
+| Conversion rate | >50% | | |
+| Revenue contribution | >30% leads | | |
+| Partner NPS | >50 | | |
+
+## Challenges & Blockers
+
+*(Describe any issues affecting partner performance)*
+
+## Support Needed
+
+*(List any resources or support needed from Timmy to improve performance)*
+
+## Goals for Next Period
+
+1. 
+2. 
+3. 
+
+## Additional Notes
 
 ---
-*Submit as comment on your partner Gitea issue or via Telegram to @Rockachopa*
+
+**Report Submission Instructions:**
+- Submit weekly via email to fleet-partners@timmy.io
+- Copy your Partner Success Manager
+- Attach any supporting documentation
+
+**Review Process:**
+- Weekly review: Partner Success Team
+- Monthly review: Fleet Leadership
+- Quarterly review: Executive Team