Analysis
Versioned memos and research log
Write private, team, or published memos with version history and exact evidence links in one research log.
Implemented task
Public task
Open Memos, Connections, or operation history from the project workspace.
Expected outcome: Research notes, links, and reversible history retain their exact evidence and revision context.
Declared product contract
Inputs and task boundary
Inputs
- Research memo text
- Optional exact evidence links and visibility choice
Input constraints
- Private, team, and published visibility are explicit and versioned.
User actions
- Open Memos in the project workspace.
- Write or revise a memo and choose visibility.
- Link exact evidence or inspect prior revisions in the research log.
Outputs
- A versioned memo and research-log entry with explicit visibility and evidence links.
Decision boundary
Where it fits
- Analytic, reflexive, methodological, or project notes that need history and evidence.
Outside the boundary
Where it does not fit
- Implicit publication of a private note.
Verification
Product proof
journey
proof.m2-analysis-kernel
- Verified
- Review due
- Expires
- All five locator kinds, overlap, multiple codes, and exact evidence return are covered.
- Codebook, memo, history, research connections, and withdrawal child journeys pass.
- Every child artifact is hashed and rerun from a fresh database.
Failure boundary: The proof covers the completed M2 kernel, not M3 cases, matrices, or later collaboration rounds.
journey
proof.m2-evidence-history
- Verified
- Review due
- Expires
- History, memos, shares, and events return to the exact revision and evidence.
- Reversible operations append compensation while governance actions use dedicated recovery.
- Published evidence remains frozen until an explicit new share.
Failure boundary: The proof covers reviewed excerpts and operation history, not complete reports.
OpenVerbatim is an open-source (Apache-2.0) qualitative data analysis platform for coding and analyzing interview transcripts. AI-suggested codes stay marked as suggestions until a human reviewer confirms or rejects them, and every decision is kept in an audit trail. The full feature set is available when self-hosted; there is no paid feature wall.