Shared context
Give collaborators useful sources and decisions, with their owner and freshness visible.
Make the source visible
Shared context should help collaborators understand a mission without guessing where its facts came from. The proposed model would connect approved documents, decisions, and working notes to the work that needs them.
Each item should identify its source and the person or team responsible for maintaining it. Readers need to distinguish an agreed decision from a draft suggestion. A task can then point to the relevant information instead of copying an entire collection of notes.
Check freshness and access
Context should show when information was checked and whether it still applies to the current mission. A changed deadline, an expired document, or an inaccessible reference should prompt review.
Conflicting sources should remain visible until someone resolves the disagreement. A newer note should not automatically erase an authoritative policy. Record the decision that resolves the conflict and who made it.
A release source of truthUse the approved release checklist for readiness, the product notes for supported features, and the current launch decision for the date. Label an unconfirmed customer quote as a draft instead of treating it as a verified claim.
Share only what belongs in the workspace
- Confirm the source owner, date, and relevance.
- Check that the intended collaborator can access the reference.
- Label assumptions and unresolved conflicts.
- Keep passwords, API keys, and tokens out of mission text and notes.
- Review access when a role or mission changes.
Access to a mission should not automatically grant access to every linked source. Persistent storage, document synchronization, and access enforcement remain planned. The current preview keeps mission changes local; refreshing resets them.