# Product naming and compatibility notes

**Prepared:** 4 November 2026
**Product brand:** BuildMender
**Original working name / compatibility identifiers:** CI Resolve / `ci-resolve`
**Recommended candidate:** **BuildMender**

## Recommendation: BuildMender

**Tagline:** Automatic CI repair. Verified through merge.

BuildMender communicates the product's central action: repairing broken engineering builds and test workflows. It is easy to pronounce as “build men-der,” uses familiar words, and can extend from CI failures into broader engineering reliability without making an unsupported promise to repair every failure.

Suggested product description:

> BuildMender automatically collects CI failures, reproduces supported issues, proposes bounded source repairs, verifies the original tests, and follows repairs through CI and merge.

For an initial product launch, use **BuildMender — Automated CI Failure Resolution**. The category descriptor explains the product before buyers recognize the brand.

Following selection of the `BuildMender` repository, the product website and dashboard now use **BuildMender**. The folder, package, CLI, environment variables and repair-branch prefix remain `ci-resolve` for compatibility. This is a display-brand change, not a package or configuration migration.

Repository: [BuildMender](https://github.com/subash-thiruppathi/BuildMender).

## Shortlist

| Rank | Candidate | Why it fits | Tradeoff |
| --- | --- | --- | --- |
| 1 | **BuildMender** | Clear build-repair meaning; straightforward engineering positioning | “Build” can suggest compilation only; descriptor should include tests/CI |
| 2 | **MergeMender** | Emphasizes carrying a repair through the PR/merge lifecycle | May be mistaken for a merge-conflict-only tool |
| 3 | **ForgeMender** | Broader engineering-platform personality | Less immediately descriptive; “forge” is widely used in software and other fields |
| 4 | **CI Resolve** | Clear existing working name; no immediate migration effort | Generic wording is less distinctive as a brand |

## Preliminary public-search findings

Exact-name and software/CI-focused searches were performed on the guide date. This was an initial naming screen, not comprehensive clearance.

No clearly matching software product surfaced for **BuildMender** or **MergeMender** in the limited searches performed. That does not establish that either name is unused, registrable or legally available. ForgeMender also had nonsoftware associations in the search results and is less preferred on clarity alone.

Several initially considered alternatives already have visible usage:

| Name excluded from the recommendation | Observed use | Source |
| --- | --- | --- |
| RunMend | Monitoring silent failures in growth/automation tools | [RunMend](https://www.runmend.app/) |
| Runwright | Scheduled-job platform with failure diagnosis, plus a testing-related GitHub Action | [Runwright](https://runwright.app/), [GitHub Marketplace](https://github.com/marketplace/actions/runwright) |
| Checkwright | Verification tooling for coding-agent delivery, closely adjacent to this product | [Checkwright](https://checkwright.dev/) |
| PatchRelay | Existing software projects, including a GitHub PR delivery/merge pipeline | [PatchRelay project documentation](https://github.com/krasnoperov/patchrelay/blob/main/docs/merge-queue.md) |

The adjacent uses make these less attractive choices for this product, even without drawing any conclusion about legal rights.

## Checks still required before adopting the name

- Search relevant trademark registries and company records in intended markets.
- Verify the desired domain through a registrar at the time of purchase.
- Check npm/package registries, GitHub organization/repository names and social handles directly.
- Check spelling/pronunciation with prospective engineering buyers.
- Assess similarity to existing “Mender” and build/repair brands before commercial adoption.

No domain registration, trademark filing, handle reservation or application rebrand has been performed. No domain availability is claimed.

## How the brand would appear

- **Product:** BuildMender
- **Category:** Engineering workflow automation
- **Initial use case:** Automated CI failure resolution
- **Headline:** A failed build. An automatic path forward.
- **Short pitch:** Reproduce the failure. Verify the repair. Keep delivery moving.

The operational guide continues to use the actual current commands. If BuildMender is selected later, update the UI, website, package/CLI naming, environment-variable compatibility, documentation, deployment configuration and repository links together.