# CUATRECASAS PERIMETER BILLING + EMAIL — AGENTIC CONTINUATION CONTROL

**Date:** 24 August 2026

**Status:** controlling continuation protocol for future repository threads

**Public/private rule:** this protocol may be public; the underlying timekeeper ledger, disbursement ledger, private emails, current-counsel material and draft correspondence are not public exhibits.

## 1. Mission

Continue the Cuatrecasas reconstruction as one non-fragmented audit of:

1. every engagement, matter opening, mandate variation and conflict decision across the 2014-to-present relationship;
2. every invoice, proforma, credit note, retainer, payment, allocation, write-off, estimate, unissued-work figure, disbursement and collection step across the complete Aweswell / LPB / Matkator and connected client-service perimeter;
3. every located Cuatrecasas email and attachment, including the complete 2020-to-present collection/enforcement period and all earlier transaction, insolvency, Community, title, Registry, planning, finance, ONA, Stoneweg/Varia, Elaia/Lagune, possession/protection and handover work;
4. what the firm said it would do, what it billed, what work product was actually produced, what was filed or implemented, what result followed, what remained undone and what explanation or missing record could reconcile the difference;
5. how the advisory mandate later became billing, collection, pagaré, Cambiario and ETJ enforcement activity, without assuming that a valid invoice necessarily proves a valid Matkator obligation or that an adverse outcome necessarily proves negligence.

The objective is an evidence-addressable professional-liability and account-reconciliation record. It does not replace the primary alleged responsibility of the Acosta Matos-connected perimeter, the Insolvency Administrator or any independently relevant judicial act. Any Cuatrecasas responsibility is separate and potentially cumulative. No common plan is presently proved.

## 2. Mandatory first reads

Future threads must read, in this order:

1. `ops/CURRENT_STATE.json`;
2. `CURRENT_HANDOVER.md`;
3. this protocol;
4. `archive/SUN_PARK_UNITARY_REVERSE_ENGINEERING_AND_CUATRECASAS_REDIGEST_20AUG2026.md`;
5. `archive/CUATRECASAS_EVIDENCE_GAP_AND_TRIGGER_REGISTER_20AUG2026.md`;
6. `archive/CUATRECASAS_CRITICAL_GAP_CLOSURE_CONTROL_20AUG2026.md`;
7. `archive/CUATRECASAS_EDGEWORTH_PARTIAL_OVERLAP_CONTROL_24AUG2026.md`;
8. the current bilingual `/cuatrecasas-sun-park/`, `/cuatrecasas-dp748-*`, `/cuatrecasas-critical-gaps/` and `/cuatrecasas-icam-ccacm-2026/` pages.

Always verify remote `main` and live GitHub Pages before treating a dated handover or archived analysis as current.

Before committing a continuation, run `python3 scripts/validate_cuatrecasas_billing_email_sync.py` together with the existing Cuatrecasas, publication-integrity, insolvency-language and audience-experience gates.

## 3. Controlling 24 August checkpoint

The located native invoice set currently contains **22 issued invoices**. Their issue dates run from 2015 to January 2019, while several work and payment records begin in 2014.

Current reconciled public-safe figures:

- native invoice-face total: **EUR 327,608.32**;
- firm's 3 July 2019 table: **EUR 326,608.32**, after netting a EUR 1,000 retainer on one row;
- invoice-face total marked settled: **EUR 190,777.60**;
- corresponding firm-table amount: **EUR 189,777.60**;
- unpaid issued invoices: **EUR 136,830.72** across six invoices;
- later unissued/estimated work: **EUR 152,424.95**.

Those totals are a checkpoint, not permission to stop searching. They must be tested against native originals, replacement lineage, account statements, bank evidence and the firm's complete matter ledger.

Known controls requiring explanation include:

- six 2015 invoices first issued to LPB and later reissued to Aweswell; the old and replacement copies must never be double-counted;
- the later replacement package contained six replacements plus one additional EUR 10,000 invoice;
- two amounts appear transposed in the firm's 2019 table and several dates differ from the native invoices;
- invoice `1810108702` records EUR 104,237.50 incurred, EUR 70,000 billed and EUR 2,907.51 expenses; the stated discount percentage does not match the arithmetic description;
- invoice `1810203752` includes engagement/fee-related activity within the located time entries and describes prospective-lender work while being addressed to Aweswell;
- invoice `1810219093` says EUR 97,492.50 accrued but bills EUR 30,000; the later unissued-work figure leaves a current EUR 6,087.55 reconciliation gap;
- some located invoice copies contain no supporting timecards or no itemised disbursement schedule;
- the two court-collection routes contain a current EUR 7,313 difference and possible same-work overlap requiring original-instrument, causal-debt, debtor, credit and recovery reconciliation. This is not presently described as proved completed double recovery.

## 4. Perimeter rule: do not merge legal capacities

Build a separate row for every potentially relevant capacity:

- instructing client;
- named engagement client;
- service beneficiary;
- invoiced entity;
- expected payer;
- actual payer;
- retainer provider;
- guarantor or security provider;
- pagaré issuer;
- judicial debtor;
- owner of the asset pursued;
- entity receiving a credit or write-off;
- entity against which later collection or enforcement was taken.

Begin with Aweswell, LPB and Matkator, then search the native corpus for every connected entity, individual or former name. Do not assume the list is exhaustive. Do not treat group control, common ownership, commercial benefit or a shared hotel project as automatic authority to bill or enforce against another legal person.

## 5. Source acquisition — search before concluding

### A. Native billing corpus

Locate and de-duplicate:

- invoices and replacement/reissued invoices;
- proformas, budgets and fee proposals;
- engagement letters, scope variations and termination/venia documents;
- timecards and narrative ledgers;
- expenses, travel, Registry, notary, translation and external-adviser disbursements;
- retainers, account statements, bank transfers and allocation notices;
- credit notes, discounts, write-offs and settlement entries;
- unissued-work schedules and estimates;
- collection letters, receivables tables and account reconciliations;
- pagarés, delivery records, authorities, presentment and accounting treatment;
- Cambiario and ETJ pleadings, certified dockets, enforcement calculations, auction/adjudication/cession records and recoveries.

Preserve native filenames, file hashes, source location, page count, duplicate family, replacement lineage, issue date, service period, addressee and confidentiality status.

### B. Email corpus

Search all available mailboxes and files, not only messages whose subject contains `invoice` or `Cuatrecasas`.

Run overlapping searches for:

- firm domains, historic lawyer/finance-team senders and the receivables function;
- invoice numbers, matter names and attachments;
- `factura`, `invoice`, `honorarios`, `fees`, `proforma`, `provisión`, `retainer`, `pago`, `paid`, `saldo`, `pendiente`, `descuento`, `abono`, `write-off`, `timesheet`, `time entry`, `gastos`, `suplidos`, `recobro`, `collection`, `pagaré`, `cambiario`, `ejecución`, `ETJ`, `remate`, `cesión`, `adjudicación`;
- `Aweswell`, its former corporate name, `LPB`, `Luchy Playa Blanca`, `Matkator`, Sun Park and every connected matter label;
- ONA, Stoneweg, Varia, Elaia, Lagune, financing, term sheets, due diligence, ECO valuation, security, insolvency exit, possession, access, Registry, planning, Community and handover;
- forwards and quoted chains where the visible sender is not Cuatrecasas;
- messages to accountants, corporate-finance advisers, lenders, insolvency professionals and successor advisers that attach or describe Cuatrecasas work.

For every relevant message, capture From/To/CC, sent time and timezone, subject, full thread context, attachments, quoted history, delivery evidence and whether the proposition is direct, forwarded or a participant's account of an oral conversation. Do not equate an account of an oral conversation with the firm's written position.

### C. Work-product and outcome corpus

Search for the corresponding deliverable and implementation record:

- final advice, draft/final comparison and internal/external version history;
- filings, LexNET receipts, service, orders and follow-up;
- contracts, term sheets, security documents, condition ledgers and closing checklists;
- Registry, planning, title and valuation work;
- notices, complaints, preservation measures and urgent protective steps;
- handover index, successor-counsel transfer and unresolved-deadline list;
- result, non-result, contrary decision and later corrective opportunity.

## 6. Required line-by-line audit model

Create one private row for each invoice entry or, where no timecard exists, each invoice narrative block:

| Field | Required content |
|---|---|
| Invoice identity | native number, issue date, service period, replacement family |
| Entity/capacity | client, addressee, beneficiary, payer and later debtor kept separate |
| Time/cost | professional, date, hours, rate, amount, expense and currency |
| Billed proposition | exact neutral description of what the entry says was done |
| Source email/file | independent message, attachment or work product supporting the entry |
| Mandate fit | within scope, scope unclear, variation located or outside located mandate |
| Deliverable | draft/final advice, contract, filing, meeting, call, research or no product located |
| Implementation | filed, sent, signed, acted upon, superseded, abandoned or unknown |
| Result | favourable, adverse, mixed, opportunity preserved/lost, or no causal result attributable |
| Missing explanation | finite document or person capable of resolving the gap |
| Public status | publishable aggregate, redacted proposition, private, privileged or hold |

Then aggregate without losing the row-level denominator by:

- year;
- matter/workstream;
- entity/capacity;
- professional team;
- billed versus unbilled;
- advice versus implementation;
- protection versus transaction versus litigation versus collection;
- result and open causal gap.

## 7. Billing-to-result test

For every material billed workstream, answer in order:

1. What exact mandate and objective existed?
2. What foreseeable risk was known at that date?
3. What did Cuatrecasas say it would do?
4. What did it bill for doing?
5. What work product exists?
6. What action was actually taken and by whom?
7. Was it timely, entity-correct and integrated with the other workstreams?
8. What result followed?
9. What contrary evidence or reasonable professional explanation exists?
10. What counterfactual is supportable without assuming inevitable success?
11. What later act, omission, handover or enforcement choice changed or compounded the position?
12. What finite disclosure would confirm, narrow or defeat the allegation?

Do not grade legal work only by whether litigation was won or lost. Equally, do not treat extensive recorded effort as proof that the accepted protective objective was competently implemented.

## 8. June 2018 package lock

Future work must not regress to the proposition that no concrete Stoneweg offer existed before the Las Palmas meetings.

Controlling formulation:

> On 12 June 2018, after an agreed call and expressly for the next day's judicial meeting, Stoneweg itself sent what it called an `Oferta Vinculante`, attaching an `Oferta Vinculante Condicionada`. The offer stage was agreed, closed and issued. Completion and drawdown of the contemplated transaction still required the stated closing conditions. The located attachment's conformity blocks are blank, so it is not publicly described as a countersigned facility agreement.

The Elaia/Lagune materials must be analysed as reciprocal components of the same documented EUR 26 million downside-sale / bridge-takeout route: a buyer-signed own-funds proposal and an Aweswell-signed preferred-acquisition instrument circulated contemporaneously as agreed/duly signed for the Elaia vehicle. Do not present the route as an unsolicited, one-sided document. Continue to request adviser-held execution copies, board/DD/SPA records and any extension without using their present absence to erase the documented package.

## 9. Private/public firewall

Never commit or publish:

- the private line-level timekeeper CSV;
- the private disbursement CSV;
- unredacted invoices or account statements;
- Gmail/message identifiers, mailbox exports or authentication tokens;
- current lawyer or procedural-representative names on the public Cuatrecasas proceedings pages;
- privileged advice, contemplated causes of action, litigation sequencing, limitation analysis, witness/expert strategy, settlement position or weaknesses;
- private ONA remuneration or unnecessary personal financial data;
- an unsent draft merely because it is complete.

Public output may use reconciled invoice totals, invoice numbers where necessary, neutral workstream descriptions, finite anomalies, primary-document hashes and document-answerable requests after privacy, privilege, defamation and procedural-prejudice review.

## 10. Litigation-communications readiness gate

The analysis and drafting campaign may resume once this protocol and the synchronized public pages are live. Resumption means research, recipient mapping, draft preparation, attachment selection and verification—not transmission.

Before any communication is sent:

1. rebuild it from external-safe primary evidence rather than current-counsel advice;
2. verify the latest court and regulatory status;
3. resolve every recipient and current role/mailbox;
4. freeze the exact English/Spanish text, links and attachment manifest;
5. confirm that no current lawyer/procurador name, privileged strategy or private billing ledger is disclosed;
6. separate established fact, attributed allegation, inference, open question and requested record;
7. preserve the primary alleged Acosta Matos-connected responsibility while presenting Cuatrecasas responsibility as separate/cumulative;
8. state that no UK legal proceedings are being pursued; any SRA question is separate, non-litigation and jurisdiction-dependent;
9. run live-link and attachment-open tests;
10. obtain Gil Marer's explicit final authorization for that exact recipient list, subject, body, links and attachments.

**Repository work, draft approval and campaign readiness never constitute email-send authorization.** No email may be sent, scheduled, resent or silently saved into a live recipient-addressed draft before the final authorization gate.

## 11. Required future outputs

Each continuation thread should leave durable outputs, not only a chat summary:

1. refreshed invoice master and replacement-lineage table;
2. payment/retainer/credit allocation ledger;
3. email-and-attachment search log with denominator and date range;
4. matter/entity/capacity matrix;
5. time-entry-to-deliverable-to-result matrix;
6. collection/court-recovery reconciliation;
7. contradiction and missing-record register;
8. public-safe aggregate reconstruction;
9. private billing inquiry / preservation / right-of-reply draft;
10. campaign-readiness note stating exactly what remains before transmission.

End every run with:

- sources searched and search dates;
- files/messages located and de-duplicated;
- gaps that remain;
- propositions strengthened, narrowed, disproved or unchanged;
- public changes made;
- private artifacts created;
- whether anything was sent (**default: no**).