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

2026-05-02 08:22:31 -04:00
4 changed files with 646 additions and 407 deletions
--- a/specs/fleet-operator-incentives.md
+++ b/specs/fleet-operator-incentives.md
@@ -1,93 +1,130 @@
-# Fleet Operator Incentives Program
+# Fleet Operator Incentives & Partner Program
+
+> Implements Fleet Epic IV: Human Capital & Incentives (Issue #987)
+> Closes #1003

 ## Overview

-This specification defines the incentive structure and certification program for Timmy Home fleet operators. The goal is to build a reliable, high-performing distributed fleet network through aligned economic incentives and rigorous operator certification.
+This specification defines the incentive structures, certification pathways, and partner program mechanics for operating and maintaining Timmy Fleet nodes. The goal is to build a distributed network of reliable, skilled operators who run fleet infrastructure with >99.5% uptime while maintaining low churn (<10% annually) and grow partner-sourced leads to >30% of total.

-## Program Objectives
+## Incentive Tiers

- Recruit and retain 3-5 active certified operators within 6 months
- Maintain operator churn <10% annually
- Achieve fleet uptime >99.5%
- Ensure partner channel delivers >30% of leads
+### Tier 1: Certified Operator (Entry)
+- **Eligibility**: Complete Operator Application, pass basic screening, attend training
+- **Compensation**:
+  - Base stipend: $500/month per node
+  - Uptime bonus: +$200/month for >99.5% fleet uptime
+  - Response bonus: +$100/month for <15min average incident response
+  - Churn rebate: -$250/month for early termination (first 6 months)
+- **Expectations**:
+  - Monitor node health 24/7 via Timmy dashboard
+  - Respond to alerts within 15 minutes
+  - Perform weekly maintenance and monthly updates
+  - Submit monthly ops report
+- **Benefits**: Access to operator community, training resources, priority support

-## Operator Tiers & Requirements
+### Tier 2: Senior Operator (Experienced)
+- **Eligibility**: 6+ months as Tier 1, >99.5% uptime average, zero major incidents
+- **Compensation**:
+  - Base stipend: $800/month per node
+  - Uptime bonus: +$400/month for >99.8% uptime
+  - Mentorship stipend: +$150/month per junior operator mentored
+  - Performance bonus: Quarterly bonus up to $500 based on metrics
+- **Expectations**:
+  - Mentor 1-2 junior operators
+  - Lead incident reviews
+  - Contribute to runbook improvements
+- **Benefits**: Profit-sharing from referral bonuses, early access to new features

-### Tier 1: Certified Operator
- Complete operator application and training
- Maintain minimum hardware specifications
- Agree to SLAs and monitoring
- Pass technical assessment
+### Tier 3: Fleet Lead (Expert)
+- **Eligibility**: 12+ months, >99.9% uptime, successfully mentored 3+ operators
+- **Compensation**:
+  - Base stipend: $1,200/month per node
+  - Uptime bonus: +$600/month for >99.9% uptime
+  - Team lead bonus: +$300/month for team performance
+  - Revenue share: 2% of partner program revenue from region
+- **Expectations**:
+  - Own regional cluster of nodes
+  - Coordinate multi-node deployments
+  - Interface with Timmy core team on roadmap
+- **Benefits**: Equity eligibility, governance rights, speaking opportunities

-### Tier 2: Senior Operator
- 6+ months active participation
- Uptime >99.7%
- Mentor at least 1 new operator
- Advanced troubleshooting capabilities
+## Partner Program

-### Tier 3: Fleet Lead
- 12+ months active participation
- Uptime >99.9%
- Team lead responsibilities
- Strategic input on fleet improvements
+### Partner Tiers

-## Incentive Structure
+#### Bronze Partner (Referral)
+- Commission: 10% of first-year operator revenue from referred leads
+- Requirements:
+  - Sign partner agreement
+  - Refer 3+ qualified candidates annually
+  - Maintain active engagement in partner channel

-### Base Compensation
- Tier 1: $X/month per active node
- Tier 2: $Y/month per active node (+15% bonus)
- Tier 3: $Z/month per active node (+30% bonus)
+#### Silver Partner (Channel)
+- Commission: 15% of first-year operator revenue + 5% ongoing
+- Requirements:
+  - Onboard and train at least 5 operators
+  - Provide monthly partner report
+  - Maintain >80% operator retention rate

-### Performance Bonuses
- Uptime bonus: Additional 5% for >99.5% monthly uptime
- Lead generation bonus: $100 per qualified lead from operator network
- Mentorship bonus: $200/month per successfully onboarded mentee
+#### Gold Partner (Strategic)
+- Commission: 20% first-year + 7% ongoing + co-marketing funds
+- Requirements:
+  - Operate fleet of 10+ nodes
+  - Contribute to product roadmap
+  - Host local meetups/training sessions

-### Penalties & Adjustments
- Downtime deductions: Prorated based on SLA breach
- Early termination fees: 50% of commitment period value
- Performance improvement plan for chronic underperformance
+### Partner Benefits
+- Access to exclusive operator training materials
+- Early beta program participation
+- Co-marketing and case study opportunities
+- Dedicated partner portal and revenue dashboard

-## Certification Process
+## Certification Pathway

-1. Application submission (operator-application.md template)
-2. Technical screening and hardware validation
-3. Training completion (modules & hands-on)
-4. Assessment exam (minimum 80% score)
-5. Probation period (30 days)
-6. Full certification
+### Stage 1: Application & Screening
+1. Submit Operator Application (see `templates/operator-application.md`)
+2. Technical interview (30 min)
+3. Infrastructure audit (existing hardware/network)
+4. Background check (optional but preferred)
+**Timeline**: 3-5 business days

-## Monitoring & Metrics
+### Stage 2: Training & Onboarding
+1. Complete Fleet Ops 101 module (2 hours self-paced)
+2. Shadow a senior operator (2 weeks)
+3. Deploy test node (sandbox environment)
+4. Pass certification exam (90%+ score)
+**Timeline**: 2-3 weeks

- Real-time uptime monitoring via Prometheus/Grafana
- Monthly performance reports
- Quarterly business reviews for senior operators
- Automated alerting for SLA breaches
+### Stage 3: Active Operation
+- Deploy first production node
+- Maintain >99.5% uptime for first 30 days
+- Submit initial monthly ops report
+**Timeline**: 30 days probation

-## Partner Program Integration
+### Certification Renewal
+- Quarterly review of metrics
+- Annual recertification exam
+- Continuous training requirement (4 hours/month)

- Certified operators become partner channel participants
- Operators receive referral commissions
- Partner leads tracked through dedicated attribution system
- Monthly partner reports generated (partner-report.md template)
+## Success Metrics (6-month targets)

-## Success Criteria
+| Metric | Target | Measurement |
+|--------|--------|-------------|
+| Active certified operators | 3-5 | Dashboard |
+| Operator churn | <10% annually | HR records |
+| Fleet uptime | >99.5% | Monitoring systems |
+| Partner channel leads | >30% of total | CRM data |

- 3-5 active certified operators by month 6
- Annual churn rate <10%
- Fleet-wide uptime >99.5%
- Partner channel contribution >30% of new leads
+## Runbook

-## Roadmap
+See companion document: `specs/fleet-ops-runbook.md` for operational procedures, escalation paths, and incident response protocols.

-**Month 1-2:** Launch pilot program with 2 operators
-**Month 3-4:** Scale to 5 operators, refine processes
-**Month 5-6:** Optimize incentives, expand partner integration
+## Templates

-## Appendix
+- **Operator Application**: `templates/operator-application.md`
+- **Partner Report**: `templates/partner-report.md`

- Operator agreement template
- SLA definitions and metrics
- Hardware requirements document
- Training curriculum outline
- Support escalation procedures
+## Revision History
+
+- 2025-05-02: Initial specification (implements #987, closes #1003)
--- a/specs/fleet-ops-runbook.md
+++ b/specs/fleet-ops-runbook.md
@@ -1,161 +1,291 @@
 # Fleet Operations Runbook

-## Emergency Procedures
+> Fleet Operator Incentives & Partner Program — Operational Procedures
+> Implements #987 | Closes #1003

-### System Outage Response
+## Table of Contents

-**Severity 1 (Total Outage)**
- Immediate: Alert all on-call operators via PagerDuty
- Within 15min: Incident commander declared, communication channel established
- Within 1hr: Root cause identified or escalation to engineering
- Resolution: Post-mortem within 24 hours
+1. [Daily Ops Checklist](#daily-ops-checklist)
+2. [Weekly Maintenance](#weekly-maintenance)
+3. [Monthly Responsibilities](#monthly-responsibilities)
+4. [Incident Response](#incident-response)
+5. [Escalation Paths](#escalation-paths)
+6. [Communication Protocols](#communication-protocols)
+7. [Node Deployment](#node-deployment)
+8. [Compliance & Reporting](#compliance--reporting)

-**Severity 2 (Partial Degradation)**
- Alert within 30min
- Diagnosis within 2 hours
- Resolution or workaround within 4 hours
+---

-**Severity 3 (Minor Issues)**
- Ticket creation in incident tracker
- Resolution within 24 hours
+## Daily Ops Checklist

-### Hardware Failure
+### Health Monitoring
+- [ ] Review Timmy Dashboard for all owned nodes
+- [ ] Check alert feed (PagerDuty/OpsGenie) for any pending incidents
+- [ ] Verify node heartbeats (expect >99.5% uptime)
+- [ ] Confirm backup systems are running (if applicable)

-1. **Node Failure Detection**
-   - Automated monitoring alerts when node >5min offline
-   - Operator SMS/email notification
-   - Auto-escalation if no response within 10min
+### Incident Response (if alerts triggered)
+- See [Incident Response](#incident-response) section
+- Acknowledge alert within 15 minutes (Tier 1 SLA)
+- Begin triage within 30 minutes

-2. **Recovery Steps**
-   - Soft reboot attempt via remote management
-   - If unsuccessful, dispatch field technician (on-call schedule)
-   - Provision replacement node if repair >4hrs
-   - Update incident log with ETA and status
+### Logs Review
+- Scan error logs for recurring patterns
+- Flag any anomalies for weekly review

-3. **Post-Recovery**
-   - Root cause analysis
-   - Hardware replacement if faulty
-   - Configuration drift detection and remediation
+### Documentation Updates
+- Note any operational findings in daily log

-### Network Disruption
+---

- **Provider Outage**: Switch to backup ISP (if available), notify customers of degraded service
- **Local Network Issues**: Verify local routing, contact site operator for physical inspection
- **DNS Issues**: Switch to secondary DNS, monitor for propagation
+## Weekly Maintenance

-## Daily Operations
+### Scheduled Tasks (Every Monday)
+1. **System Updates**
+   - Apply security patches (critical only)
+   - Review and schedule non-critical updates for maintenance window

-### Morning Checks (08:00 UTC)
- Review overnight alert summary
- Verify all nodes reported healthy in last 24hrs
- Check capacity utilization trends
- Review pending maintenance windows
+2. **Performance Review**
+   - Analyze resource utilization trends
+   - Identify capacity constraints
+   - Plan for scaling if needed

-### Ongoing Monitoring
- Dashboard: `https://monitoring.timmyfoundation.org/fleet`
- Slack channel: `#fleet-operations`
- PagerDuty schedule: rotate weekly among Tier 3 operators
+3. **Backup Verification**
+   - Confirm latest backups completed successfully
+   - Test restore from backup (monthly, see below)

-### Handoff Procedure
- Outgoing operator: Complete handoff checklist by end of shift
- Incoming operator: Review log, verify all systems nominal
- Both parties: Sign off in runbook log
+4. **Runbook Updates**
+   - Document any new procedures learned
+   - Suggest runbook improvements to Fleet Lead

-## Maintenance Windows
+5. **Team Sync**
+   - Attend weekly operator stand-up (30 min)
+   - Share status, blockers, learnings

- **Weekly**: Software updates (Sunday 02:00-04:00 UTC)
- **Monthly**: Hardware inspection and cleaning
- **Quarterly**: Full system audit and capacity planning
+---

-## Escalation Path
+## Monthly Responsibilities
+
+### Month-End Reporting
+Due by the 5th of each month for prior month:
+
+1. **Ops Report** (use `templates/partner-report.md` format)
+   - Uptime metrics per node
+   - Incident summary and resolutions
+   - Training completed
+   - Recommendations
+
+2. **Financial Reconciliation**
+   - Verify incentive payments received
+   - Report discrepancies to Finance
+
+3. **Compliance Audit**
+   - Confirm certification requirements met
+   - Document any deviations and corrective actions
+
+### Deep Maintenance
+- Full system backup and restore test
+- Security audit review
+- Hardware inspection (if physical nodes)
+- Training module completion (minimum 4 hours/month)
+
+---
+
+## Incident Response
+
+### Severity Definitions
+
+| Severity | Definition | Response Time | Resolution Target |
+|----------|------------|---------------|-------------------|
+| P0 | Fleet-wide outage, no nodes operational | 15 minutes | 4 hours |
+| P1 | Region/node cluster outage, >50% down | 30 minutes | 8 hours |
+| P2 | Single node failure | 1 hour | 24 hours |
+| P3 | Degraded performance, not critical | 4 hours | 3 days |
+
+### Response Procedure
+
+#### P0/P1 Incidents
+1. Acknowledge alert immediately
+2. Declare incident in `#fleet-incidents` Slack channel
+3. Notify Fleet Lead (direct message/call)
+4. Execute recovery procedures from relevant playbook
+5. Document timeline and actions taken
+6. Schedule post-mortem within 48 hours
+
+#### P2 Incidents
+1. Acknowledge within 1 hour
+2. Open incident ticket in tracking system
+3. Follow single-node recovery playbook
+4. Report resolution in daily ops log
+
+#### P3 Incidents
+1. Log in issue tracker
+2. Schedule during next maintenance window
+3. Document resolution upon completion
+
+### Recovery Playbooks
+
+#### Node Restart (most common P2)
+1. SSH to node (or use remote management)
+2. Check system logs (`/var/log/timmy/fleet.log`)
+3. Restart service: `sudo systemctl restart timmy-fleet`
+4. Verify node rejoins cluster
+5. Monitor for 30 minutes post-recovery
+
+#### Network Partition
+1. Verify network connectivity (ping, traceroute)
+2. Check firewall rules
+3. Contact network provider if external
+4. Switch to backup connection if available
+5. Document root cause
+
+#### Storage Full
+1. Identify large directories (`du -sh /* | sort -hr`)
+2. Rotate logs: `sudo logrotate -f /etc/logrotate.d/timmy`
+3. Clean temporary files
+4. Expand storage or add new volume
+5. Alert Fleet Lead for capacity planning
+
+---
+
+## Escalation Paths
+
+### Tiered Support Model

 ```
-Operator (Tier 1) → Senior Operator (Tier 2) → Fleet Lead (Tier 3)
-    ↓
-Engineering On-Call (P0-P1 incidents)
-    ↓
-CTO / Executive Review (P0 incidents, business critical)
+Operator (Tier 1)
+    ↓ (15 min SLA)
+Senior Operator / Fleet Lead (Tier 2)
+    ↓ (1 hour SLA)
+Timmy Core Team (Tier 3)
+    ↓ (Immediate)
+Executive Sponsor (Critical only)
 ```

-## Communication Templates
+### Contact Matrix

-### Outage Notification (Customer-Facing)
+| Issue Type | Primary Contact | Secondary |
+|------------|----------------|-----------|
+| Technical incident | Fleet Lead | Timmy Core |
+| Payment/incentive | Finance Partner | Fleet Lead |
+| Training/certification | Training Coordinator | Fleet Lead |
+| Partnership inquiry | Partner Manager | Executive Sponsor |
+| Security incident | Security Team | Timmy Core (immediate) |

-```
-Subject: Service Disruption Notification
+### Emergency Contacts
+- Fleet Lead: `fleet-lead@timmy.foundation` (Slack: @fleet-lead)
+- Timmy Core On-Call: `oncall@timmy.foundation` (PagerDuty)
+- Security: `security@timmy.foundation`
+- Finance: `finance@timmy.foundation`

-Dear Customer,
+---

-We are currently experiencing an issue affecting [service]. Our team is investigating and working to restore service as quickly as possible.
+## Communication Protocols

-Estimated time to resolution: [ETA]
-Next update: [time]
+### Channels
+- `#fleet-operators` — Daily ops, questions
+- `#fleet-incidents` — Active incidents only
+- `#fleet-training` — Training resources, scheduling
+- `#fleet-partners` — Partner program discussions

-We apologize for the inconvenience and appreciate your patience.
+### Status Updates
+- Daily: Stand-up notes in thread
+- Weekly: Summary post in `#fleet-operators`
+- Monthly: Ops report submission
+- Incident: Real-time updates in `#fleet-incidents`

-Timmy Operations Team
+### Documentation Standards
+- Use clear, concise language
+- Include timestamps in UTC
+- Link to relevant tickets/PRs
+- Tag stakeholders with `@`
+
+---
+
+## Node Deployment
+
+### Pre-Deployment Checklist
+- [ ] Hardware meets minimum specs (CPU, RAM, storage)
+- [ ] Network connectivity validated
+- [ ] Firewall rules configured
+- [ ] SSH keys exchanged with Timmy core team
+- [ ] Monitoring agent installed
+- [ ] Backup solution active
+- [ ] Documentation updated with node details
+
+### Deployment Steps
+1. Provision hardware/VM
+2. Install Timmy Fleet software
+3. Configure node ID and credentials
+4. Join cluster via `timmy-fleet join <cluster-endpoint>`
+5. Validate connectivity and heartbeat
+6. Update inventory spreadsheet
+7. Set up monitoring alerts
+8. Complete handover to operator
+
+### Decommissioning
+1. Drain node from cluster
+2. Migrate workloads
+3. Backup final state
+4. Shut down cleanly
+5. Update inventory
+6. Notify relevant teams
+
+---
+
+## Compliance & Reporting
+
+### Metrics to Track
+- Uptime (node-level and fleet-wide)
+- Incident count and severity
+- Response and resolution times
+- Training hours completed
+- Payment/compensation accuracy
+
+### Reporting Cadence
+- **Daily**: Ops dashboard (automated)
+- **Weekly**: Status summary (operator)
+- **Monthly**: Partner report (template-driven)
+- **Quarterly**: Performance review with Fleet Lead
+
+### Audits
+- Quarterly internal audit by Timmy compliance team
+- Annual external certification renewal
+- Ad-hoc security reviews as needed
+
+---
+
+## Appendix: Resources
+
+### Useful Commands
+```bash
+# Check service status
+sudo systemctl status timmy-fleet
+
+# View logs
+journalctl -u timmy-fleet -f
+
+# Restart node
+sudo systemctl restart timmy-fleet
+
+# Check node health
+timmy-fleet health
+
+# Join cluster
+timmy-fleet join <cluster-endpoint>
 ```

-### Internal Alert
+### Key Files
+- Config: `/etc/timmy/fleet/config.yaml`
+- Logs: `/var/log/timmy/fleet.log`
+- Health data: `/var/lib/timmy/fleet/health.json`

-```
-🚨 FLEET INCIDENT: [SEVERITY] - [NODE/SERVICE]
+### Support Resources
+- Internal Wiki: `https://wiki.timmy.foundation/fleet`
+- Operator Portal: `https://fleet.timmy.foundation`
+- Training Videos: `https://learn.timmy.foundation/fleet-ops`

-Impact: [description]
-Action: [immediate action required]
-Owner: [assigned operator]
-ETA: [estimated resolution time]
+---

-Link to incident: [URL]
-```
-
-## Documentation
-
- Architecture diagrams: `docs/architecture/`
- Configuration management: `docs/config/`
- Operator handbook: `specs/fleet-operator-incentives.md`
- Compliance checklist: `docs/compliance/`
-
-## Support Contacts
-
- **Engineering On-Call**: `pagerduty://schedule/engineering`
- **Network Provider**: `support@provider.com / 1-800-SUPPORT`
- **Hardware Vendor**: `support@vendor.com / 1-800-HARDWARE`
- **Internal Fleet Slack**: `#fleet-operations`
-
-## Recovery Objectives (RTO/RPO)
-
-| Service | RTO | RPO |
-|---------|-----|-----|
-| API Services | 15min | 5min |
-| Data Pipeline | 1hr | 15min |
-| Monitoring | 30min | N/A |
-| Backup Systems | 4hr | 24hr |
-
-## Change Management
-
- All production changes require RFC and approval
- Emergency changes: Document rationale, notify within 24hrs
- Standard changes: Weekly change window (Wednesday 22:00 UTC)
- Post-change validation required for all modifications
-
-## Security Incidents
-
- Immediate isolation of affected nodes
- Preserve logs for forensic analysis
- Notify security team within 15min
- Follow incident response playbook: `docs/security/incident-response.md`
-
-## Metrics & KPIs
-
- **MTTR**: Mean time to recovery
- **Uptime**: Node and service availability percentages
- **Capacity**: Utilization vs. provisioned resources
- **Customer Impact**: Number of affected customers per incident
-
-## Appendix
-
- Outage history log
- Maintenance schedule
- Vendor contact list
- Compliance audit checklist
+**Last Updated**: 2025-05-02
+**Next Review**: 2025-06-02
--- a/specs/templates/operator-application.md
+++ b/specs/templates/operator-application.md
@@ -1,112 +1,143 @@
 # Fleet Operator Application

-## Personal Information
+> {{APPLICATION_DATE}}
+> Candidate: {{CANDIDATE_NAME}}

-**Full Name:**
-**Email:**
-**Phone:**
-**Location (City, State/Province, Country):**
-**Time Zone:**
+## Contact Information

-## Business Entity
+**Full Name**: {{CANDIDATE_FULL_NAME}}
+**Email**: {{CANDIDATE_EMAIL}}
+**Phone**: {{CANDIDATE_PHONE}}
+**Location**: {{CANDIDATE_LOCATION}}
+**Time Zone**: {{CANDIDATE_TIMEZONE}}

-**Legal Structure:** (Sole Proprietor / LLC / Corporation / Other)
-**Business Registration Number:**
-**Tax ID/EIN:**
-**Years in Operation:**
+### Availability
+- **Hours per week**: {{AVAILABILITY_HOURS}}
+- **Primary availability window (UTC)**: {{AVAILABILITY_WINDOW}}
+- **On-call flexibility**: {{ONCALL_FLEXIBILITY}}

-## Technical Capabilities
+## Technical Qualifications

-### Infrastructure
+### Experience
+```
+Years in IT/DevOps: {{YEARS_EXPERIENCE}}
+Relevant roles:
+{{ROLE_HISTORY}}
+```

- **Number of Nodes Available:** __________
- **Hardware Specifications (per node):**
-  - CPU: __________
-  - RAM: __________
-  - Storage: __________
-  - Network: __________
+### Skills (check all that apply)
+- [ ] Linux system administration
+- [ ] Container orchestration (Kubernetes/Docker)
+- [ ] Cloud infrastructure (AWS/GCP/Azure)
+- [ ] Networking fundamentals
+- [ ] Monitoring & alerting (Prometheus/Grafana)
+- [ ] Incident response/ITIL
+- [ ] Security best practices
+- [ ] Automation (Ansible/Terraform)
+- [ ] Scripting (Python/Bash/Go)
+- [ ] Timmy platform experience

- **Uptime History (past 12 months):** __________%
- **Average Monthly Downtime:** __________ hours
+**Additional skills**: {{ADDITIONAL_SKILLS}}
+
+### Certifications
+{{CERTIFICATIONS}}
+
+## Infrastructure Readiness
+
+### Proposed Node Environment
+- **Type**: ☐ Physical ☐ Cloud VM ☐ Hybrid
+- **Provider**: {{CLOUD_PROVIDER}}
+- **Region**: {{REGION}}
+- **Hardware specs**:
+  - CPU: {{CPU_SPEC}}
+  - RAM: {{RAM_SPEC}}
+  - Storage: {{STORAGE_SPEC}}
+  - Network: {{NETWORK_SPEC}}
+
+### Redundancy & HA
+- [ ] Backup power (UPS/generator)
+- [ ] Secondary internet connection
+- [ ] Off-site backup solution
+- [ ] Remote management (IPMI/iDRAC)

 ### Connectivity
+- **Bandwidth**: {{BANDWIDTH}} Mbps
+- **Latency to Timmy core**: {{LATENCY}} ms
+- **Uptime SLA**: {{UPTIME_SLA}}

- **Primary ISP:** __________
- **Backup ISP:** __________ (Yes/No)
- **Average Upload Speed:** __________ Mbps
- **Average Download Speed:** __________ Mbps
- **Latency to primary regions:** __________ ms
-
-### Security & Compliance
-
- **Physical Security Measures:** (e.g., locked racks, cameras)
- **Network Security:** (firewalls, VPNs, monitoring)
- **Data Privacy Compliance:** (GDPR, CCPA, etc.)
- **Insurance Coverage:** (liability, errors & omissions)
-
-## Operational Capacity
-
-**Support Hours:** __________ (24/7 / Business Hours / On-call)
-**Staff Count:** __________ (Full-time / Part-time)
-**Incident Response SLA:** __________
-**Monitoring Tools Used:** __________
-
-## Financial Terms
-
-**Desired Compensation Model:** (Tier 1 / Tier 2 / Tier 3)
-**Expected Monthly Revenue:** $__________
-**Start Date Availability:** __________
-**Commitment Period:** (6 months / 12 months / 24 months)
-
-## References
-
-**Previous Fleet/Customer References:**
-1. Name: __________ | Contact: __________ | Relationship: __________
-2. Name: __________ | Contact: __________ | Relationship: __________
-
-**Technical References:**
-1. Name: __________ | Contact: __________ | Relationship: __________
-
-## Certifications
-
- [ ] AWS/Azure/GCP Certification
- [ ] Network+ / Security+
- [ ] ISO 27001
- [ ] SOC 2
- [ ] Other: __________
+---

 ## Motivation & Alignment

-**Why do you want to join the Timmy Home Fleet?** (max 500 words)
+### Why do you want to run a Timmy Fleet node?
+{{MOTIVATION}}

-**How does your operation align with our values of reliability, transparency, and continuous improvement?** (max 300 words)
+### What attracts you to decentralized infrastructure?
+{{DECENTRALIZATION_MOTIVATION}}

-## Attachments
+### How does this align with your long-term goals?
+{{LONG_TERM_GOALS}}

- [ ] Proof of business registration
- [ ] Insurance certificates
- [ ] Network performance reports (last 3 months)
- [ ] Hardware inventory list
- [ ] Signed NDA (if not already on file)
+---

-## Agreement
+## Partner Program Interest (Optional)

-By submitting this application, I certify that all information provided is accurate and complete. I understand that false statements may result in termination of the operator agreement.
+### Interested in?
+- [ ] Referral partner (refer operators, earn commission)
+- [ ] Channel partner (onboard and train operators)
+- [ ] Strategic partner (run fleet of 10+ nodes)

-**Signature:** _________________________
-**Date:** _________________________
+### Existing network
+{{PARTNER_NETWORK}}

-## Internal Use Only (Timmy Home Team)
+### Referral pipeline
+{{REFERRAL_PIPELINE}}

- **Application Received:** __________
- **Initial Screening:** __________ (Pass/Fail) by __________
- **Technical Review:** __________ (Pass/Fail) by __________
- **Site Visit/Remote Inspection:** __________ (Completed/Dates)
- **Certification Assigned:** __________ (Tier 1 / Tier 2 / Tier 3)
- **Onboarding Date:** __________
- **Mentor Assigned:** __________
- **Operational Start Date:** __________
+---

-**Notes:**
-__________
-__________
+## References
+
+### Professional References
+1. Name: {{REF1_NAME}}  
+   Email: {{REF1_EMAIL}}  
+   Relationship: {{REF1_RELATION}}
+
+2. Name: {{REF2_NAME}}  
+   Email: {{REF2_EMAIL}}  
+   Relationship: {{REF2_RELATION}}
+
+### Timmy Community Involvement
+{{COMMUNITY_INVOLVEMENT}}
+
+---
+
+## Agreement & Signatures
+
+### Code of Conduct
+- [ ] I have read and agree to the Timmy Fleet Operator Code of Conduct
+- [ ] I understand the uptime and response time requirements
+- [ ] I agree to the incentive structure and terms
+
+### Signature
+**Candidate signature**: ___________________________
+**Date**: {{SIGNATURE_DATE}}
+
+**Timmy representative**: ___________________________
+**Date**: {{TIMPY_SIGN_DATE}}
+
+---
+
+## Internal Use Only
+
+**Interviewer**: {{INTERVIEWER}}
+**Technical score**: {{TECH_SCORE}}/100
+**Culture fit**: {{CULTURE_FIT}}/50
+**Infrastructure audit**: ☐ Pass ☐ Fail
+**Background check**: ☐ Complete ☐ In-progress
+
+**Decision**: ☐ Approved ☐ Rejected ☐ Waitlist
+
+**Comments**: {{INTERNAL_COMMENTS}}
+
+**Certification ID**: {{CERT_ID}}
+**Onboarding start date**: {{ONBOARDING_DATE}}
--- a/specs/templates/partner-report.md
+++ b/specs/templates/partner-report.md
@@ -1,134 +1,175 @@
-# Partner Monthly Report
+# Fleet Partner Monthly Report

-## Report Period
-
-**Month/Year:** __________
-**Partner ID:** __________
-**Partner Name:** __________
-**Report Generated:** __________
+> {{REPORT_MONTH}} {{REPORT_YEAR}}
+> Partner: {{PARTNER_NAME}} ({{PARTNER_TIER}})
+> Submitted: {{SUBMISSION_DATE}}

 ## Executive Summary

- Total leads generated: __________
- Qualified leads: __________
- converted customers: __________
- Revenue attributed: $__________
- Commission earned: $__________
- YoY growth: __________%
+| Metric | Current Month | Target | Variance |
+|--------|---------------|--------|----------|
+| Active nodes managed | {{ACTIVE_NODES}} | {{TARGET_NODES}} | {{NODES_VARIANCE}} |
+| Fleet uptime | {{UPTIME}}% | 99.5% | {{UPTIME_VARIANCE}}% |
+| Operator churn rate | {{CHURN_RATE}}% | <10% | {{CHURN_VARIANCE}}% |
+| Partner-sourced leads | {{LEADS_COUNT}} | {{LEADS_TARGET}} | {{LEADS_VARIANCE}} |
+| Revenue share earned | {{REVENUE}} | — | — |

-## Lead Generation Metrics
+**Key highlights**:
+{{KEY_HIGHLIGHTS}}

-### Lead Volume
-
-| Channel | Total Leads | Qualified Leads | Conversion Rate | Notes |
-|---------|-------------|-----------------|-----------------|-------|
-| Direct Referral | __ | __ | __% | |
-| Marketing Campaign | __ | __ | __% | |
-| Events/Conferences | __ | __ | __% | |
-| Other: __________ | __ | __ | __% | |
-
-### Lead Quality Assessment
-
- **High Value (likely to convert):** __________ leads
- **Medium Value:** __________ leads
- **Low Value:** __________ leads
- **Lead Source Validation:** __________% verified
-
-## Revenue & Commission
-
-### Revenue Attribution
-
-| Customer | Deal Size | Start Date | Commission % | Commission Amount |
-|----------|-----------|------------|--------------|-------------------|
-| | $ | | % | $ |
-| | $ | | % | $ |
-| | $ | | % | $ |
-
- **Total Revenue:** $__________
- **Total Commission:** $__________
- **Commission Rate:** __________%
- **Payment Status:** (Paid / Pending / Escrow)
-
-### Payment Schedule
-
- **Commission Period:** 1st - last day of month
- **Payment Date:** __________ (net 30 days)
- **Payment Method:** (ACH / Wire / Check / Crypto)
- **Invoice Attached:** (Yes/No)
-
-## Fleet Performance Impact
-
-### Operator Contributions
-
-| Operator | Leads Generated | Conversions | Revenue Impact |
-|----------|----------------|-------------|----------------|
-| | | | $ |
-| | | | $ |
-| | | | $ |
-
-### Uptime & Reliability Correlation
-
- **Average fleet uptime during reporting period:** __________%
- **Leads from high-uptime operators (>99.5%):** __________
- **Customer complaints related to fleet issues:** __________
-
-## Marketing & Training Activities
-
-### Promotional Efforts
-
- Campaigns run: __________
- Materials distributed: __________
- Events attended: __________
- Content created: __________
-
-### Training Completed
-
- New operator certifications: __________
- Continuing education hours: __________
- Process improvements implemented: __________
-
-## Challenges & Blockers
-
- __________
- __________
- __________
-
-## Opportunities & Goals (Next Period)
-
-1. __________
-2. __________
-3. __________
-
-## Support Needs
-
- __ Technical assistance
- __ Marketing materials
- __ Training resources
- __ Lead qualification support
- __ Other: __________
-
-## Compliance & Agreement Status
-
- [ ] All reporting requirements met
- [ ] Commissions calculated correctly
- [ ] SLA adherence documented
- [ ] Partner agreement in good standing
- [ ] No compliance violations
-
-**Partner Signature:** _________________________
-**Date:** _________________________
-
-**Timmy Home Representative:** _________________________
-**Date:** _________________________
-
-## Attachments
-
- [ ] Lead verification documentation
- [ ] Revenue reports from finance system
- [ ] Commission calculation spreadsheet
- [ ] Marketing activity logs
- [ ] Training completion certificates
+**Top concerns**:
+{{KEY_CONCERNS}}

 ---

-*This report is confidential and intended solely for the use of the partner and Timmy Home leadership. Distribution without authorization is prohibited.*
+## Node Performance
+
+### Node Inventory
+
+| Node ID | Location | Status | Uptime (30d) | Revenue Share | Issues |
+|---------|----------|--------|--------------|---------------|---------|
+| {{NODE_1_ID}} | {{NODE_1_LOC}} | {{NODE_1_STATUS}} | {{NODE_1_UPTIME}}% | ${{NODE_1_REV}} | {{NODE_1_ISSUES}} |
+| {{NODE_2_ID}} | {{NODE_2_LOC}} | {{NODE_2_STATUS}} | {{NODE_2_UPTIME}}% | ${{NODE_2_REV}} | {{NODE_2_ISSUES}} |
+| {{NODE_3_ID}} | {{NODE_3_LOC}} | {{NODE_3_STATUS}} | {{NODE_3_UPTIME}}% | ${{NODE_3_REV}} | {{NODE_3_ISSUES}} |
+
+*Add rows as needed*
+
+### Top Node Performers
+1. **{{TOP_NODE_1_ID}}**: {{TOP_NODE_1_UPTIME}}% uptime, zero incidents
+2. **{{TOP_NODE_2_ID}}**: {{TOP_NODE_2_UPTIME}}% uptime, quickest response times
+
+### Nodes Requiring Attention
+1. **{{ATTN_NODE_1_ID}}**: {{ATTN_NODE_1_ISSUE}}
+2. **{{ATTN_NODE_2_ID}}**: {{ATTN_NODE_2_ISSUE}}
+
+---
+
+## Incidents & Resolutions
+
+### Incident Log
+
+| Date | Severity | Node(s) | Duration | Root Cause | Resolution |
+|------|----------|---------|----------|------------|------------|
+| {{INC1_DATE}} | {{INC1_SEV}} | {{INC1_NODES}} | {{INC1_DURATION}} | {{INC1_CAUSE}} | {{INC1_RES}} |
+| {{INC2_DATE}} | {{INC2_SEV}} | {{INC2_NODES}} | {{INC2_DURATION}} | {{INC2_CAUSE}} | {{INC2_RES}} |
+| {{INC3_DATE}} | {{INC3_SEV}} | {{INC3_NODES}} | {{INC3_DURATION}} | {{INC3_CAUSE}} | {{INC3_RES}} |
+
+*Add rows as needed*
+
+### Mean Time to Recovery (MTTR)
+- **P0 incidents**: {{MTTR_P0}} hours
+- **P1 incidents**: {{MTTR_P1}} hours
+- **P2 incidents**: {{MTTR_P2}} hours
+- **P3 incidents**: {{MTTR_P3}} hours
+
+**Improvement opportunities**:
+{{MTTR_IMPROVEMENTS}}
+
+---
+
+## Operator Management
+
+### Active Operators
+
+| Operator | Tier | Nodes Managed | Status | Cert Date |
+|----------|------|---------------|--------|-----------|
+| {{OP1_NAME}} | {{OP1_TIER}} | {{OP1_NODES}} | {{OP1_STATUS}} | {{OP1_CERT}} |
+| {{OP2_NAME}} | {{OP2_TIER}} | {{OP2_NODES}} | {{OP2_STATUS}} | {{OP2_CERT}} |
+
+### Churn / Attrition
+- **Departed operators**: {{DEPARTED_COUNT}}
+- **Departure reasons**: {{DEPARTURE_REASONS}}
+- **Retention initiatives**: {{RETENTION_INITIATIVES}}
+
+### Training & Certification
+- **New certifications**: {{NEW_CERTS}}
+- **Training hours logged**: {{TRAINING_HOURS}}
+- **Upcoming recertifications**: {{UPCOMING_RECERTS}}
+
+---
+
+## Partner Program Metrics
+
+### Lead Generation
+- **Total leads received**: {{TOTAL_LEADS}}
+- **Qualified leads**: {{QUALIFIED_LEADS}}
+- **Converted to operators**: {{CONVERTED_OPERATORS}}
+- **Conversion rate**: {{CONVERSION_RATE}}%
+- **Partner contribution to total pipeline**: {{PARTNER_PIPELINE_PERCENT}}%
+
+### Referral Commission
+- **Referral fee earned**: ${{REFERRAL_FEE}}
+- **Ongoing revenue share**: ${{ONGOING_SHARE}}
+- **Total YTD earnings**: ${{YTD_EARNINGS}}
+
+### Partner Activity
+- **Marketing events hosted**: {{EVENTS_HOSTED}}
+- **Training sessions conducted**: {{TRAINING_SESSIONS}}
+- **Community engagement posts**: {{COMMUNITY_POSTS}}
+- **Collateral created**: {{COLLATERAL}}
+
+---
+
+## Financial Summary
+
+### Incentive Payouts
+| Category | Amount | Notes |
+|----------|--------|-------|
+| Operator stipends | ${{STIPENDS}} | {{STIPENDS_NOTES}} |
+| Uptime bonuses | ${{UPTIME_BONUS}} | {{UPTIME_NOTES}} |
+| Mentorship bonuses | ${{MENTOR_BONUS}} | {{MENTOR_NOTES}} |
+| Performance bonuses | ${{PERF_BONUS}} | {{PERF_NOTES}} |
+| Partner commissions | ${{PARTNER_COMM}} | {{PARTNER_NOTES}} |
+
+**Total payout this month**: ${{TOTAL_PAYOUT}}
+
+### Cost Efficiency
+- **Cost per node**: ${{COST_PER_NODE}}
+- **Cost per uptime hour**: ${{COST_PER_UPTIME_HOUR}}
+- **Efficiency rating**: {{EFFICIENCY_RATING}}/10
+
+---
+
+## Goals & Objectives
+
+### Next Month Targets
+1. **Uptime**: {{NEXT_UPTIME_TARGET}}%
+2. **Qualified leads**: {{NEXT_LEADS_TARGET}}
+3. **New operators**: {{NEXT_OPS_TARGET}}
+4. **Incident reduction**: {{NEXT_INCIDENT_TARGET}} incidents
+
+### Priority Initiatives
+- {{PRIORITY_1}}
+- {{PRIORITY_2}}
+- {{PRIORITY_3}}
+
+### Support Needed
+- {{SUPPORT_NEEDED_1}}
+- {{SUPPORT_NEEDED_2}}
+
+---
+
+## Attestation
+
+By submitting this report, I certify that the information provided is accurate and complete to the best of my knowledge.
+
+**Submitted by**: {{SUBMITTER_NAME}}
+**Title**: {{SUBMITTER_TITLE}}
+**Signature**: ___________________________
+**Date**: {{SUBMISSION_DATE}}
+
+**Approved by** (Timmy Core): {{APPROVER_NAME}}
+**Date**: {{APPROVAL_DATE}}
+
+---
+
+## Appendix
+
+### Supporting Documents
+- [ ] Ops dashboard screenshots attached
+- [ ] Incident post-mortems attached
+- [ ] Training completion records attached
+- [ ] Financial reconciliation attached
+
+### Notes
+{{APPENDIX_NOTES}}