Example proposal: persistent project context
The encounter or problem
When work spans documents, chats, browser pages, code, and email, the surrounding intent fragments across tools.
Proposed behavior
Represent projects as user-owned context envelopes containing goals, related artifacts, decisions, open questions, and boundaries.
What could go wrong?
The system may connect items that should remain separate.
Privacy and consent expectation
Users should control what enters a project envelope and which tools can see it.
Popularity can surface a question. It cannot establish truth, priority, acceptance, or architectural authority.
No comments yet. Be the first to challenge or strengthen the idea.