Master planLos Cabos
Costa Palmas
Behind the master plan
3 relations -
Developer Irongate The release names Jason Grosfeld as "Chairman and CEO of Irongate (Costa Palmas developer)", attributing the whole East Cape community rather than a single building; a second page calls Costa Palmas "an Irongate development", a 1,000-acre master planned resort community opened in 2017. -
Building manager not found No opened page names an estate manager, community association or service-charge entity for Costa Palmas. The estate's own pages and Irongate's project page describe amenities and buildings only, and the 2016 announcement names an operator for the Four Seasons resort alone.
-
Holds title to not found No opened page states who holds or held title to the 1,000-acre landholding, nor a year in which the land was acquired or sold. Ownership is asserted only of the Four Seasons resort, which the 2019 release says is "owned and developed by Irongate" — a statement about that building, not about the estate.
Behind these projects
5 firms and individuals 2 open questionsabout this master plan
Points this record cannot yet settle, with the sources on
each side. Both readings are published rather than one being chosen quietly.
Is Irongate a co-developer at Costa Palmas, and should it hold a credit of its own?
- Recorded as reportedThe Costa Palmas projects credit two developers, Costa Palmas and Irongate, and name Costa Palmas alone as owner. "Costa Palmas · Irongate" is how two credits are written out together, not the name of one company.
- Irongate holds no credit of its ownIrongate holds a developer credit of its own on the Costa Palmas projects and appears in the registers and on its own record page. What no opened source settles is whether the co-developer role is correct: it rests on trade press, and the developer’s own pages name Costa Palmas alone.
Los Cabos · Name clash · openWhether `SOMA · FibraSOMA · Sordo Madaleno` should exist as a single registry record when its three members each hold their own.
- A false positive, not a clashA partnership credits each company separately, and the middle dot is only how they are written out together. One combined record survives on its own, which no project now credits — its three members are each credited individually.
- But a composite does not join its membersA composite string is one entity record, so a project crediting it does not credit the partners named inside it. Each partner reaches the register only where a project credits it separately, and a partner named nowhere else is invisible to every register.
Los Cabos · Name clash · open