How Do You Merge Three Conflicting Notes Into One Defensible Draft?

A useful Sunday draft can begin by merging three fragments that were never written for marketing: a commit message, a support reply, and a voice memo. The founder’s job is to preserve what each fragment proves, resolve contradictions, and review one defensible draft before publishing anything.

In April 1970, the Apollo 13 crew faced rising carbon dioxide inside the lunar module. The command module carried square lithium hydroxide canisters; the lunar module’s system used round ones. NASA engineers in Houston had to connect incompatible parts using materials available aboard the spacecraft, then give the astronauts instructions they could follow under pressure.

NASA flight controller Ed Smylie helped lead the work. The improvised adapter used items including plastic bags, cardboard, a hose, and duct tape. Jim Lovell and Jeffrey Kluger document the episode in Lost Moon, their account of a mission whose safe return was still uncertain.

The comparison has limits, and the stakes are worlds apart. But the working shape is familiar: useful pieces exist, they do not fit together yet, and somebody has to turn them into one clear set of instructions before time runs out.

Three fragments contain three kinds of evidence

At 8:47 p.m. on Sunday, imagine a solo founder opening three notes from the week.

The commit message says:

“Add workspace-level approval requirement before scheduled Reddit publishing.”

The support reply says:

“You can draft Reddit replies now, but publishing depends on the connected product account and remains reviewable.”

The voice memo says:

“Talk about how founders can stay active in communities without handing an agent permission to say anything it wants.”

Each fragment carries something valuable.

The commit message records what changed in the product. It is precise, but it assumes the reader understands the underlying system.

The support reply explains the capability in customer language. It also contains an important boundary: provider access and product-account permissions still matter.

The voice memo captures the benefit. A founder can reduce repetitive engagement work while retaining approval control.

Used alone, each note produces weak copy. The commit message becomes release-note jargon. The support reply becomes a narrow answer to one person. The voice memo risks overstating autonomy.

Combined carefully, they can produce a reviewable claim:

“Marketing Agent can draft contextual Reddit replies from your product strategy and publish supported replies through the connected product account. You decide where approval is required, so community engagement can continue without giving the system unrestricted permission to speak for your product.”

That draft still needs human judgment. It now has enough structure to review.

The merge should expose conflicts before publication

Combining notes means more than pasting three blocks into a prompt. The useful step is finding where the sources disagree.

Suppose the voice memo says “publishes everywhere,” while the support reply mentions only supported Reddit publishing. The narrower, verified statement wins.

Suppose the commit message describes an approval gate, but the founder remembers enabling unattended publishing for another product. Both facts may be true because Marketing Agent keeps strategy, connections, permissions, schedules, and approval rules scoped per product. The draft needs to say which workflow it describes.

Suppose none of the fragments contains a customer result. The copy cannot claim that community engagement increased signups or saved five hours. A reviewable draft marks that proof as unknown instead of filling the gap with a plausible number.

This is the same discipline behind making product promises narrower and defensible, explored in Product Marketing Promises: How Dev Made His Launch Narrower and Defensible. It also prevents the drift that appears when engineering, support, and marketing maintain separate versions of the product story, as shown in The Three Product Descriptions, and What Their Drift Costs a Developer.

The merge becomes a small evidence audit:

• What changed?
• What can a customer do now?
• What limits or approval boundaries apply?
• What benefit follows directly from the capability?
• Which attractive claims still lack proof?

Five minutes spent on those questions can prevent a week of distributing the wrong promise.

One reviewable draft beats three unfinished intentions

The Sunday-night goal is modest. Produce one draft that a tired founder can accept, correct, or reject.

Marketing Agent can use a product’s configured positioning, brand voice, competitors, keywords, offers, and channel strategy to turn source material into blog articles, social posts, newsletters, and videos. It can also maintain an editorial calendar and publish approved or unattended content to connected destinations where provider access permits.

Control remains part of the work. The founder can keep approval requirements, capability pauses, permissions, budgets, and schedules tied to the relevant product. Automation can run multiple times per day, subject to daily safety caps and plan usage limits, but a late Sunday note merge does not require switching everything to unattended mode.

A practical review order is simple. Check factual capability first. Check audience relevance second. Check the benefit and evidence third. Check channel fit last.

That order matters because a polished LinkedIn post built on an inaccurate product claim is still inaccurate. Formatting cannot rescue the wrong canister.

Make Monday start with a decision

Before closing the laptop, save the merged draft beside its source fragments. Keep the commit message, support reply, and voice memo attached or referenced so Monday’s reviewer can see why each sentence exists.

Then choose one next state: approve it for a channel, return it with a specific correction, or hold it until missing evidence arrives. “Needs work” leaves the same open loop for tomorrow.

Apollo 13’s adapter succeeded because Houston worked from the materials actually available aboard the spacecraft. Your product draft deserves the same constraint. Use the facts you have, label the facts you do not, and finish Sunday with one object someone can review.