# The Google Doc Analogy: Understanding How It Works

Let's make this concrete with an analogy you already understand.

**Traditional System = Email Attachments**

When you email someone a document, they get their own copy. If they make changes, you have no idea unless they email it back. Now you have two versions. Someone else makes edits on their version—now there are three versions. Which one is correct? No one knows. You schedule a meeting to reconcile the differences.

**Blockchain = Google Doc**

Everyone works on **the same document** in real time. You see changes as they happen. There's a complete history of who changed what and when. You can revert to any previous version. Most importantly: **everyone always sees the same information**.

<figure><img src="/files/ZByx11B0lE2WTMDFc9nx" alt=""><figcaption></figcaption></figure>

But **blockchain adds three critical features** beyond Google Docs:

1. **No one owns the document** (it's decentralized—no single company controls it)
2. **Changes can't be deleted** (history is permanent, creating accountability)
3. **Advanced self-executing actions can be automated** (e.g payments released upon action verification)

This is why blockchain works for business transactions where Google Docs wouldn't: **no single party can manipulate the records**, and **everyone can verify the complete history** without trusting any intermediary.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/the-business-case-for-blockchain-in-supply-chain/what-blockchain-actually-does-for-supply-chain/the-google-doc-analogy-understanding-how-it-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.