One brief, connected work

The example project brief now sits beside its tasks and decisions. The brief records the audience, intended result and relevant constraints. Individual tasks can refer to that shared context while retaining their own scope and owner.

What to review

Use the brief for information that applies across the project. A change to one task should remain on that task unless it changes the wider agreement. The example does not import an outside document, synchronize a file service or establish access permissions. The product walkthrough explains the relationship between context, review and a final handoff.