CEA case-study archive
These records preserve attributed historical CEA context. Each page states what the available public source establishes and what it does not establish about current Platform use, delivery responsibility or measured outcomes.
Archive publication rule
A record remains public only with a source, attribution label, publication permission and an explicit evidence boundary. Historical domain context is not automatically product implementation evidence or an external validation result.
- Record type
- Publication-gated evidence record
- Product relationship
- Current product implementation and validation are reported separately on Product Status and Evidence & Validation.
- Evidence scope
- Names, data and results from selected private-beta organisations remain confidential unless publication is separately authorised.
The archive can establish attributed project context and the content of a permitted historical source. It does not by itself establish a current customer relationship, Platform use, delivery scope, quantified outcome or external product validation.
Attributed domain context
The named place, period, facility or project context supported by the permitted source.
Source and permission
The public source, attribution and publication permission supporting the record.
Relationship boundary
What the record establishes about Crop Urbanis involvement and what must not be inferred.
Outcome boundary
Whether a measured result, method and validation scope are actually published.
Illustrative Platform workflow
This example uses synthetic or sanitised information to explain how the Platform structures evidence, requirements, comparisons, design cases with reproducible calculations and reviews. It demonstrates workflow logic; it does not represent a named customer or project result.
Product direction
How evidence informs the Platform workflow
The internally usable workflow structures the recurring information and decision patterns behind CEA projects: project data, requirements, supplier intelligence, design cases with reproducible calculations, expert review, controlled delivery and handover. Historical project records do not imply current Platform use.
Project data and requirements
The Platform records project entities, requirements, constraints, alternatives, source documents, assumptions, versions and permissions.
Supplier intelligence and scenarios
source-linked supplier information, explicit units, capacity, crop cycles, CAPEX/OPEX and sensitivities support comparable controlled scenarios.
Review, delivery and handover
professional review by a named role, approvals, unresolved issues and defined project outputs packages keep accountability and the delivery boundary explicit.