How Weavidence Journey turns decisions into a protocol

#Answer in brief

Journey does not treat a protocol as a document to be filled in. It treats a protocol as the visible output of a sequence of design decisions, and it keeps those decisions — including the alternatives that were weighed and set aside — inspectable after the fact, so a methodological reviewer is looking at the reasoning, not just its conclusion.

#The problem: reasoning disappears once a protocol looks finished

A study protocol's job is to convince a reviewer the design will actually answer the question it claims to answer. The common failure mode is not a bad design — it is a design whose reasoning has quietly evaporated by the time it reaches review. The tradeoffs that were considered, the design that was picked over, the reason a comparison group was structured one way rather than another: all of that lives in an email thread, a meeting, or someone's memory, and none of it survives into the polished document a reviewer actually reads.^[1]

#What Journey keeps visible

Journey's core capabilities are built directly against that failure mode: design comparison with visible tradeoffs, a protocol built from the same state as the decisions behind it — not a separate document assembled afterward — and export into the format a submission actually needs (HTML, PDF, DOCX, JSON).^[1]

Three signals stay deliberately separate rather than being folded into one reassuring score:

• Decision Score — how well-supported a given decision is.
• Design Fit — how well the chosen design actually matches the question being asked.
• Readiness — whether the protocol, as it stands, is ready for review.

Keeping these apart matters because a design can be well-supported in principle and still poorly fitted to the specific question, or well-fitted and still not ready — collapsing the three into a single number would hide exactly the distinction a reviewer needs.

#The Decision Trace

Every methodological decision in a protocol leaves a visible trail: what was chosen, and — because Journey is explicitly built around comparison — what the alternative was and why it was not chosen. This is what "inspectable" means concretely: not a changelog of edits to a document, but a record of the actual methodological reasoning, attached to the decision it belongs to, revisable without losing the history of how the design got there.^[1]

#Where the authority sits

The researcher keeps the final call. Journey's design comparisons, scores, and suggestions are inputs to a decision the researcher makes, not a decision made for them — consistent with the ecosystem-wide commitment that a human retains the final call and, where AI is present, it acts as a bounded assistant.^[1]

#Practical implications

For a team preparing a protocol for methodological or ethics review, the practical value is not a nicer-looking export. It is that the reviewer can ask "why this design and not that one" and get an answer that was recorded at the time the decision was made, rather than reconstructed under deadline pressure after the fact.

#Limitations and uncertainty

Journey is available now at app.weavidence.com. External scientific validation of the platform is not yet complete, and Journey is not a clinical decision system — its Decision Score, Design Fit, and Readiness signals support a researcher's judgment; they do not replace independent methodological or ethics review.

#Connection to Weavidence

The Decision Trace is Journey's specific instance of the same traceability principle that runs through the whole Weavidence ecosystem — see Why traceability matters in AI-supported evidence systems.