Foundry EAM becomes the preferred founding-team naming direction

---

id: MAXCONNECT-TEAM-004

title: Foundry EAM becomes the preferred founding-team naming direction

type: TEAM

state: red

area: D-brand-design

purpose: discovery-pack

priority: S

work_kind: H

provenance: primary

confidence: medium

triangulated: false

engagement: maxconnect

sources:

• uri: discord://herm/maxconnect/2026-09-04-foundry-eam-name-correction

role: primary

• uri: file://outputs/founding-team-interview-analysis-2026-09-04.md

role: supporting

• uri: file://outputs/founding-team-briefing-pack-2026-09-04.html

role: supporting

relates_to:

• MAXCONNECT-TEAM-003
• MAXCONNECT-INTERVIEW-001

feeds_atoms: []

open_questions:

• Is www.foundry-eam.com registered/controlled and ready for DNS configuration?
• Does Foundry EAM clear company-name, trademark and category-confusion checks in the intended markets?
• Which public naming architecture should be used: Foundry EAM as company, Foundry as shorthand, and Max Connect as internal evidence-history handle?

needs_validation:

• Confirm domain registration/DNS and legal availability before hard-rebranding the pack, source room, design system and public URL.
• Founding team must agree the name/category before external positioning copy moves.

resolution_log:

• 2026-09-04: Ant corrected the intended domain spelling to www.foundry-eam.com; pack and truth surfaces updated to treat Foundry EAM as the preferred naming direction while keeping Max Connect as the evidence-history handle until gates close.

module:

---

Foundry EAM is now the preferred naming direction for the Max Connect opportunity. This is a meaningful Discovery update because it supports the already-emerging independent asset-intelligence/EAM posture and reduces the risk of the business being framed as another Maximo-only implementation partner.

The current target domain is www.foundry-eam.com. DNS/HTTP did not resolve from this machine during the 2026-09-04 check, so availability/control is not proven by the pack. The name should be treated as a preferred founding-team direction, not final public identity, until registration, DNS and legal checks are complete.

Pack implication

The founding-team digest should now say “Foundry EAM / Max Connect” where it discusses the future name/category. Existing atoms, research-room paths and historical evidence may retain the maxconnect handle because they are provenance and control-plane identifiers, not final brand copy.

Open questions

• Does the founding team want the formal name to be “Foundry EAM”, with “Foundry” as shorthand?
• Should foundry-eam.com become the canonical public domain, with www.foundry-eam.com as the visible site?
• What trademark/company-name checks are required before the hard rebrand?