How a partner report becomes a stage change.

This console is published rather than kept internal so that the verification step can be inspected alongside the ledger it produces. The controls below are inert and write nothing.

File a partner report

Donation batch

Only batches with a settled transaction appear here.Planting project

Must already exist in the project register.

Trees confirmed planted

From the report. Never an estimate.Report date

The date on the document, not today.

Evidence reference

A permanent link. The report is pinned rather than hosted on our own server.

No donation has settled, so there is nothing to report against. Batches appear here once a transaction confirms.

Submission needs 2 of 3 multisig signers.

Selected batch

The donation register is empty. Once the reforestation address has sent its first batch, it appears here with its transaction hash and awaits a partner report.

Metadata diff

Fill the three report fields and preview to see exactly which keys change. Frozen attributes are shown greyed so a reviewer can confirm the write touches nothing it shouldn’t.

No back-dating

The report date is taken from the document. Where a report arrives late, both dates are shown.

No partial credit

A batch is either reported or it is not. Figures are never pro-rated across periods.

No silent edits

Every write is a new version carrying a pointer to the one it supersedes, so corrections remain visible.