# Project Context Document
*AI guidance document — fill in fresh for each project before starting a session*

---

## Project Overview

> One or two sentences describing what this project is. What exists, what needs to exist.

**Project name:** _____

**Project type:** _____ (e.g. web app, art commission, engineering consult, training engagement)

**Summary:** _____

---

## Client Background and Goals

> Who is the client? What do they do, what do they care about, and why are they coming to you?
> Include any relevant history, domain knowledge, or organizational context.

**Client / organization:** _____

**Industry / domain:** _____

**Why they came to you:** _____

**What they ultimately want to achieve:** _____

**Known biases or preconceptions to be aware of:** _____

---

## Project Scope and Deliverables

> Define what is in scope and — equally important — what is out of scope.
> List concrete deliverables. Vague scope is the root of most project problems.

**In scope:**
-
-

**Out of scope:**
-
-

**Deliverables:**
-
-

---

## Success Criteria

> What does done look like? How will you and the client know the work is complete and correct?
> Be as concrete and measurable as possible.

**Success looks like:** _____

**Acceptance criteria:** _____

**Who signs off:** _____

---

## Timeline and Milestones

> Key dates, phases, and deadlines. Note any hard constraints vs. soft targets.

| Milestone | Target Date | Hard Deadline? |
|---|---|---|
| | | |
| | | |
| | | |

**Overall deadline:** _____

**Notes on timeline constraints:** _____

---

## Communication Preferences

> How does the client want to communicate? How often? Through what channels?
> Misaligned expectations here cause most relationship problems.

**Primary contact:** _____

**Preferred channel:** _____ (e.g. email, Slack, WhatsApp, in-person)

**Meeting cadence:** _____

**Response time expectations:** _____

**Language / locale:** _____ (note if working across languages or time zones)

---

## Known Risks and Constraints

> What could go wrong? What limits exist that the AI should be aware of?
> Include technical, organizational, personal, or logistical risks.

**Known risks:**
-
-

**Hard constraints:** _____ (things the solution must not do, use, or assume)

**Dependencies:** _____ (things outside your control that affect delivery)

---

## Tech Stack and Tools *(optional — complete for technical projects)*

> Relevant only for software, engineering, or technical consulting work.
> Leave blank or delete for non-technical projects.

**Platform / OS:** _____

**Languages:** _____

**Frameworks / libraries:** _____

**Databases:** _____

**Deployment / hosting:** _____

**Version control:** _____

**Other tools:** _____

**Constraints or preferences:** _____ (e.g. no Windows, no proprietary tools, client uses X)

---

## Budget *(optional)*

> Include only what is relevant and appropriate to share in this context.

**Agreed budget:** _____

**Payment structure:** _____ (e.g. fixed, hourly, milestone-based)

**Notes:** _____

---

## Context and Intent References

> Load these documents alongside this one for full AI context.

- **Personal context doc:** see `personal-context.md`
- **Intent / values doc:** see `intent-values.md`
- **Art context doc** *(if art-related)*: see `art-context.md`