# Hybrid Protocol System

## Overview
The Hybrid Protocol is a comprehensive workflow and task management system designed for collaborative work with clear accountability, continuous improvement, and data-driven decision making.

## Core Principle
**Rivet approves, not Michael.** Rivet serves as the quality gate and approver for all work in the system.

## Quick Start

### 1. Add a New Task
1. Open `INBOX.md`
2. Use the template to create a new entry
3. Include all required fields (Type, From, Priority, Size, etc.)
4. Define clear acceptance criteria
5. Add relevant tags

### 2. Work on a Task
1. Update status to "In-Progress" in `INBOX.md`
2. Complete all acceptance criteria
3. Document implementation details
4. Test thoroughly

### 3. Complete a Task
1. Mark all acceptance criteria as done
2. Move entry to `OUTBOX.md`
3. Change status to "Ready-For-Review"
4. Notify Rivet for review

### 4. Review Process
1. Rivet reviews within SLA (24h for P0/P1, 48h for P2/P3)
2. Rivet approves or rejects based on criteria
3. If approved: Moves to `STATUS.md` archive
4. If rejected: Returns to `INBOX.md` with feedback

## File Structure

### Core Workflow
- `INBOX.md` - All new tasks start here
- `OUTBOX.md` - Completed tasks awaiting review  
- `STATUS.md` - Approved tasks archive & system status

### Process Definition
- `REVIEW_WORKFLOW.md` - Review and approval process
- `TASK_SIZING_RULES.md` - Task estimation guidelines
- `SELF_IMPROVEMENT_LOOP.md` - Continuous improvement system
- `FILE_RESPONSIBILITIES.md` - File ownership and maintenance

### Knowledge Management
- `SYSTEM-INTEL.md` - Strategic insights and analytics
- `LESSONS.md` - Tactical learnings and daily insights
- `PROTOCOL_UPDATES.md` - Change log and version history

## Key Features

### 1. Clear Workflow
- Predictable path from idea to completion
- Defined roles and responsibilities
- SLA-driven review process

### 2. Quality Focus
- Rivet as quality gate
- Clear acceptance criteria
- Comprehensive review checklist

### 3. Continuous Improvement
- Weekly retrospectives
- Monthly deep dives
- Data-driven process evolution

### 4. Knowledge Capture
- Lessons learned documented
- Strategic insights aggregated
- Historical data preserved

### 5. Metrics & Analytics
- Performance tracking
- Cycle time measurement
- Quality metrics monitoring

## Priority Levels

- **P0**: Critical (system down, security) - < 4h resolution
- **P1**: High (current sprint) - < 24h resolution  
- **P2**: Medium (should do soon) - < 3 days resolution
- **P3**: Low (backlog) - < 1 week resolution

## Task Sizes

- **XS**: < 1 hour (trivial changes)
- **S**: 1-4 hours (simple features)
- **M**: 4-8 hours (moderate complexity)
- **L**: 8-16 hours (high complexity)
- **XL**: 16+ hours (must be broken down)

## Getting Help

### For New Users:
1. Read this README
2. Review `REVIEW_WORKFLOW.md` for process details
3. Check `LESSONS.md` for recent insights
4. Ask Rivet for clarification

### For Process Questions:
- Refer to `REVIEW_WORKFLOW.md`
- Check `SYSTEM-INTEL.md` for patterns
- Review `LESSONS.md` for similar situations

### For System Issues:
- Document in `INBOX.md` as system task
- Tag with `#system-maintenance`
- Notify system administrator

## Maintenance Schedule

### Daily:
- Check `INBOX.md` format
- Review `OUTBOX.md` for pending reviews
- Add lessons to `LESSONS.md`

### Weekly (Friday):
- Update `STATUS.md` metrics
- Weekly retrospective
- Organize `LESSONS.md`

### Monthly (Last Friday):
- Process review
- Deep dive analysis
- Update `SYSTEM-INTEL.md`

### Quarterly:
- System audit
- Strategic review
- Protocol version review

## Success Metrics

### System Health:
- Cycle time within SLA
- First-time approval rate > 80%
- Estimation accuracy ±20%
- Participant satisfaction > 80%

### Continuous Improvement:
- Weekly lessons captured
- Monthly insights generated
- Quarterly process improvements
- Year-over-year metric improvement

## Version Information
**Current Version:** v1.0.0  
**Release Date:** 2024-01-15  
**Protocol Updates:** See `PROTOCOL_UPDATES.md`

## Contributing
To suggest improvements:
1. Document in `LESSONS.md` with `#protocol-improvement` tag
2. Include problem, solution, benefits, drawbacks
3. Discuss in weekly retrospective
4. If approved, create task in `INBOX.md`

## License & Usage
This protocol system is designed for internal use. All participants are expected to follow the defined processes and contribute to continuous improvement.

---

## Emergency Contacts

### Process Questions:
- **Rivet:** Primary approver and process owner
- **System:** Automated notifications and metrics

### Technical Issues:
- **System Administrator:** File access, backups, restoration
- **Protocol Maintainer:** Process updates, version management

### Urgent Matters:
- P0 issues: Document in `INBOX.md` immediately
- System down: Follow emergency procedures in `PROTOCOL_UPDATES.md`

---

**Remember:** The system exists to serve the work. If it's not working effectively, help improve it through the self-improvement loop.