Episode 1 - Choose one result

Pick one research result you have already postponed. Do not migrate your website: the first success is one private page with a clear claim, evidence, and uncertainty boundary.

What you will finish

By the end of this episode, you will have:

• one result small enough to explain on one page;
• the evidence another person should inspect;
• the sentence you are willing to make public after review;
• a list of work that is explicitly outside this first update.

The next three episodes create a clean CLI workspace, write the private article, validate it, and then publish the source deliberately. Local preview needs Docker. A production URL needs your own deployment configuration.

Pick a good first update

Choose a result that has already created a mismatch between what you know and what your public record says:

• an experiment changed your recommendation;
• a paper was accepted but the project page still describes a submission;
• a benchmark, archive, or release changed an earlier claim;
• a project milestone exists only in a slide deck or chat;
• a résumé statement has evidence that is not linked anywhere.

Avoid "my whole research website" and "all past projects." Those are migration projects. This guide is about making one update small enough to complete.

Write the boundary in plain language

Before touching the CLI, fill in four lines:

Example:

Know the four separate actions

• Edit changes ordinary Markdown/TOML files.
• Validate checks the source and rebuilds the local index.
• Publish changes the reviewed item's source state.
• Preview or deploy renders the public output when the required infrastructure is configured.

These steps remain separate so editing or accepting an Agent proposal cannot accidentally expose private work.

Move to Episode 2 when the update fits on one page and you know what evidence supports it.