format/frontmatter
Front matter: the title is text, the date is data, and the target's slug is its own.
What changed
This is what the diff version was told. The nodiff baseline got the current page of each language instead.
English changed
@@ -1,9 +1,9 @@ --- -title: Membership fees +title: Membership and fees slug: fees -updated: 2026-01-10 +updated: 2026-09-01 --- -# Membership fees +# Membership and fees Membership costs 200 SEK per year.
Runs
nodiff
✗ Run 1 · 0 edits · 1 turn · 1,873 in / 261 out tokens · $0.0073 · 3.0 s
Checks
- ✓
keeps "slug: avgifter" - ✗
has "updated: 2026-09-01" - ✗
lacks "2026-01-10" - ✗
has /^title: Medlemskap (och|&) avgifter$/m - ✗
has /^# Medlemskap (och|&) avgifter$/m - ✓
2× /^---$/gm
Swedish, before → after
Left unchanged.
The translator's notes
Comparison of the two pages: - Title: en "Membership and fees" and sv "Medlemsavgifter". The Swedish title covers the same topic in its own words, so I'm leaving it. - Slug: en "fees" and sv "avgifter". The slug is markup and the Swedish one is localized, so I'm leaving it. - Body: en "Membership costs 200 SEK per year." and sv "Medlemskapet kostar 200 kr per år." These say the same thing, so no edit is needed. - The `updated` date is 2026-09-01 in en and 2026-01-10 in sv. The content is identical, so this looks like a metadata difference only. I'm not changing it, because no content changed in Swedish. I made no edits. The Swedish page already says what the English page says.
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions (English (en)). The languages are equal peers; none is the original. One or more of them may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now. Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things. The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that: - A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself. - A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose. - A difference in order or structure is not a reason to reorder Swedish. - Something that only looks like a difference, but says the same thing, stays as it is. Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style. Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word. Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why. Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content: --- title: Membership and fees slug: fees updated: 2026-09-01 --- # Membership and fees Membership costs 200 SEK per year. ## Current sv content (this is what you'll edit): --- title: Medlemsavgifter slug: avgifter updated: 2026-01-10 --- # Medlemsavgifter Medlemskapet kostar 200 kr per år. Bring the sv file up to date with the pages above.
✗ Run 2 · 0 edits · 1 turn · 1,873 in / 245 out tokens · $0.0028 · 3.5 s
Checks
- ✓
keeps "slug: avgifter" - ✗
has "updated: 2026-09-01" - ✗
lacks "2026-01-10" - ✗
has /^title: Medlemskap (och|&) avgifter$/m - ✗
has /^# Medlemskap (och|&) avgifter$/m - ✓
2× /^---$/gm
Swedish, before → after
Left unchanged.
The translator's notes
Comparison of the two pages: - **Title:** the English page says "Membership and fees" and the Swedish says "Medlemsavgifter". Swedish still covers both topics in its own words, and the slug and title are localized on purpose. I'm leaving it. - **Body:** the English "Membership costs 200 SEK per year." matches the Swedish "Medlemskapet kostar 200 kr per år." The facts are the same, so no edit is needed. - **`updated` date:** English has 2026-09-01 and Swedish has 2026-01-10. The content is identical, so no text change is waiting. I'm not changing the date, because it would claim a revision that didn't happen. I made no edits. The Swedish page already says what the English page says.
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions (English (en)). The languages are equal peers; none is the original. One or more of them may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now. Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things. The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that: - A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself. - A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose. - A difference in order or structure is not a reason to reorder Swedish. - Something that only looks like a difference, but says the same thing, stays as it is. Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style. Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word. Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why. Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content: --- title: Membership and fees slug: fees updated: 2026-09-01 --- # Membership and fees Membership costs 200 SEK per year. ## Current sv content (this is what you'll edit): --- title: Medlemsavgifter slug: avgifter updated: 2026-01-10 --- # Medlemsavgifter Medlemskapet kostar 200 kr per år. Bring the sv file up to date with the pages above.
✗ Run 3 · 0 edits · 1 turn · 1,873 in / 274 out tokens · $0.0031 · 3.6 s
Checks
- ✓
keeps "slug: avgifter" - ✗
has "updated: 2026-09-01" - ✗
lacks "2026-01-10" - ✗
has /^title: Medlemskap (och|&) avgifter$/m - ✗
has /^# Medlemskap (och|&) avgifter$/m - ✓
2× /^---$/gm
Swedish, before → after
Left unchanged.
The translator's notes
Comparing the two pages: - **Title:** en has "Membership and fees" and sv has "Medlemsavgifter". The Swedish title covers the same topic in its own words, so this is a difference on purpose and needs no edit. - **Slug:** en has `fees` and sv has `avgifter`. The slug is translated by design, so it stays. - **Body:** en has "Membership costs 200 SEK per year" and sv has "Medlemskapet kostar 200 kr per år". The two say the same thing, so no edit is needed. - **`updated` date:** en has 2026-09-01 and sv has 2026-01-10. The content is the same, so there is nothing to bring across. I'm leaving the date alone because it is metadata and I have no content change to record. I made no edits. The Swedish page already says what the English page says.
The full prompt
System
You are keeping the Swedish (sv) version of a document up to date with its other language versions (English (en)). The languages are equal peers; none is the original. One or more of them may have changed since Swedish was last brought up to date. You have the current page of each other language and the current Swedish page. You have no diff and no earlier version, so you cannot see what changed: only how the pages compare as they are now. Your job is to bring the Swedish page up to date with the current English page: find what it says that Swedish does not, or says differently, and make the edits a careful editor of the Swedish page would make so that it says the same things. The versions are not copies of each other. They may differ on purpose: wording, order, examples, local services and links, whole sections that only one language has. Many differences between the pages are deliberate, not changes waiting to be made. Keep all of that. It follows that: - A fact that differs may need several edits in Swedish: everywhere Swedish states it, so that Swedish does not contradict itself. - A difference may need no edit at all: when Swedish says the same thing in its own words, or leaves something out or adds something on purpose. - A difference in order or structure is not a reason to reorder Swedish. - Something that only looks like a difference, but says the same thing, stays as it is. Some things the documents cannot settle: two languages say different things about the same fact, or a change could mean two different things for Swedish. Then do not guess. Call ask, once, with the question, the options you see, and what you would do if no one answered, and keep the content in question as it is unless you get an answer. Ask only when the answer changes what you write, never about wording or style. Markup is not text. Component and attribute names, ids, front matter keys, file paths and URLs stay exactly as they are, except a link whose Swedish pages follow a convention of their own (a language prefix, a translated path): new links in Swedish follow that convention too. Text a reader sees is Swedish, written as a Swedish writer would put it, not word for word. Before you edit, write out briefly: every place where the Swedish page no longer says what the other pages say, quoted from both, with whether you think it is a change waiting to be made in Swedish or a difference on purpose, and why. Then make the edits, together in one response. Edit with edit_file: its old_string must appear exactly, once, in the Swedish file. Each edit's result shows the Swedish file around it as it now reads. Look at it: if anything there is wrong, was missed, or now contradicts something elsewhere in the Swedish file, fix it with further edits. When the Swedish file is right, say in a sentence or two what you changed and why. If nothing needs to change, make no edit at all, and say why not. Write your plan, your notes and your summary in English, whatever language the documents are in.
User
## Current en content: --- title: Membership and fees slug: fees updated: 2026-09-01 --- # Membership and fees Membership costs 200 SEK per year. ## Current sv content (this is what you'll edit): --- title: Medlemsavgifter slug: avgifter updated: 2026-01-10 --- # Medlemsavgifter Medlemskapet kostar 200 kr per år. Bring the sv file up to date with the pages above.