What it is
The Berkeley Protocol on Digital Open Source Investigations, published in 2020, is the recognised international standard for collecting, preserving, verifying, and presenting open-source information rigorously. It was co-developed by the Human Rights Center at the University of California, Berkeley, and the United Nations — that is its public provenance, and it shaped the language the Protocol uses.
Before the Protocol, open-source research was rigorous in places and improvised in others. The Protocol's contribution was to write down a consistent methodology — one that any field needing the work to stand up under scrutiny could point to as a shared baseline.
Why the principles travel
The Protocol was written for one specific setting, but the underlying asks are sector-agnostic. Track every source. Preserve the original so the work can be re-checked. Log every step from collection through to a finding. Corroborate across independent sources, not a single one. Protect the people in and behind the material.
Those are general properties of disciplined research, and they apply just as cleanly to a planning team comparing zoning decisions across cities to spot policy patterns, an environmental researcher tracking deforestation or water-quality change from open satellite and NGO sources, a due-diligence analyst tracing ownership and litigation history for a parcel through corporate registries, an infrastructure team reconciling project announcements with what procurement portals actually show, a public-administration researcher monitoring tender activity across jurisdictions, or a journalist field-mapping a topic across thousands of public sources. The questions differ. The methodology does not.
What it asks for
The Protocol is detailed, but its core asks are consistent:
- · Identification and authentication — know what a piece of content is and where it came from
- · Preservation — capture the source so it survives even if the original is later changed or removed
- · Chain of custody — log every step from collection to presentation, so nothing is unaccounted for
- · Corroboration — establish reliability across independent sources, not from any single one
- · Verifiability — keep enough of the original that a disputed finding can be re-checked
- · Ethical and security considerations — protect the people in, and behind, the material
What it means for tooling
The Protocol is a methodology for people, not a software spec — it describes how a researcher should work. But several of its requirements are really about record-keeping, and record-keeping is where tools either help or quietly fail you. Capturing the source URL, timestamp, and a content hash at the moment of collection; preserving the raw material; logging every change — these are mechanical, and a tool that does them by construction removes a whole class of provenance failure.
What a tool cannot do is the judgement: source assessment, corroboration decisions, and the operational decision the work was for. A well-built workspace makes the mechanical parts reliable so the researcher's attention goes to the parts that need a human.
How DjeedX relates to it
DjeedX does not apply the Berkeley Protocol — applying it is the researcher's responsibility, and claiming otherwise would miss the point. What DjeedX does is restructure the open record into Silver-tier records that already carry the chain-of-custody attributes the methodology expects: original source URLs, capture timestamps, content hashes, the raw extraction payload, and a full edit history. The verification and review steps stay with you. The evidence trail they depend on is there from the start — alongside your own internal data, in the same workspace.