# Project Notes Discipline

The imported pack expected the skill to keep a lightweight but current project
memory surface during meaningful work. Harness Forge preserves that discipline
as guidance rather than shipping the source pack's sample note file.

## Keep current

- project name and primary goal
- intended users and success metric
- time, budget, security, compliance, performance, and availability constraints
- proposed or active stack across frontend, backend, data, infra, CI, and observability
- decisions as mini-ADRs with date and rationale
- open questions and working glossary terms

## Update triggers

- a major design choice is made
- a key requirement, constraint, or risk becomes clear
- the active stack or ownership boundary changes
- the team uncovers unknowns that materially affect delivery

## Recommended structure

1. project snapshot
2. constraints
3. proposed or active stack
4. decisions as mini-ADRs
5. open questions
6. glossary

## MVP operating rule

Until package-owned helper commands land, update the equivalent notes manually
using this structure and keep the rationale concise enough that another agent or
maintainer can recover the project state quickly.