The repeat edit: which fixes to stop making in Ember Console's editor

The editor is the cheapest place in Ember Console to fix a report, and that is why some fixes get made every week instead of once.

Ember Console is a session-report builder for coaches, in closed beta, and its landing page promises the editor learns: “Refine the report directly in Ember’s editor, and your next report will be created with those past edits and preferences already in mind.”

A fix you make once is a preference. A fix you make every week is an instruction you never wrote down. Call that one a repeat edit.

Why does the same edit come back every week?

Because editing is quicker than writing the instruction down, and the landing page sells that quickness: “As easy to edit as it is to generate.” A fix that takes one pass never feels expensive enough to become a rule, so you pay for it again next week.

One r/ChatGPT poster put a number on what that costs. Pulling PDF data into one fixed CSV format, they had trained the chat several times and still had to “retrain it on the ~30% it forgets every time, which of course is extremely tedious.” One reply told them to stop retraining and have the model write the instruction out as a prompt for its future self.

Which edits belong in the box prompt or the eval?

The ones that come back. A template in Ember Console carries your letterhead and a set of boxes, one prompt and one eval per section, so a standing instruction has two places to live.

The edit you just made	Where it belongs
The same wording fix, every report	the box prompt
A section that keeps arriving too long, or without the agreed next step	the box eval
Something true of this client, this week	the editor

The prompt says what the section should contain. The eval is the minimum standard it has to pass, and on each build the AI gets every prompt and the eval system, then reworks each box until it passes.

What is not stated yet?

Two questions, and they are mine to answer rather than yours to guess.

What editing in the dashboard changes for the next report: the prompt, the eval, or an example. And whether the learning is per template, per client, or per coach.

The landing page live on 2026-10-05 makes the claim twice and describes it neither time, so until I write those answers down, treat the loop as a bonus and the boxes as the plan. An instruction sitting in a prompt or an eval is one you can read back and change.

If the box itself is wrong, the fix it needs is a different question.

Open last month’s reports and mark every fix you made more than once. Each mark is a box you have not finished writing.

Questions people ask next?

Can AI learn my writing style?

Ember’s landing page says it “learns from your edits” and checks each result against criteria you set. What that changes inside the next report is not published, so plan around the instruction you wrote into a box yourself.

How do you edit AI generated notes?

Edit once, then sort what you edited. A change you made because of this client stays in the editor, and a change you make every week belongs in that section’s prompt or in the standard it has to pass.

Does an edit in Ember carry across clients?

Not stated. Whether the learning is per template, per client or per coach is one of two open questions on my own editor fact sheet, and I would rather leave it blank than guess in public.