OptionalclosedRequired when phase is "closed". Records the reason for the Charter to be closed.
Conditions that bound the solution space, including explicit scope exclusions. Hard constraints are non-negotiable; soft constraints are strong preferences.
The resolved choices that define the current project direction. Only decisions significant enough to explain why the artifact is in its current state belong here. Everything else lives in issues.
OptionaldescriptionOrientation: what kind of project this is and the context needed to read the charter
Why this project exists and what concrete outcome it must reach. This is the single most important field in the Charter — every requirement, constraint, and decision should be traceable back to it.
What the project outcome must do or be. Scope exclusions and solution-space limits belong in constraints, not here.
OptionalstakeholdersEveryone with a stake in the project outcome — active contributors or not.
Unix epoch milliseconds of the last Charter update.
The project-level identity and reasoning anchor.
A Charter holds what an engineer or agent needs to understand what the project is trying to achieve and why the current artifact state exists.