Part E: the manuscript on Overleaf

You and your coauthors can edit the manuscript on Overleaf while the repository keeps one account of it.

Principles in play: Track records, Control transitions.TRACETrack records · Control transitions

Needs: an Overleaf plan with the Git integration, and its token in .env. This is the workshop repository’s own setup, and the natural part to do at home.

What you do

1. One of you creates a blank Overleaf project named after your pair, shares it, and copies its Git link from Menu, Sync, Git.

2. Say to your agent

   Connect this repository to my Overleaf project and put the paper there. The Git link is: (paste the link).

   Your agent pushes paper/ and nothing else, and prints which commit Overleaf now holds.

3. On Overleaf, change one sentence in sections/introduction.tex and wait for it to save.

4. Say to your agent

   Bring my Overleaf edit back.

   Your agent commits the edit in your name, pushes to GitHub and to Overleaf, and prints again which commit Overleaf holds.

5. Your partner presses Sync Changes and asks their agent to connect to the same link; it finds the manuscript there and pushes nothing. In the Graph, the commit that brought your edit back carries your name, and has no Record: line and no execution marker.

Ask your agent

• Which commit does Overleaf hold now, and does its paper/ still match ours?
• What crossed to Overleaf, and what stayed here?
• What will the report say about the commit my Overleaf edit made, and why?

What you can say now

The manuscript is one state in two places, and the repository can say which commit Overleaf holds: that is T, track records, across the boundary. Only paper/ crossed, and my trace records did not: that is C, control transitions, at the edge.