Protect Approved Email Copy With an Immutable-Content Manifest

If copy has already passed legal, product, or brand approval, do not ask an AI email tool to “keep it the same.” Put every protected value in an immutable-content manifest, define which transformations are allowed, and compare that manifest with the final email artifact before release.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 4, 2026.

Migma’s approved-copy workflow separates the task brief from an immutable copy block, protects variables and commercial details, and calls for a deterministic comparison before acceptance. That is the right control boundary: generation may propose presentation, but it does not own approved meaning.

Build the manifest before opening an editor#

Store the source text and protected values in a reviewable record:

Scroll table →

Field	Example	Acceptance rule
`source_version`	`launch-copy-v7`	Must match the approved revision
`subject`	`Your plan changes October 1`	Exact text unless subject edits are explicitly allowed
`preheader`	`Review the new limits`	Exact text and length checked separately
`body_blocks`	IDs plus approved plain text	Every block present once and in approved order
`cta_labels`	`Review your plan`	Exact visible label
`destinations`	Canonical URL per CTA	Normalized destination must match
`variables`	`{{first_name	default: "there"}}`
`commercial_values`	price, discount, date, quantity	Exact value and currency/date semantics preserved
`legal_lines`	terms and unsubscribe wording	Exact or approved jurisdictional variant
`forbidden_additions`	testimonials, urgency, extra links	Zero occurrences

Hash the canonical manifest after approval. The hash does not prove the resulting email is correct, but it proves which input the release gate evaluated.

Separate stable context from immutable campaign facts#

Brand context and campaign copy have different lifetimes. Migma’s brand setup documentation says teams can review website findings and maintain brand guidelines, design references, visual identity, and lasting AI instructions. Use those surfaces for durable rules such as headline casing, button shape, approved fonts, or prohibited tone.

Keep expiring facts—launch dates, offers, prices, coupon codes, legal notices, and one-off claims—in the campaign manifest. A persistent memory is a poor source of truth for a fact that expires next Tuesday.

When sources conflict, the immutable campaign manifest wins for that artifact. Record the conflict rather than allowing the model to reconcile it silently.

Define the transformation budget#

“Do not rewrite” is still ambiguous because production systems legitimately transform content. State what may change:

Scroll table →

Transformation	Default
Add table layout, spacing, and responsive wrappers	Allowed
Convert straight quotes or whitespace	Block unless normalized comparison is approved
Reorder paragraphs or split sentences	Block
Add image, CTA, claim, or link	Block
Wrap a destination in tracking parameters	Allowed only by declared URL rule
Convert variable syntax for a destination ESP	Allowed only by an explicit mapping
Add sender-required footer or unsubscribe element	Allowed and separately verified
Produce a plaintext alternative	Allowed if semantic equality passes

This budget makes review finite. A team can approve a known Mailchimp merge-tag conversion without granting permission to invent a different offer.

Compare semantics and protected tokens#

Run two classes of checks.

First, deterministic assertions:

Extract visible text from the final HTML.
Normalize only the transformations listed in the budget.
Compare every protected block, token, value, and destination.
Reject missing, duplicated, reordered, or newly introduced protected items.
Produce a machine-readable difference report tied to the manifest hash.

Second, human classification. Label every remaining difference as approved, harmless presentation, or blocking semantic change. Do not let a reviewer dismiss a changed URL because the visible button label looks correct.

For links, compare parsed destinations after applying the approved tracking rule. For variables, test complete, missing, long, unusual, and hostile-looking values. A token that survives source HTML but disappears after ESP import still fails.

Test the final artifact, not the generator output#

The email can change after generation:

approved manifest -> generated draft -> editor save -> export/import
                  -> ESP rendering -> received test -> release

Attach the manifest hash and artifact identifier at every boundary. If any step creates a new artifact, rerun the deterministic comparison.

This matters in editor/API workflows. Loops’ Content API release describes content created in code, opened visually, and represented again as LMX. That shared canvas is useful, but every round trip is still a transformation boundary to test.

Add rendering and delivery checks after copy equality#

Copy equality is necessary, not sufficient. Migma’s Email Preflight documentation covers finished-email previews, links, writing, and delivery-risk signals, then recommends sending a test. Run those checks after the immutable manifest passes.

Release evidence should include:

approved manifest version and hash;
final HTML or immutable artifact ID;
deterministic difference report;
reviewer disposition for allowed differences;
Preflight or equivalent result after the last edit;
received test from the intended sender path;
final audience, sender, schedule, and accountable approver.

Any edit after that evidence invalidates the release record. Rerun the relevant gates.

Stop conditions#

Stop the release when a protected value is missing or duplicated, a destination changes without an approved tracking rule, a variable loses its fallback, an unapproved claim or asset appears, or the final artifact cannot be tied to the approved manifest.

Do not waive those failures because the email “reads better.” Once text is approved, better is a new editorial decision and requires a new source version.

Evidence limits#

Marketing Wiki did not run Migma, Loops, an ESP import, or an inbox test. Migma documents the dated approved-copy method, brand-context controls, and Preflight surface; Loops documents a code-to-editor content workflow. The manifest and gates here are a portable operating method. They do not establish that any product will preserve copy without the checks.