# TeamBuild — AI-Powered Engineering Workflow System

## Start Here

1. Read [HANDOFF.md](HANDOFF.md) — current project state, what's been decided, what's next, and the full research inventory
2. Read [requirements.md](requirements.md) — standalone requirements spec (extracted from interview)
3. Check [conversation-logs/](conversation-logs/) — numbered transcripts of all project conversations

## Key Context Files

| File | Purpose |
|------|---------|
| `HANDOFF.md` | **Current state + next task** — always read this first |
| `requirements.md` | v0.1 requirements spec with build order and module definitions |
| `base-plan.md` | Original plan (superseded by requirements.md, kept for context) |
| `initial-build-ticket-idea.md` | Original inspiration — full vision beyond v0.1 |
| `conversation-logs/` | All project conversations, numbered in order |
| `research/` | Reference material — see HANDOFF.md for what's been reviewed vs. not |
| `current_ai/` | Josh's current Claude Code setup — baseline for skills and config |

## Rules

- **Context efficiency is paramount** — NEVER front-load an entire codebase into context. Use targeted, lazy loading. Read index notes first, drill down only when needed. See requirements.md for the full Context Window Management spec.
- **Modular everything** — every component must work independently, plug-and-play per project/user
- **Provider-agnostic** — no AI provider lock-in, abstraction layer from day one
- **TDD** — tests before implementation, always
- **Strict linting and type checks** — no exceptions
- **Track costs** — token usage, actual costs, context window health on everything
- **Circuit breaker** — all agent loops must have a max retry (3-5) before escalating to human
- **Open source first** — self-hosted where possible
- **Log every conversation** — save to `conversation-logs/` with sequential numbering before ending a session
