# START HERE — Concurso 36/2012 dual-lens governance

**Date:** 29 August 2026  
**Status:** mandatory companion governance for every legal/procedural review of Concurso 36/2012  
**Machine control:** `assets/data/concurso36-procedural-taxonomy-judicial-ac-dual-lens-20260829.json`  
**Mandatory no-regression supplement:** `CONCURSO36_CONTROLLING_CONCLUSIONS_29AUG2026.md`  
**Machine no-regression overlay:** `assets/data/concurso36-controlling-conclusions-supplement-20260829.json`

## Mandatory read order

Before relying on any older generated continuity dataset, validator, timeline or public page, read:

1. `CONCURSO36_UNITARY_CRIMINAL_FIRST_GOVERNANCE.md`;
2. this dual-lens file;
3. `CONCURSO36_CONTROLLING_CONCLUSIONS_29AUG2026.md`;
4. `assets/data/concurso36-controlling-conclusions-supplement-20260829.json`;
5. the procedural-taxonomy machine control named above; and
6. `CHATGPT_START_HERE_CONCURSO36_COURT_RECORD.md` for the current court-record/P0 denominator.

Where an older generated object conflicts with the controlling conclusions, the supplement governs until a later dated primary-source correction record expressly supersedes it.

## Purpose

This file prevents two opposite forensic errors:

1. assuming that an official/judicial act is regular, neutral or benign merely because an official actor performed it; and
2. treating an adverse, inconsistent or legally disputed act as proof of criminal guilt merely because it benefited an adverse party or harmed LPB/Aweswell.

The project must instead use a **dual lens** every time it reviews the judge, the Insolvency Administrator (AC), the Community/CAM/private perimeter, or the interaction between them.

## Declared position that must not be erased

Gil Marer/Aweswell's position is that the concerns and allegations regarding the insolvency judge concern a **cumulative pattern of multiple alleged acts and omissions**, not one isolated resolution and not only the 4 June 2018 Auto. The allegation set includes lack of neutrality, asymmetric treatment, possible institutional shielding/neutralisation, abuse or overreach of concursal powers and potential judicial prevaricación. Complaint/supervisory material has also been pursued before the CGPJ and other competent routes.

That allegation history is part of the intelligence context. **It is not itself proof that the judge, AC or any private actor committed a crime.** Every new primary document must be checked against the allegation history to determine whether it corroborates, contradicts, narrows, disproves or materially changes an allegation.

## Mandatory two-pass method

### Pass A — dry law / black-letter procedural classification

Before discussing motive, bias or criminal significance, identify the exact historical procedural class and statutory route:

- `INCIDENTE_CONCURSAL`
- `MODIFICACION_TEXTOS_DEFINITIVOS`
- `ACLARACION_CORRECCION_COMPLEMENTO`
- `PLAN_LIQUIDACION`
- `RECURSO_REVISION`
- `CALIFICACION`
- `ESCRITO_O_INFORME_DE_SECCION`
- `REALIZACION_ADJUDICACION_IMPLEMENTACION`
- `TESTIMONIO_FIRMEZA`

An important or contested act is **not** automatically an `incidente concursal`.

Former LC art. 192 made the incident the channel for questions arising during the insolvency **where the Ley Concursal did not prescribe another procedure**. If the statute supplied another route, use the correct route in the repository even if the act is central to a criminal allegation.

### Pass B — adversarial judge/AC/private-actor review

After classification, test without a presumption of benign regularity:

1. statutory/jurisdictional authority;
2. procedural route and possible route substitution;
3. notice and actor-specific knowledge;
4. consistency with the actor's own prior position/decision;
5. evidentiary selectivity or adoption of one party's calculation;
6. equality of arms and meaningful contradiction;
7. availability/loss/reduction of review or appeal;
8. protection of the masa activa, productive unit and third-party/extraconcursal rights;
9. beneficiary and harm;
10. implementation and causation;
11. repetition and cumulative pattern;
12. legal alternative explanations and corrective/protective counterweights;
13. subjective element where a criminal hypothesis requires it.

For judicial prevaricación, CP art. 446 requires more than a wrong/adverse ruling: the investigation must address an unjust resolution and knowledge (`a sabiendas`).

## Locked controlling corrections — apply before arithmetic

The following are no-regression controls and are developed fully in `CONCURSO36_CONTROLLING_CONCLUSIONS_29AUG2026.md`:

- **20 January 2017** is a genuine definitive-text modification comparator showing formal statutory machinery existed and was used.
- **8 February 2018** changes creditor identity, not the recorded fixed amount: **CHANGE OF CREDITOR ≠ CHANGE OF CREDIT**; the primary rule is “not change the amount”. The recognized special-privilege comparator is **€8,194,877.88 + €857,373.81 = €9,052,251.69**.
- **4 June 2018** is a liquidation-plan clarification/implementation bridge using **€11,887,314.33 + €1,278,518.03 = €13,165,832.36** for the operative liquidation/payoff/bid calculation; it is not itself a demonstrated statutory modification of the definitive texts.
- Amounts must be kept in five separate columns: **recognition → accrual → liquidation/payment → adjudication/set-off → modification**. Numerical continuity is not procedural authority.
- The correct unresolved amount question is whether approximately €13.166m operated lawfully only as payoff/liquidation arithmetic while recognized credit remained approximately €9.052m, or whether a further statutory final-text modification was required. A complete later amount-increase bridge is **NOT LOCATED**, not proved never to have existed.
- IA knowledge of the 7-June allegations is supported by the **8-June “He llamado a Borja…”** record; the remaining question is what the IA then verified, protected, reported, filed and accounted for.
- On **13 June**, counsel accepted that Mercantile should be informed and a protective pleading had been drafted; the canonical ledger ends **FORMAL FILING RECEIPT NOT LOCATED**. That is an instruction/performance tension, not proof of criminal motive.
- Mercantile Court nº1 **did respond** to the 2-May Arrecife exhorto; Arrecife records receipt on **11 June** and the **13-June Auto** joins it into DP 1132/2018. Mandatory banner: **WE KNOW A RESPONSE EXISTED. WE DO NOT YET HAVE ITS CONTENT.** The pre-7-June response must not be presumed to address the 7-June event.
- The **27-April-2017 LexNET** establishes that the convenio was presented. Do not say liquidation occurred because LPB failed to present one. The official/certified 28-June Junta record and complete IA evaluation remain open.
- For June 2018 use historical **former Ley Concursal Article 176**; TRLC Article 465.6 is later numbering/mapping and must not be used anachronistically.
- The lender track is continuous entity-by-entity but must be audited loan-by-loan, separating principal, contractual/default interest, security ceilings, enforcement costs, calculation dates and procedural use.

## 4 June 2018 — locked procedural position

The 4 June 2018 Auto is **not to be classified as an `incidente concursal`** unless a separate primary incident file proves otherwise. The signed order says that it **clarifies** the 16 April 2018 liquidation-plan approval and states that no appeal lies against the clarification under LEC art. 214.4.

It is also **not to be recorded as a formal amendment of the `texto definitivo`** merely because it uses a different debt number.

Primary comparator:

- **8 February 2018** — formal definitive-text modification/succession order. Judge Alberto López Villarrubia states that the assignment changes creditor identity **but not amount**, for which the definitive texts control. Located special privilege: **€857,373.81 + €8,194,877.88 = €9,052,251.69**, plus contingent enforcement costs without their own quantified amount.
- **4 June 2018** — plan clarification. The judge relies on two CAM balance-fixing instruments dated 17 May rather than requiring the AC to carry out the prior calculation requested by LPB, and uses **€11,887,314.33 + €1,278,518.03 = €13,165,832.36**, plus continuing default interest within the respective mortgage-security limit, as the operative amount a rival bidder would have to improve.

The repository must therefore keep two propositions separate:

1. secured interest may have accrued or been exigible under former LC art. 59 to the extent of the real security; and
2. that does **not automatically establish that the definitive creditor-list amount was formally amended** through arts. 97/97 bis or that clarification could lawfully perform the function of another procedure.

### Required 4 June adversarial tests

- Was the quantitative mechanism within the narrow scope of LEC 214/LOPJ 267 clarification, or did it alter an essential term?
- If any definitive-list amount changed, where is the art. 97/97 bis application/report/transfer/order and exact before/after entry?
- Why were CAM's own 17 May instruments treated as the operative amount without the prior AC calculation LPB requested?
- Did use of a non-appealable clarification materially affect LPB/Aweswell's contradiction/review position?
- How does the order reconcile with the same judge's 8 February rule that assignment does not change amount?
- What exactly does former LC art. 59 lawfully explain, mortgage by mortgage and within each security ceiling?
- What economic/competitive effect did the threshold have on funded exits, rival bidding and the estate, and what intervening causes existed?
- Does the act form part of the alleged cumulative pattern when tested with 7/13 June 2018 knowledge/protection, 24 February 2021, the two 15 October 2021 Autos, January-February 2022 finality/testimonio acts and implementation — or do contrary/protective decisions materially weaken that inference?

The user position remains categorical: **Gil Marer/Aweswell disputes that the 4 June clarification was legally capable, by itself, of creating a lawful approximately €13m definitive-text credit or liquidation-payoff/set-off amount.** Preserve this as the party's position while independently testing the law and evidence.

## Definitive-text change gate

Never write that the `texto definitivo` was lawfully changed because a later document contains another number. Require:

`application/request + statutory ground + AC report + transfer/opposition + incidente if the applicable route requires it + signed order expressly modifying + exact before/after entry + service/remedy/finality + corrected list/inventory/implementation binding`.

A debt certificate, AC calculation, liquidation-plan order, clarification, testimony, deed recital, set-off calculation or accounting entry is not automatically a definitive-text amendment.

## Verified incidentes concursales currently located

This is a **located denominator, not a certified docket**.

1. **Piece 7 / 2012 — LPB v Garrigues.** `Pz Incidente concursal impugnación inventario/lista de acreedores (Art 96.4)`. LPB sought exclusion of recorded Garrigues ordinary/subordinated claims. Judgment 1 April 2016 dismissed the claim and did not impose costs because of legal/factual doubts.
2. **Piece 8 / 2012 — AC v LPB and Monterecco Sun Park, S.L.** `Pz Incidente concursal Resolución contrato por incumplimiento (Art 62 LC)`. Judgment 24 November 2015 granted termination for non-payment, vacating/eviction relief, €2,733,923.64 plus interest/future rent and costs.

### Community-fee family — do not force the taxonomy

The primary order currently controlled is the **20 January 2017 Article 97 bis definitive-text modification**, following LPB's position, a favorable AC report, transfer and no located opposition. It expressly orders modification of the definitive texts concerning the Community's contingent ordinary pre-insolvency fee credit.

That makes it an important comparator. But until a separate primary incidental docket/claim/admission/decision is located, **do not relabel this 97 bis modification itself as an `incidente concursal`**. If another Community-fee incident exists, add it when it is source-bound.

This distinction strengthens, rather than weakens, the user position: the record demonstrates that formal definitive-text modification had an identifiable statutory route and an order expressly saying that the texts were modified.

## Why the following are not placed in the incidente-concursal list

- 4 June 2018 clarification Auto — clarification/liquidation-plan route.
- approval/clarification of the liquidation plan — specific liquidation route.
- reposición/apelación/queja/revisión/nullity — remedy/review routes.
- calificación — its own statutory section/procedure.
- ordinary section filings and AC reports — submissions/inputs unless they generate a separately admitted incident.
- 2021-22 offer/improvement/adjudication — liquidation realisation/implementation unless a dispute was separately opened as an incident.
- testimonios/finality instruments — certification/implementation.
- later correction/clarification applications — LEC/LOPJ correction/completion route.

**Exclusion from the incident list is not exclusion from the criminal-led chronology.** These acts remain material and can be more important than an incident for the cumulative bias/prevaricación/neutralisation hypothesis.

## CGPJ / complaint-history linkage

Maintain a separate complaint-history lane. The connected corpus includes CGPJ Diligencia Informativa 169/2026 and related supervisory/appeal material, plus separate 2026 complaint material concerning alleged judicial conduct in Concurso 36/2012. Do not publish a complaint as proof of its merits. Do link each controlled judicial act to the allegations it potentially supports, contradicts or changes.

## Improved autonomous continuation prompt

> Continue Concurso 36/2012 under `CONCURSO36_UNITARY_CRIMINAL_FIRST_GOVERNANCE.md`, this dual-lens protocol, `CONCURSO36_CONTROLLING_CONCLUSIONS_29AUG2026.md`, the machine no-regression overlay and `CHATGPT_START_HERE_CONCURSO36_COURT_RECORD.md`. For every material act, first classify it under the historical procedural law, then run the actor-specific criminal/prosecutorial test. Keep **recognition → accrual → liquidation/payment → adjudication/set-off → modification** separate; preserve **CHANGE OF CREDITOR ≠ CHANGE OF CREDIT**; treat 20-Jan-2017 as the genuine final-text comparator, 8-Feb-2018 as creditor succession without amount change, and 4-Jun-2018 as a liquidation-plan clarification/implementation bridge to €13,165,832.36 rather than a demonstrated final-text amendment. Recover the complete later amount-increase bridge if it exists; otherwise keep it NOT LOCATED. Preserve IA knowledge by 8-Jun, the counsel instruction→draft→receipt-not-located chain, the 27-Apr-2017 convenio filing, historical LC Art.176 numbering, and the Mercantile response to Arrecife as known to exist but missing in content. Keep the dedicated Arrecife↔Mercantile page and the existing continuity/court-record pages mutually linked. Treat authority before arithmetic as mandatory for every Community occurrence, keep Pieza 7 and Pieza 8 separately controlled, reconcile the lender track loan-by-loan, close the P0 primary-source families, repair rather than bypass CI failures, publish only through PR/CI/merge/Pages verification, and leave a dated deletion-safe closeout. Do not turn serious allegations into adjudicated criminal findings without competent judicial authority.

## Deletion-safe rule

Future threads must recover this governance from the repository. Do not depend on the originating chat for the declared position, taxonomy, 4 June comparator, five-column credit model, Arrecife response rule, IA/counsel knowledge chains or P0 queue.