# FILE_RESPONSIBILITIES.md - Hybrid Protocol File Ownership & Maintenance

## Purpose
Clear ownership and maintenance responsibilities ensure the Hybrid Protocol system remains organized, up-to-date, and effective.

## Core Principle
**Every file has an owner.** Owners are responsible for content quality, updates, and maintenance.

## File Inventory & Responsibilities

### Core Workflow Files

#### 1. INBOX.md
**Owner:** System (shared responsibility)
**Purpose:** Entry point for all new tasks
**Responsibilities:**
- Ensure all new entries follow format
- Validate required fields are present
- Maintain cleanliness (archive old/moved items)
- Update template if needed
- Backup: Weekly

**Update Frequency:** Continuous (as tasks arrive)
**Review Cycle:** Daily quick check, weekly cleanup

#### 2. OUTBOX.md
**Owner:** Rivet (primary), Task Owners (secondary)
**Purpose:** Holding area for completed tasks awaiting review
**Responsibilities:**
- Validate completion before moving from INBOX
- Ensure review readiness (all criteria met)
- Notify Rivet of pending reviews
- Archive approved tasks to STATUS.md
- Return rejected tasks to INBOX.md

**Update Frequency:** As tasks complete
**Review Cycle:** Daily by Rivet

#### 3. STATUS.md
**Owner:** System (automated), Rivet (quality)
**Purpose:** Archive of approved tasks and system status
**Responsibilities:**
- Maintain accurate archive of completed work
- Update system status metrics
- Generate performance reports
- Ensure data integrity
- Backup: Daily

**Update Frequency:** Daily (metrics), On approval (archive)
**Review Cycle:** Weekly metrics review

### Process Definition Files

#### 4. REVIEW_WORKFLOW.md
**Owner:** Rivet
**Purpose:** Defines review and approval process
**Responsibilities:**
- Keep process documentation current
- Update based on lessons learned
- Ensure consistency in application
- Train new reviewers
- Version control changes

**Update Frequency:** As process evolves (monthly review)
**Review Cycle:** Monthly with metrics analysis

#### 5. TASK_SIZING_RULES.md
**Owner:** All Participants (collective), Rivet (curator)
**Purpose:** Guidelines for task estimation
**Responsibilities:**
- Maintain sizing examples and guidelines
- Update based on historical data
- Calibrate team estimation skills
- Document estimation techniques
- Track accuracy metrics

**Update Frequency:** Quarterly, or when accuracy drops
**Review Cycle:** Monthly estimation review

#### 6. SELF_IMPROVEMENT_LOOP.md
**Owner:** System (facilitator), All Participants (contributors)
**Purpose:** Continuous improvement framework
**Responsibilities:**
- Facilitate improvement cycles
- Document lessons learned
- Track improvement initiatives
- Measure impact of changes
- Foster learning culture

**Update Frequency:** Weekly (lessons), Monthly (system)
**Review Cycle:** Weekly retrospective

### Knowledge Management Files

#### 7. SYSTEM-INTEL.md
**Owner:** System (aggregator), Rivet (analyst)
**Purpose:** Strategic insights and system intelligence
**Responsibilities:**
- Aggregate data from all tasks
- Identify patterns and trends
- Generate strategic insights
- Support decision making
- Historical analysis

**Update Frequency:** Monthly deep dive
**Review Cycle:** Quarterly strategic review

#### 8. LESSONS.md
**Owner:** All Participants (contributors), System (organizer)
**Purpose:** Tactical learnings and immediate insights
**Responsibilities:**
- Capture lessons from each task
- Organize by category and priority
- Make accessible for future reference
- Highlight recurring issues
- Support onboarding

**Update Frequency:** Daily (as lessons occur)
**Review Cycle:** Weekly retrospective

### Support Files

#### 9. FILE_RESPONSIBILITIES.md (this file)
**Owner:** System Administrator
**Purpose:** Defines file ownership and maintenance
**Responsibilities:**
- Keep ownership matrix current
- Update when roles change
- Ensure coverage for all files
- Document backup procedures
- Handle ownership disputes

**Update Frequency:** When roles change, quarterly review
**Review Cycle:** Quarterly

#### 10. PROTOCOL_UPDATES.md
**Owner:** System (change log), Rivet (approver)
**Purpose:** Track protocol changes and versions
**Responsibilities:**
- Document all protocol changes
- Version control
- Breaking change notifications
- Migration guidance
- Release notes

**Update Frequency:** On protocol change
**Review Cycle:** With each change

## Ownership Matrix

| File | Primary Owner | Backup Owner | Update Trigger | Review Frequency |
|------|---------------|--------------|----------------|------------------|
| INBOX.md | System | All Participants | New task | Daily |
| OUTBOX.md | Rivet | System | Task completion | Daily |
| STATUS.md | System | Rivet | Approval/metrics | Weekly |
| REVIEW_WORKFLOW.md | Rivet | System | Process change | Monthly |
| TASK_SIZING_RULES.md | All Participants | Rivet | Accuracy issue | Monthly |
| SELF_IMPROVEMENT_LOOP.md | System | All Participants | Retrospective | Weekly |
| SYSTEM-INTEL.md | System | Rivet | Monthly deep dive | Quarterly |
| LESSONS.md | All Participants | System | Lesson learned | Weekly |
| FILE_RESPONSIBILITIES.md | System Admin | Rivet | Role change | Quarterly |
| PROTOCOL_UPDATES.md | System | Rivet | Protocol change | Per change |

## Maintenance Procedures

### Daily Maintenance
1. **INBOX.md:** Quick format check, remove spam/duplicates
2. **OUTBOX.md:** Review notifications, check SLA compliance
3. **LESSONS.md:** Add any new lessons from completed tasks

### Weekly Maintenance
1. **STATUS.md:** Update metrics, clean up old data
2. **SELF_IMPROVEMENT_LOOP.md:** Facilitate retrospective
3. **LESSONS.md:** Organize and categorize weekly lessons
4. **All files:** Backup verification

### Monthly Maintenance
1. **REVIEW_WORKFLOW.md:** Review against metrics
2. **TASK_SIZING_RULES.md:** Update based on accuracy data
3. **SYSTEM-INTEL.md:** Monthly deep dive update
4. **All files:** Comprehensive review and cleanup

### Quarterly Maintenance
1. **FILE_RESPONSIBILITIES.md:** Ownership review
2. **All process files:** Strategic review
3. **System health:** Comprehensive audit
4. **Improvement assessment:** Measure impact of changes

## Backup Strategy

### Frequency:
- **Daily:** STATUS.md, INBOX.md, OUTBOX.md
- **Weekly:** All files
- **Monthly:** Complete system snapshot

### Location:
- Primary: /root/clawd/hybrid-protocol/
- Backup: /root/clawd/hybrid-protocol/backups/
- Archive: External storage (quarterly)

### Retention:
- Daily backups: 30 days
- Weekly backups: 90 days  
- Monthly snapshots: 1 year

## Quality Standards

### For All Files:
- Consistent formatting
- Clear, concise language
- Up-to-date information
- Proper version control
- Accessibility (readable by all participants)

### For Process Files:
- Actionable guidance
- Examples and templates
- Metrics and measurement
- Continuous improvement hooks

### For Knowledge Files:
- Organized structure
- Searchable content
- Practical insights
- Historical context

## Ownership Transfer Process

### When ownership needs to change:
1. Current owner identifies need for transfer
2. Document reason for transfer
3. Identify suitable new owner
4. Knowledge transfer session
5. Update FILE_RESPONSIBILITIES.md
6. Announce change to all participants

### Success criteria for transfer:
- New owner understands responsibilities
- Historical context transferred
- Quality standards maintained
- No disruption to workflow

## Emergency Procedures

### If owner unavailable:
1. Backup owner takes temporary responsibility
2. Document temporary assumption of duties
3. Handle critical maintenance only
4. Notify system administrator
5. Plan for permanent solution

### If file corrupted:
1. Restore from most recent backup
2. Document incident in LESSONS.md
3. Identify root cause
4. Implement preventive measures
5. Update backup procedures if needed

## Getting Help

### For file-specific questions:
- Check file owner in this document
- Review file history and comments
- Consult LESSONS.md for related insights

### For process questions:
- Refer to REVIEW_WORKFLOW.md
- Check SYSTEM-INTEL.md for patterns
- Ask Rivet for clarification

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

---

## Quick Reference

### Your Responsibilities:
1. **As Task Owner:** Update INBOX/OUTBOX, contribute to LESSONS.md
2. **As Reviewer (Rivet):** Maintain OUTBOX.md, REVIEW_WORKFLOW.md
3. **As Participant:** Contribute to LESSONS.md, follow processes
4. **As System:** Maintain STATUS.md, SYSTEM-INTEL.md, backups

### Maintenance Checklist:
- [ ] Daily: Check INBOX/OUTBOX format
- [ ] Weekly: Update metrics, retrospective
- [ ] Monthly: Process review, deep dive
- [ ] Quarterly: System audit, ownership review

### Quality Checklist:
- [ ] Format consistent?
- [ ] Content current?
- [ ] Examples relevant?
- [ ] Metrics accurate?
- [ ] Backups current?

**Remember:** Well-maintained files = effective system. Your attention to these responsibilities keeps everything running smoothly.