Shared Initiative Context Manual
Shared Initiative Context is the feature that turns isolated session work into a reusable source of truth for the whole initiative.
What this feature solves
Before this release, a winning thesis often stayed trapped inside the session where it was created.
That created friction:
- You had to re-upload documents in other sessions.
- Or import context manually from previous work.
- Or keep multiple slightly different versions of the same artifact.
Now you can promote the winning document to the initiative scope so every session inside that initiative can use it.
The three scopes
| Scope | What it means | Best use |
|---|---|---|
| Session | Private to one session | Exploration, drafts, alternatives, temporary working files |
| Initiative | Shared across sessions in one initiative | Winning personas, approved roadmaps, validated research, reusable assets |
| System | Shared more broadly | Company-wide defaults, shared templates, reusable global assets |
The key rule: precedence
When the same document name exists in more than one scope, Masterminds resolves it in this order:
- Session
- Initiative
- System
This is intentional. It lets you experiment safely in one session without breaking the shared truth for everyone else.
Why this matters
If you promote persona.md to the initiative scope, but your current session still has another persona.md, the session version wins in that session.
So if you want the promoted initiative document to become the active truth in your current session, make sure you do not keep a conflicting session document with the same name.
The most common workflow
1. Explore in Session
Use session scope while testing alternatives:
- multiple theses
- multiple personas
- multiple roadmaps
- rough working notes
2. Pick the winner
When you decide which document is the winner, promote it to initiative.
3. Reuse everywhere in the initiative
Other sessions inside the same initiative can now see and use that document as shared context.
This is the moment where isolated exploration becomes shared intelligence.
How to move documents between scopes
Use the Journey Navigator in the right panel:
- Drag a document to Initiative to move it into shared initiative context.
- Hold Option on Mac or Ctrl on Windows while dragging to copy instead of move.
- If a conflict exists, review the target name carefully.
Best practice:
- Use Session for experimentation.
- Use Initiative for approved working truth.
- Use System only for assets that should be broadly reusable.
Practical examples
Example 1: Winning persona
- You test 3 persona options inside one strategy session.
- You choose one winner.
- You promote it to initiative.
- Now the design, roadmap, and delivery sessions can all use the same persona.
Example 2: Winning roadmap
- Your strategy session produces multiple roadmap directions.
- You approve one roadmap.
- You promote it to initiative.
- Every downstream master now works from the same roadmap baseline.
Example 3: Safe local override
- The initiative already has
pricing-hypothesis.md. - In one session, you want to test an alternative.
- Create or keep a session-level document with the same name.
- Your session version wins only there, without overwriting the initiative-level truth.
Fast track
- Create or refine a document in one session.
- Decide whether it is still exploratory or already shared truth.
- Promote it to initiative when it becomes reusable across sessions.
- Check for same-name session documents if the promoted file does not seem to take effect.
FAQ
Why can another session see my promoted document?
Because initiative scope is shared across sessions inside the same initiative.
Why is my promoted document not being used in this session?
Most likely there is a session-level document with the same name. Session wins over initiative.
Should I promote everything to initiative?
No. Promote only the documents that should become the shared truth for the initiative.
Is this different from System scope?
Yes. Initiative is shared only within one initiative. System is broader and should be used more carefully.