Keep the source on each paragraph
Open a paragraph and read the source Cortee used for that change.
The failure mode
Documentation goes wrong when wording changes and the reason disappears. A chatbot draft can sound finished, then get pasted into a wiki with no trail. The next reader sees polished language and has no way to check where it came from.
How Cortee keeps the source on the paragraph
You write what changed in plain language. Cortee drafts a small live-page edit from that input, then keeps a normalized source with the paragraph after the change lands. Opening the line shows the source Cortee used, not a lost chat thread. If the edit misses, you reverse it and the page returns to the prior wording.
Why the loop has to be fast
When you enter what changed, Cortee updates the live page in about 0.7 seconds1. That speed matters because the team can correct the page while the decision is still fresh, instead of waiting for a documentation pass that never quite happens.
Who hits this problem
Anyone who inherits a page they cannot trust, and anyone who has watched shared documents disagree after a paste from chat. In both cases the missing piece is a live paragraph that still carries its source.
FAQ
Does Cortee invent facts?
Edits come from the notes and source context you provide. Open a paragraph to see the source that produced the wording.
What if the edit is wrong?
Reverse it. Every change can be undone, so a miss does not have to linger on the page.
1 Typical edit latency is around 0.7s in internal tests. Performance varies by prompt complexity, network, and system load.