Free browser tool · zero cloud lock-in
Research Synthesis Matrix Builder
Build multi-study literature review matrices with explicit unknown markers and incommensurability guards.
Runs 100% locally in your browser. Build multi-study literature comparison matrices with explicit unknown markers. Incommensurate qualitative and quantitative findings are never flattened into false averages.
Step 1: Literature Review Overview
- Dimension "Write Latency Performance": Incommensurate Methodologies Detected. Quantitative experimental metrics (RCT/Simulation) and qualitative observations cannot be flattened into a single numerical index.
Step 2: Interactive Multi-Study Matrix
Scroll horizontally to view all dimensions| Study & Methodology | Write Latency Performance[Round-Trip Times (RTTs)] | Fault Model Scope | Empirical Cluster Evidence |
|---|---|---|---|
IncommensurateAbstract logical ticks; not physically benchmarked in milliseconds.Note: Theoretical model does not yield physical latency numbers. | Crash-stop; assumes processes execute correct state transitions. | [Unmeasured] | |
0.5ms median write latency (1 RTT commit path). | Fail-stop with persistent state log recovery. | Validated on Linux commodity servers across 43 human student comprehension trials. | |
IncommensurateAsymptotic round complexity under eventually perfect detector <>P. | Crash-stop with weakly complete failure detection. | [Unmeasured] | |
IncommensurateSubjective engineer perception: consensus latency perceived as acceptable during normal load.Note: Qualitative interview finding; incommensurate with millisecond benchmarking. | Correlated power loss, operator misconfiguration, disk wear. | Historical incident post-mortems over 10 years of operations. |
Step 3: Obsidian GFM Synthesis Table
Full Markdown table with explicit unmeasured markers# Distributed Consensus Latency & Fault Tolerance Synthesis **Core Research Question:** How do crash-fault-tolerant consensus protocols balance write latency vs network partition resilience? > [!WARNING] Incommensurability Guard > - Dimension "Write Latency Performance": Incommensurate Methodologies Detected. Quantitative experimental metrics (RCT/Simulation) and qualitative observations cannot be flattened into a single numerical index. | Study & Citation | Methodology | Write Latency Performance | Fault Model Scope | Empirical Cluster Evidence | | --- | --- | --- | --- | --- | | **Lamport1978** (CACM 21(7), pp. 558-565) | Theoretical / Formal Proof | ⚠️ Abstract logical ticks; not physically benchmarked in milliseconds. | Crash-stop; assumes processes execute correct state transitions. | _[Unmeasured]_ | | **Ongaro2014** (USENIX ATC 14, pp. 305-320) | Algorithmic / Benchmark Simulation | 0.5ms median write latency (1 RTT commit path). | Fail-stop with persistent state log recovery. | Validated on Linux commodity servers across 43 human student comprehension trials. | | **Chandra1996** (JACM 43(2), pp. 225-267) | Theoretical / Formal Proof | ⚠️ Asymptotic round complexity under eventually perfect detector <>P. | Crash-stop with weakly complete failure detection. | _[Unmeasured]_ | | **Gray2006** (Distributed Systems Field Interviews, Tech Report) | Case Study / Organizational Analysis | ⚠️ Subjective engineer perception: consensus latency perceived as acceptable during normal load. | Correlated power loss, operator misconfiguration, disk wear. | Historical incident post-mortems over 10 years of operations. |
The Danger of False Commensurability in Meta-Synthesis
When writing academic literature reviews, researchers often face a severe methodological trap: false commensurability. In an effort to summarize disparate findings cleanly, writers frequently force qualitative ethnographies, formal mathematical proofs, and randomized physical benchmarks into identical comparison columns.
A qualitative study exploring engineer perceptions of consensus latency cannot be averaged with a microsecond hardware benchmark. The two measurements belong to completely different ontological paradigms. Coercing them into an aggregated "average latency score" creates a fundamentally misleading metric.
Epistemic Integrity in Literature Matrices
The Research Synthesis Matrix Builder enforces strict academic standards:
- Incommensurability Auditing: The engine automatically inspects populated cells within every thematic dimension. If qualitative interviews and double-blind quantitative trials are mixed under a metric column, an active incommensurability alert is raised.
- Explicit Unknowns: When a paper does not evaluate a specific variable, the cell is explicitly marked as
[Unmeasured]. It is never coerced to zero, blanked out, or filled with fabricated placeholder values. - Obsidian-Ready GFM Tables: Outputs clean GitHub Flavored Markdown tables that format seamlessly in local Obsidian vaults, complete with callouts preserving methodological caveats.
Frequently Asked Questions
Clear answers regarding literature synthesis, incommensurability guards, and Obsidian integration.
Questions
What is a research synthesis matrix in academic literature reviews?
A synthesis matrix is a structured table used by researchers to compare multiple primary studies across key thematic dimensions or evaluation criteria. Unlike an annotated bibliography that examines papers in isolation, a synthesis matrix reveals consensus, divergence, and research gaps across literature bodies.
Why does this tool prevent incommensurate studies from being flattened into identical numbers?
Methodological incommensurability occurs when distinct research paradigms (such as a qualitative interview study vs. an algorithmic simulation or a randomized controlled trial) are inappropriately forced into a single quantitative scale or averaged together. Flattening qualitative depth or incompatible metrics into arbitrary numerical ratings produces pseudo-scientific artifacts and distorts meta-analyses.
How does the tool handle missing or unexamined variables across studies?
If a study did not measure or evaluate a specific thematic dimension, the matrix explicitly marks the cell as [Unmeasured] rather than leaving it blank or coercing it to zero. This preserves transparency and identifies genuine gaps in literature.
Can I export the synthesis matrix directly into Obsidian?
Yes. The tool formats clean GitHub Flavored Markdown (GFM) tables compatible with Obsidian, complete with wikilinks, methodology labels, and warning callouts highlighting incommensurate metrics.
Are exported CSV spreadsheets protected against formula injection?
Yes. Any cell content starting with spreadsheet formula triggers (=, +, -, @, tabs, or newlines) is prefixed with an apostrophe and wrapped in escaped quotes, defending Microsoft Excel and Google Sheets against formula execution vulnerabilities.
Does this tool transmit my literature review or confidential manuscript data to the cloud?
No. All matrix compiling, incommensurability auditing, and Markdown formatting execute 100% locally in browser memory. Zero data is sent to external servers.
Keep your research private, portable, and verifiable
Build your literature review matrices in clean plain Markdown on your local disk with zero cloud telemetry.