RobotnixAcademy

Week 04 · lesson

Collaboration Leaves Evidence

Shared documents are useful because several people can contribute without emailing final-v7-actually-final.docx back and forth. The same collaboration tools can also make it unclear who changed what unless you understand the evidence they leave behind.

Three collaboration modes, three different effects

Direct editing changes the document content immediately for people with edit access.

Suggesting proposes changes that can be accepted or rejected, preserving a review step.

Comments attach discussion to a location or idea without directly rewriting the underlying sentence.

The best mode depends on the job.

Worked choice

A partner notices your brief says:

LiDAR always tells a robot exactly where it is.

The partner is not sure the claim is correct and wants you to verify it.

A comment such as “Can we verify this claim? LiDAR measures distance; localization usually depends on additional processing/context” may be better than silently rewriting the sentence. The comment preserves the reason for review.

Later, version history can show that the document changed, but version history alone does not prove the new claim is true. Revision evidence and factual evidence are different.

Run a controlled collaboration cycle

Use a course-safe Docs sample and an authorized class partner, or use a teacher-provided simulation if sharing is not appropriate.

  1. Partner A writes a short two-paragraph draft.
  2. Partner B leaves one substantive comment about clarity, evidence, or structure.
  3. Partner B proposes one wording change using Suggesting if the feature is available.
  4. Partner A responds to the comment and either accepts/rejects the suggestion with a reason.
  5. Inspect version history or available revision evidence.

Do not use this exercise to inspect private document history outside the course.

Evidence chain

DRAFT
  ↓
COMMENT / SUGGESTION
  ↓
REASONED RESPONSE
  ↓
REVISION
  ↓
VERSION EVIDENCE

The chain matters. A screenshot of version history with no explanation only proves that some change occurred.

Failure mode: Editor access for every reviewer

Granting Editor because it is convenient can erase the distinction between “review my work” and “coauthor my work.” Use the permission and collaboration mode that matches the intended action.

Collaboration Evidence Record

Record one complete cycle:

  • original sentence/section;
  • comment or suggestion;
  • response;
  • final revision;
  • revision/version evidence;
  • what the evidence proves;
  • what it does not prove.

You are ready for the Week 4 source lab when you can explain the difference between who may modify the file and how collaborators choose to propose a modification.