Move a draft into the manuscript

Principles in play: Control transitions.TRACEControl transitions

Moving a draft into the shared manuscript is a boundary transition, and the standing instructions require an explicit request for it. The promotion record names who moved the draft, when, and on whose words. Until then, drafts stay in your sandbox.

Steps

1. Read the draft before it moves.

   Say to your agent

   What changed, what was asked, chosen and checked, and what was not checked?

2. Say the promotion.

   Say to your agent

   Promote my results into paper/, then commit and push.

   Either partner can promote, their own draft or the other’s.

3. See where it went.

   Say to your agent

   Show me the promotion commit and the row in sources/transitions.jsonl that names it.

   The file arrives in paper/ byte for byte as the sandbox draft, and the row names your sentence as its authority.

4. Try a page without promoting anything.

   Say to your agent

   Copy the LaTeX starter into my sandbox, put one sentence from the shared note into the copy, build it, and open the page.

   The page is built from a copy, and nothing under paper/ changes.

Things to know

• Promotion is not acceptance. Accepting the work is a separate decision; see Accept, return or refuse work.
• Two people can act at once. If your partner pushed first, your agent syncs and pushes again, and both rows are kept.
• A return stays a return. A returned or refused promotion is never rewritten as a success.

What the agent runs

python3 scripts/trace_record.py transition --help    # kind, object, checks, actor, authority, decision, destination, commits
python3 scripts/trace_record.py registries           # validates the rows on read