Umay Ana's Carbon Diary currently focuses on documenting sustainability-related farm practices with contextual evidence such as activity type, date, location and photos. The next technical step is not to invent a carbon credit. It is to make those records structured, traceable and interoperable enough to support future measurement, reporting and verification workflows with qualified external partners.
MRV readiness is a data-design problem before it becomes a carbon-accounting problem. If a farmer's activity is stored only as an unstructured sentence — “I used a cover crop last autumn” — it may be useful as a personal note but difficult to audit, aggregate or map to a future methodology. If the same activity is stored as structured evidence with provenance, time and context, it can become a more useful input to a formal MRV workflow later.
Umay Ana's Carbon Diary is intentionally an evidence-log MVP. Its role is to help farmers build a history of sustainability-related and regenerative agricultural practices. Current product positioning should remain conservative:
It does not currently constitute a certified MRV system, an approved CRCF methodology, a carbon-credit registry, an independent verification body or a legally authoritative carbon calculator.
Carbon Diary records evidence of farm activity. It does not currently calculate verified tonnes of CO₂e, issue carbon credits, certify CRCF compliance or replace a recognised certification scheme.
Formal carbon-farming systems need historical evidence. Baselines, activity periods, monitoring, additionality, quantification and audits all depend on knowing what happened, where and when. A farmer who begins documenting practices before a finance or certification opportunity appears may have a stronger evidence history than a farmer attempting to reconstruct several seasons retrospectively.
This does not mean an old app record automatically qualifies under a future methodology. It means the record can reduce one class of information gap: the absence of any structured history.
A useful Carbon Diary record should answer a simple set of questions without claiming more than it knows:
A normalized practice category: cover crop, reduced tillage, compost application, nutrient-management action or another supported practice.
A timestamp and permissioned location or farm-area reference, at an appropriate precision for the use case.
Provenance showing whether the record is farmer-entered, system-derived, partner-supplied or externally validated.
Photo, document, sensor, invoice, laboratory or remote-sensing references — each with its own source and integrity metadata.
Self-recorded, evidence attached, externally validated, quantified or certified — never collapse these into one label.
Initially none. Later, a partner can map the record to an accepted methodology and specify required missing fields.
The following is a proposed future-facing interoperability model, not a claim about the current production database. Its purpose is to show how a Carbon Diary event could remain useful as Umay Ana integrates with external MRV, finance or certification partners.
{
"record_id": "practice_record_...",
"record_type": "sustainability_practice",
"practice": {
"category": "cover_crop",
"methodology_mapping": null
},
"farm_context": {
"crop": "wheat",
"location_reference": "permissioned_location",
"area_reference": null
},
"evidence": {
"recorded_at": "ISO-8601 timestamp",
"photo_refs": [
"evidence_photo_..."
],
"source": "farmer_recorded",
"provenance": "umay_ana_carbon_diary"
},
"verification": {
"status": "self_recorded",
"external_validator": null,
"quantification_status": "not_quantified",
"certification_status": "not_certified"
},
"future_mrv_fields": {
"baseline_reference": null,
"monitoring_plan_reference": null,
"methodology_id": null,
"measurement_refs": [],
"audit_refs": []
}
}The most important design decision in this example is the use of explicit null or “not quantified” states. A missing quantification should never be silently converted into zero tonnes, and a self-recorded practice should never be represented as externally verified.
Instead of treating every record as equally trustworthy, Umay Ana can use an evidence-state model. This can support both user clarity and institutional data quality.
This maturity model is intentionally conservative. A record can move upward only when new evidence or external validation exists. The app should never upgrade a record's status merely because time passed or because an AI model is confident.
The EU Carbon Removals and Carbon Farming Certification Framework is useful as a design reference because it separates documentation from formal certification. Regulation (EU) 2024/3012 requires certified carbon removals and soil-emission reductions to satisfy quality criteria and to be independently verified. It requires quantification to be relevant, conservative, accurate, complete, consistent, transparent and comparable, with uncertainty treated conservatively.
For carbon farming, the Regulation also addresses baselines, additionality, storage, monitoring, liability and sustainability. Certification applications require an activity plan and monitoring plan, and certification bodies conduct independent audits. This is far beyond what a farmer-facing diary alone should claim to perform.
On 10 July 2026, the European Commission announced adoption of CRCF certification methodologies for three carbon-farming activity types, including agriculture and agroforestry on mineral soils. The Commission's methodology page describes these as a major implementation step and states that recognised certification schemes will be able to apply the methodologies once the delegated regulation enters into force.
This matters technically because Umay Ana can now design interoperability around a more concrete European direction rather than an abstract idea of “carbon farming.” The correct goal is not to imitate the methodology inside the app. It is to store enough structured evidence that a recognised scheme, project developer or MRV provider can determine whether and how a record maps to the applicable methodology.
A practice such as reduced tillage can exist in Umay Ana without being CRCF-eligible. Only an external mapping to an applicable methodology — with its baseline, additionality, monitoring and verification requirements — can determine formal eligibility.
Under Article 9 of the CRCF Regulation, an operator or group of operators applying for certification submits an activity plan and a monitoring plan. The certification body then audits the submitted information and compliance with the relevant requirements.
That gives Umay Ana a concrete integration target. A future partner-facing export does not need to say “this farm is certified.” It can say:
That is much more useful to an MRV provider than a single opaque “carbon score.”
One of the most important fields in a future institutional architecture is not the agricultural value itself, but its source.
| Source type | Example | How it should be interpreted |
|---|---|---|
| Farmer-entered | “Cover crop planted on 15 October.” | A user declaration; useful but not independently verified. |
| App-derived | Crop or practice classification generated by AI. | A model output carrying version, confidence and limitations. |
| Photo evidence | Time-linked farm image. | Visual evidence requiring integrity and contextual checks. |
| Weather source | Observed rainfall or temperature. | External contextual data with provider and timestamp. |
| Remote sensing | Vegetation or land-cover indicator. | Third-party derived evidence with spatial/temporal resolution limits. |
| Laboratory / sensor | Soil carbon, moisture or other measurement. | Measurement evidence whose method, calibration and chain of custody matter. |
| Verifier / certifier | Audit result or certificate reference. | Formal external status under the named scheme or methodology. |
This approach also helps avoid a common AI-data problem: a derived model output being mistaken for an observed fact.
For a practical next-generation Carbon Diary, a lightweight core could be separated from optional program-specific fields.
Record ID, user/farm reference, crop/system reference, practice category, timestamp.
Permissioned location, field/parcel reference where available, precision metadata.
Photo/document references, capture time, source, integrity metadata and notes.
Start/end dates, quantity or area where relevant, management details and repeated actions.
Status, verifier, method, timestamp, audit reference and exceptions.
Named methodology, version, required fields, missing fields and mapping status.
Keeping the methodology layer separate is important. If CRCF, a bank program, an insurer or a voluntary project uses different rules, the underlying evidence should not need to be rewritten. The platform can map the same evidence object to different program adapters where legitimate.
Institutional value is determined by quality, not the number of rows in a database. A future dashboard should therefore show data-quality indicators alongside practice counts.
Possible quality dimensions include:
Farm sustainability data can reveal commercially sensitive information. Precise location, production practices and financial-program participation should therefore be shared under role-based and purpose-limited controls.
A sensible architecture can separate:
The CRCF Regulation itself anticipates interoperability of carbon-farming databases and identifies key information that may be connected with agricultural parcel systems, including management practices, activity dates, certificate code, certification body and certification scheme. That reinforces the value of structured identifiers and interoperable records.
A future integration can be designed as an adapter rather than a hard-coded certification engine:
The external partner remains responsible for methodology application, formal quantification, audit and certification unless and until Umay Ana separately becomes qualified for a specific regulated or recognised role.
The CRCF framework explicitly allows groups of operators and aims to reduce administrative and financial burden, especially for small-scale operators. The Commission is also exploring buyer-club structures intended to create economies of scale for carbon-farming projects.
This aligns with an important platform opportunity. A single small farmer may not justify expensive project-development and verification costs. A digital platform can potentially help organise cohorts by geography, practice, crop and evidence completeness, making it easier for qualified project developers or schemes to assess whether aggregation is viable.
That does not make the platform a carbon-market intermediary automatically. It means structured data can reduce coordination cost.
Not every institutional use requires a certified tonne of carbon. A green-finance program may need evidence that specific eligible investments or practices were implemented. An insurer may be interested in documented resilience practices. A supply-chain program may need practice adoption evidence.
For these use cases, the output can be a controlled evidence summary:
{
"farm_reference": "permissioned_partner_reference",
"program": "example_green_agriculture_facility",
"practice_records": 14,
"evidence_attached": 11,
"externally_validated": 4,
"quantified_carbon": null,
"certified_units": null,
"data_quality": {
"completeness": 0.86,
"provenance": "mixed",
"methodology_readiness": "partial"
},
"important_note": "Evidence summary only — not a carbon certificate."
}This is deliberately less glamorous than a “carbon score,” but far more defensible.
From a product perspective, the next MRV-readiness milestones are relatively concrete:
Carbon Diary becomes more valuable when it stops being viewed as a feature called “carbon” and starts being viewed as a longitudinal agricultural evidence system. The carbon-farming market is one potential consumer of that evidence. Green finance, insurance, agricultural support, supply-chain sustainability and farm-management history are others.
The long-term defensibility does not come from claiming to calculate carbon earlier than everyone else. It comes from having a large, permissioned, structured and increasingly verifiable history of what agricultural practices were recommended, recorded, evidenced and validated across crops, places and time.
The CRCF framework provides a useful European reference model for designing data that can later participate in recognised carbon-farming workflows.
Umay Ana's Carbon Diary is designed to evolve from a farmer evidence history into an interoperable sustainability-data layer — without confusing self-recorded activity with certified climate outcomes.