RELATIONSHIP DOSSIER · FAMILY ≠ ATTRIBUTION
Three separately accountable people appear across the Sun Park Community / Pamanil record and, later, across a disclosed family and corporate network. This page shows where those lines intersect — and where the evidence requires them to remain separate.
THREE PEOPLE · THREE CONTROLLED LANES
Family relationship: husband of Shaila María Cogolludo Ramos; son-in-law of Antonio Cogolludo Rojas.
Controlled chronology: source-reported Community administrator functions by 22 June 2011; legitimacy and act-specific mandate remain separate questions.
FMMMFamily relationship: wife of FMMM; daughter of Antonio Cogolludo Rojas.
Controlled chronology: documented in the Pamanil / Community communications perimeter by 8 April 2014; later corporate powers must not be backdated.
SCRFamily relationship: father of Shaila; father-in-law of FMMM.
Controlled chronology: documented in the Sun Park Community / Pamanil perimeter by 10 April 2014; each office, power and act requires its own proof.
ACRSOURCE-IDENTIFIED FAMILY PHOTOGRAPH
Identified as Shaila's husband.
Identified as FMMM's wife and Antonio's daughter.
Identified as Shaila's father and FMMM's father-in-law.
Identification provenance: Patricia Domínguez identified the people in a source email dated 21 September 2026; Gil Marer then expressly confirmed that Francisco Mario Matos Matas is on the left, Shaila María Cogolludo Ramos is in the centre, and Antonio Cogolludo Rojas is on the right. This is source-attributed, user-confirmed identification — not a facial-recognition result.
Evidence limit: The photograph establishes identity/relationship context only. It does not establish authority, coordination, knowledge, intent or liability. It also proves no Community mandate, corporate mandate, wrongdoing or causation.
22 SEP 2026 RESCAN · PHASED ATTRIBUTION
22 June 2011 → The controlled minutes place him in administrator functions. This is the trio's earliest personal starting point.
Pamanil communications → FMMM and Shaila appear in the 8 April communication; Antonio is in the Community/Pamanil representation lane by 10 April. The page does not backdate all three to 2011.
12 June 2017 → The record places Antonio in the Community presidency and preserves the attributed Pamalexsha/administration and Shaila vice-presidency/work lanes, subject to act-by-act proof.
18 May: security/access → · 7 June: material control →. This is where the record's strongest joint attribution to the three concentrates, while order, presence, vote, instruction, implementation, knowledge and benefit remain individual questions.
4 February 2022 → · Orion / later network →. FMMM's continuity is direct in the record; later Antonio/Shaila links are not used to manufacture earlier participation.
Rescan of GitHub, public GitLab Pages, all three connected Gmail accounts and the Library corpus. Open canonical JSON map →
COMMUNITY ORGAN · MONTELANZA/MOLINA → PAMANIL/PAMALEXSHA → ACOSTA MATOS/CAM
The record separates the 2008 completion question, owner-by-owner CEXP accession/non-adherence and the emergence of a Molina-linked owner split. The decisive transition for this trio is 22 June 2011: FMMM is recorded in administrator functions, Pamanil is ratified for administration/maintenance and the minutes address debt, voting, document custody and litigation. Montelanza →
8 Apr 2014: FMMM and Shaila appear in the Pamanil/Community communications perimeter. 10 Apr 2014: Antonio represents Cristina Molina Petit. 19 Nov 2015: he represents her again. 26 Apr 2016: FMMM continues as administrator; Antonio represents Inversiones Salinetas; the documentary Pamanil→Pamalexsha transition appears. 11 Jun 2016: FMMM participates in the working meeting with PwC/advisers on operation, costs, debt, records and insolvency. Communications → · 2016 meeting →
The 12 June 2017 meeting places Antonio as president, Shaila as treasurer and FMMM as secretary-administrator; Pamalexsha/FMMM administration continues. The next-day Pamalexsha email signed “Shaila” announces Antonio's presidency and renewal of the company for administration services. This is a direct documentary connection among the three, the organ and the administration vehicle.
At the 18 May 2018 meeting, Antonio chairs, FMMM acts as secretary-administrator and Shaila is recorded as treasurer. The president is authorised to hire security up to €8,500/month for access control/preservation. This is the trio's strongest documented Community convergence before 7 June. The minute alone does not prove who later gave operational instructions, what areas were affected or an unlawful purpose.
The 7 June dossier preserves the allegation that Community authority, security, access, keys and administration were used as a bridge into material control by the CAM/Acosta Matos perimeter. For Antonio the proof target is contract/provider/payer/instructions; for Shaila, voting/treasury/communications/intervention; for FMMM, custody/documents/instructions/implementation. Acosta Matos perimeter →
The private corpus preserves three important controls: the 29 June “Molina and Matos relationship” package; the 18 July DP 1132/2018 Q&A expressly testing CAM, FMMM, Antonio, Shaila, Molina-linked owners and Pamanil/Pamalexsha; and the 12 November email requesting counsel's draft “against FMMM, Cogolludo and Shaila.” They prove the contemporaneous investigative hypothesis, not that its accusations were true.
The 4 February 2022 record keeps FMMM in the secretary-administrator/bank lane while José Daniel Acosta Matos chairs the project meeting. That makes FMMM the longest personal documentary bridge between the earlier Community architecture and the later Acosta Matos phase. Antonio's or Shaila's exact 2022 participation is not manufactured from kinship or later corporate offices.
Official records place Antonio as initial administrator of Pamalexsha and later in Noalpa/Santa Lucia; later powers place Shaila in Noalpa and Pamalexsha; and in 2024 FMMM and José Daniel Acosta Matos sit together on the Orion board, with FMMM also in the AGM lane. These facts support custody, disclosure and economic-continuity questions; they do not prove a historic agreement.
Canonical machine-readable map: fmmm-shaila-antonio-action-map-v1.json. It records every phase, actor, role/action, evidence class, connection and evidential limit.
WHY A DEDICATED PAGE
FMMM appears in the controlled Community/Pamanil record by 2011; Shaila and Antonio appear in the same documentary environment by April 2014. Their dates and capacities are kept person-specific.
The 8 April 2014 communications record places FMMM and Shaila together in the Pamanil / Community communications perimeter. Antonio appears in the Community/Pamanil representation lane two days later. That proximity is a research fact, not a finding of common intent.
The repository's audit of the 7 November 2024 Orion Documento de Emisión records an expressly disclosed FMMM–Shaila–Antonio family/corporate architecture around Pamalexsha and related companies. The correct question is what each later role proves, not whether later ownership can be projected backwards.
Private 2018 working material already examined FMMM, Antonio and Shaila together. Such advocacy material proves that the questions were being raised at the time; it does not establish that the allegations were true.
THREE LANES · ONE CLOCK
RELATIONSHIP MAP
EVIDENCE DISCIPLINE
Names; controlled minimum dates; the family relationships recorded in the project controls and later issuer material; identified Community/Pamanil/Pamalexsha appearances; later corporate links where the cited source states them.
Claims that Community machinery was captured or instrumentalised; disputed authority; debt/vote manipulation; access/security allegations; alleged coordination. These remain attributed allegations unless and until proved by the competent authority.
DP 1132/2018 did not list FMMM as an investigated person in the controlled caption; the repository records him as having been summoned as a witness. Do not silently upgrade that historical status.
Any named person or entity may provide a correction, source, competing chronology or response. Relevant material should be preserved and assessed under the same source and attribution rules.
SOURCE ROUTES