Project Context

Context is the authoritative home for project intent and durable knowledge. It is separate from workspace Notes and uploaded files, and it is designed so a teammate or connected agent can understand why work exists before changing it.

Every project has one canonical Brief. It covers purpose, users, outcomes, principles, constraints, non-goals, terminology, priorities, and agent guidance. Owners and project administrators control brief edits and approval transitions.

Other Context types include Specification, Proposal, Decision, Process, Research, Meeting Packet, and Retrospective. Their statuses—Draft, In review, Approved, Superseded, and Archived—communicate maturity without preventing task execution.

Each content change creates an immutable revision. Approved content returns to Draft when edited so prior approval is not implied for new text. Artifacts can relate to other artifacts and link to tasks as Related, Implements, Informs, Evidence, or Action from.

When Context produces concrete follow-up, choose Action item in its Linked work section. Edit the suggested title and description, choose the destination project plan and section, and create the task. ToDoddle opens the action item and preserves a link to the Context it came from. Repeating the same title from the same Context opens the existing action item rather than making a duplicate.

Use Context when information should remain discoverable after a chat or task is complete. Use task comments for the working conversation, the Message Board for project announcements, Notes for workspace-level wiki material, and Documents for files.

Before substantial planning or implementation, agents should load the project brief or bounded project context once. Link the resulting task to the relevant artifact and leave concise evidence or decision comments when work changes the shared understanding.