Repo modernization
Update CI, package metadata, config files, templates, and documentation across many repositories while preserving local differences that should remain.
Uses
Structured changes that need evidence.
StructuredMerge is useful where ordinary text replacement is too brittle and a silent best effort merge is not acceptable.
Agent-safe edits
Let planning tools propose changes while the merge layer applies declared behavior, reports unsupported cases, and preserves review decisions.
Configuration drift
Bring JSON, TOML, YAML, and similar files back toward a known shape without flattening comments or policy-specific exceptions.
Docs and embedded content
Handle Markdown sections, link definitions, fenced code blocks, and other nested surfaces with explicit ownership and delegation rules.
Above specialized backends
The same pattern can help with merge-like workflows outside ordinary documents: normalize a manifest, validate policy, produce a dry run, hand execution to a specialized backend, and record provenance. That is an application of the contract model, not the starting point for the public project.