Keeping status current automatically
Let PYNGYN derive status from the work itself, so the board is never stale.

Status that has to be manually updated is status that goes stale. PYNGYN derives status from the work itself wherever it can, so the board reflects reality without someone having to remember to update it.
What updates automatically
- Task status changes as dependencies complete and work moves through your pipeline
- Overall project health rolls up from the status of its tasks
- Client-visible status (in Client Space) reflects the same live state, not a separately maintained summary
What still needs a person
Judgment calls, like whether a project is genuinely "on track" despite one slipped task, are yours to make. Automatic status handles the mechanical parts so your team's judgment goes toward the calls that actually need it.
Overriding a status
Any automatically derived status can be manually overridden on a task or project if you know something the system doesn't yet.