<!--
Sync Impact Report:
- Version change: None (initial creation) -> 1.0.0
- List of modified principles: All (initial population)
- Added sections: All (initial population)
- Removed sections: None
- Templates requiring updates:
    - .specify/templates/plan-template.md: ⚠ pending (Constitution Check section needs update)
    - .specify/templates/spec-template.md: ⚠ pending (Implicit alignment with principles needs review)
    - .specify/templates/tasks-template.md: ⚠ pending (Test-First principle alignment needs review)
- Follow-up TODOs: TODO(RATIFICATION_DATE)
-->
# FitTrack Report Generator Constitution

## Core Principles

### I. Library-First
Every feature starts as a standalone library; Libraries must be self-contained, independently testable, documented; Clear purpose required - no organizational-only libraries

### II. CLI Interface
Every library exposes functionality via CLI; Text in/out protocol: stdin/args → stdout, errors → stderr; Support JSON + human-readable formats

### III. Test-First (NON-NEGOTIABLE)
TDD mandatory: Tests written → User approved → Tests fail → Then implement; Red-Green-Refactor cycle strictly enforced

### IV. Integration Testing
Focus areas requiring integration tests: New library contract tests, Contract changes, Inter-service communication, Shared schemas

### V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity
Text I/O ensures debuggability; Structured logging required; Or: MAJOR.MINOR.BUILD format; Or: Start simple, YAGNI principles

## Additional Constraints

Technology stack requirements, compliance standards, deployment policies, etc.

## Development Workflow

Code review requirements, testing gates, deployment approval process, etc.

## Governance

All PRs/reviews must verify compliance; Complexity must be justified; Use [GUIDANCE_FILE] for runtime development guidance

**Version**: 1.0.0 | **Ratified**: TODO(RATIFICATION_DATE) | **Last Amended**: 2025-10-09