Merge Knowledge Notes Without Erasing Disagreements
As of 2026-10-23 · The AZET team. We prepared this maker-authored exercise for fun and reference. Its notebook entries are fictional. The workflow is a proposal for reviewing text, not a verified AZET capability or a report of customer results.
Two notes about a fictional drawing exercise seem ready to merge. One says, “Use a narrow border to give the picture room.” The other says, “The wide border made the picture feel less crowded.” A polished combined note might quietly choose one statement. That would produce cleaner prose by removing the most interesting question.
The merge needs to preserve what each writer actually observed. In this example, both notes belong to the same person, but they concern different drawings. The apparent disagreement may come from missing context rather than an inconsistent preference.
Define what the merged note should answer
Give the destination note one job: help its owner choose a border for a future sketch. That scope does not require every sentence from both source notes. It does require enough context to understand why the earlier choices differed.
Assign short source labels such as A and B before editing. Keep untouched copies. In A, the owner used a narrow border around a dense street sketch. In B, the owner used a wide border around a sparse leaf study. Neither entry says that its choice should apply to all drawings.
A merge that turns either observation into a universal design rule would exceed both sources. The useful output is a comparison with boundaries, not a confident verdict.
Sort overlap into three categories
Work through the notes at the claim level. Mark exact repetition, complementary detail, and unresolved tension. These categories describe editorial relationships; they do not certify the claims themselves.
Exact repetition can usually be consolidated with source pointers retained. Complementary detail can sit together if the connection is explicit. Unresolved tension should remain visible until someone checks the original context or makes a new observation.
For our border notes, a small ledger might look like this:
| Proposed sentence | Source basis | Editorial decision |
|---|---|---|
| A narrow border suited the street sketch | A | Keep as an individual observation |
| A wide border suited the leaf study | B | Keep with its different subject |
| Narrow borders suit all dense images | Neither | Omit as an unsupported extension |
The last sentence may sound plausible. That is precisely why it belongs in the review ledger rather than slipping into the merged note unnoticed.
Use a prompt that preserves disagreements
Propose a merge of these two notes for the stated destination question. Label each source A or B. Separate duplicate statements, complementary details, and unresolved tensions before writing the merged draft. Attach source labels to factual assertions. Keep personal observations limited to their original situations. Do not resolve a disagreement by choosing the smoother wording. Return a short list of omitted material and the reason for each omission.
Inspect the classification before reading the polished draft. If the model has already called the two border observations contradictory, ask whether that label depends on treating different drawings as equivalent. Fix the reasoning at that stage.
The omission list matters too. A sentence about the paper's size might look incidental, yet explain why a border felt large. If it affects interpretation, restore it or record that the dimension is unknown.
Write a note that can accept another observation
A defensible merged passage could read: “In the street sketch, I preferred the narrow border. In the leaf study, I preferred the wide border. The drawings differ in subject and density, so these entries do not isolate border width as the reason. For the next sketch, compare two border options before deciding.”
That passage has a practical next step without claiming a general rule. It also leaves room for a third observation. The note is useful because its limits are readable, not because it sounds complete.
Keep the original dates if they exist. If a date is missing, write “date not recorded.” Do not infer chronology from file order or whichever source was pasted first.
Close the merge with a reversible record
Save the new note beside the originals initially. Record which source passages were combined, which were omitted, and which questions remain open. A short record is enough if another reader can reconstruct the main choices.
Read the merged note without the sources, then read it again with them. The first pass checks whether it stands on its own. The second checks whether it says more than the originals support.
Only then decide whether to archive the older copies. Keep links or stable identifiers so a future correction can reach the evidence. A merge that cannot be traced is harder to repair when context returns.
FAQ
Should every disagreement stay in the main prose?
No. A minor disagreement can live in a clearly linked review note. Keep it somewhere visible and retrievable, and do not present the main conclusion as settled if the disagreement affects it.
What if one source is clearly newer?
Newer does not automatically mean more accurate. Look for an explicit correction, a changed situation, or fresh evidence. Preserve the distinction between replacing an earlier claim and merely adding a later observation.
Can AI decide what to delete?
It can propose omissions with reasons. Check them against the destination question and the original context. Keep the merge reversible until you have reviewed both the retained and omitted material.
The product reference
The AZET maker introduction described an assistant and early-access waitlist on October 3, 2026. This note-merging exercise is independent of that dated product description and does not update its availability claims.
For the AZET waitlist, visit azet.io.