Skip to main content
Menu

Evidence, validation and project experience

This page classifies what a public record can establish. Domain experience, implemented product behaviour, research evidence and external validation have different meanings and publication thresholds.

Evidence classes

Four records that must not be conflated.

Each class answers a different question about the company, product or method.

Domain experience

Attributed CEA project or operating context that establishes relevant domain work, not automatic Platform use or product performance.

Product implementation evidence

Observable software behaviour or a repeatable internal workflow, reported through the canonical Product Status register with its limitations.

Research evidence

A defined question, protocol, baseline, metric, result and limitation. Product implementation alone is not a research result.

External project or product validation

A documented organisation, independent reviewer or external study has evaluated a stated project or product scope with publication permission.

Public record

A published claim carries its classification and boundary.

A public evidence record identifies the source, attribution, relationship to Crop Urbanis, scope, method where applicable, date, permission, limitation and whether the record concerns domain experience, product implementation, research or external validation.

Classification rule
A record is published only under the strongest evidence class actually supported; architecture and status descriptions are not presented as measured outcomes.
Naming rule
An organisation is not named as a customer, beta participant, collaborator or partner without documented permission.

Current external-validation status

No public external Platform-validation result is currently published.

Current implementation status and research questions are reported on their canonical pages. They should not be interpreted as an external performance result.

Canonical records

Follow the page that owns the claim.

Product Status

Implementation, limitations, availability and next validation.

Open related record

Case-study archive

Attributed historical records with explicit relationship and publication boundaries.

Open related record

Discuss a defined validation or project context.

Begin with high-level non-confidential context and the evidence class you expect the work to establish.