A Bearadise

Integrity

Additionality is supported: the validation report confirms an investment test and the VVB (Ruby Canyon Environmental) verified additionality. A 10% buffer pool is documented, and the baseline is project‑specific with a reassessment in 2016. However, integrity is weakened by an historical notification of an error that caused over‑issuance of risk credits (Rainforest Alliance received notice from VCSA dated 18 September 2012) and by contradictory records on reversals and leakage (see contradictions). These reliability issues reduce confidence in baseline/leakage treatment and permanence.

Transparency

The project has substantial documentation (49 documents including monitoring and validation reports, PDD and issuance records) and a recent monitoring period covering 2022. Nevertheless, transparency suffers because key metrics are inconsistent between documents: total emissions reductions claimed vs verified vary widely across validation reports and monitoring reports, and leakage deductions changed between earlier and later reports. These contradictions make it hard to trust reported totals without further reconciliation.

Claim Safety

There is a clear over‑crediting risk signalled by conflicting ERR figures (for example, a claimed total of about 100,789 in an earlier validation report vs a later verified total of 32,675). Leakage treatment changed (20% in a 2019 validation vs 0% in a 2023 validation), which materially affects crediting. On the positive side the project is reported as not CORSIA‑eligible and a buffer pool exists, but CCP status is not stated, so dual‑claim risk cannot be fully excluded.

Documentation

Documentation breadth and recency are good: the merged record includes validation and monitoring reports, PDD and issuance documents with the latest monitoring report dated 2023‑12‑06 and validation material up to 2023‑12‑21; extraction confidence is high. However, multiple contradictions across documents (leakage, ERR totals, FPIC/grievance, safeguards, benefit sharing) indicate inconsistent recordkeeping or unresolved issues, lowering the documentation score.

Overall

I privileged the most recent validation and monitoring validation reports when resolving contradictions (generally the validation report dated 2023‑12‑21 and the monitoring report dated 2023‑12‑06) because they are later and likely to reflect corrections. Examples: for verified ERR I privileged the 2023 validation figure of 32,675 over earlier higher claims; for leakage deduction I privileged the 0% stated in the 2023 validation over 20% reported in 2019. Contradictions remain material: reversal events were reported in 2012 (error in risk credit calculation) but later monitoring reports state no reported reversals; FPIC and grievance presence/absence also conflict between older monitoring and newer validation documents. These unresolved inconsistencies reduce the project’s overall score to a mid level (5.5).