Project context model
Give the next contributor a clean starting point.
2IX project context briefs turn scattered notes into current state, completed work, unfinished work, blockers, risks, next actions, links, people to ask, confidence, and verification date.
Continuity model
What belongs in a project context brief
Project context prevents each new contributor from rediscovering the same basics. It is especially important for technical, open-source, research, data, and operations work.
State and history
A good packet records current state, completed work, unfinished work, blockers, risks, and last verification date in ordinary language.
- What changed?
- What remains uncertain?
- What should the next person avoid undoing?
Next actions and artifacts
The next contributor should see the first three actions, linked docs/repos/issues, artifacts, and people to ask without searching through chat history.
- Public links only on public pages.
- Keep credentials and private files outside the packet.
- Use confidence level to show whether the packet was recently verified.
From brief to useful guidance
Temporary context notes can later become reviewed public guidance when they are stable, useful, and safe to share with volunteers.
- Promote reviewed facts.
- Archive stale guesses.
- Keep private data out of public guidance.
Key terms
- Next-contributor brief
- A short summary that lets a new person take the first safe action quickly.
- Confidence level
- A visible cue for how trustworthy or recently verified the packet is.