The manuscript on Overleaf

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

Overleaf holds only the manuscript; the repository holds the manuscript together with the trace records. An edit made on Overleaf comes back into the repository as a commit in your name, and the repository can say which commit Overleaf holds.

The workshop repository's setup

These steps follow Part E of the workshop, in the repository each workshop pair receives. The TRACE-OS release ships no Overleaf command, so ask your agent what your own project provides.

Steps

1. Create a blank Overleaf project, share it, and copy its Git link (Menu, Sync, Git). You need an Overleaf account with the Git integration.

2. Have your agent connect it.

   Say to your agent

   Connect this repository to that Overleaf project and put the paper there. Here is the link.

   Only paper/ is pushed, and your agent prints which commit Overleaf holds.

3. Edit one sentence on Overleaf, then bring it back.

   Say to your agent

   Bring my Overleaf edit back.

   The edit is committed in your name and pushed to both places.

4. Check where things stand.

   Say to your agent

   Which commit does Overleaf hold now, and does its paper/ still match ours?

Things to know

• Only the manuscript crosses. Your trace records stay in the repository.
• An Overleaf edit is your own commit. It carries your name, no Record: line and no trailer.
• Your partner connects with the same link. Their agent finds the manuscript already there and pushes nothing.