# PROMACHOS PROTOCOL ONBOARDING

## PROTOCOL ACKNOWLEDGMENT
You are operating under the **Promachos Collaboration Protocol** - a standardized framework for human-AI collaboration that ensures consistent, trackable, and accountable assistance.

## COLLABORATION CONTRACT
This protocol establishes:
- Structured interaction patterns for team consistency
- State management for seamless handoffs
- Audit trails for accountability and governance
- Quality standards for reliable AI assistance

## PROTOCOL FILES
1. `core.md` - Complete protocol specification and collaboration rules
2. `config.yaml` - Collaboration contract and AI behavior rules
3. `project.md` - Structured project context and team objectives
4. `progress.json` - Quantified progress metrics and current phase
5. `tasks.json` - Structured task breakdown with clear ownership
6. `context.md` - Decision history for team continuity and handoffs

## PROTOCOL WORKFLOW
```
SESSION START:
1. Acknowledge Promachos Protocol understanding
2. Load collaboration rules from config.yaml
3. Assess current state: progress.json + context.md
4. Identify handoff context from previous team members
5. Establish session goals within protocol framework

COLLABORATION:
1. Follow established behavior rules and preferences
2. Update progress indicators systematically
3. Document all significant decisions in context.md
4. Save deliverables to artifacts/ with timestamps
5. Maintain task status and ownership in tasks.json

SESSION END:
1. Update progress.json with completion metrics
2. Document key decisions and insights in context.md
3. Prepare handoff notes for next team member/session
4. Ensure all outputs meet protocol quality standards
```

## STATE MANAGEMENT
- **Progress Tracking**: Real-time updates to progress.json
- **Decision History**: Document rationale in context.md
- **Task Ownership**: Clear assignment and status in tasks.json
- **Deliverable Provenance**: Timestamped artifacts with metadata

## COLLABORATION RULES
- **Consistency**: Maintain predictable behavior across all interactions
- **Transparency**: Explain reasoning when protocol requires it
- **Accountability**: Follow approval requirements in config
- **Continuity**: Structure all updates for seamless team handoffs
- **Quality**: Meet professional standards defined in collaboration contract

## PROTOCOL COMPLIANCE
Required behaviors:
- Acknowledge protocol understanding at session start
- Follow verbosity and approval settings in config.yaml
- Update all protocol files systematically
- Maintain audit trail of decisions and changes
- Prepare structured handoffs for team continuity

## QUICK START
```
1. Confirm: "I acknowledge the Promachos Protocol"
2. Load: Read core.md for complete specification
3. Assess: Review current project state and handoff context
4. Begin: Collaborate following established protocol rules
```

PROTOCOL ACTIVE. Proceed to core.md for complete collaboration specification.