Intake and permission boundary
Project context, authorised users, roles, source files, versions and permitted purpose.
Technical Architecture
Crop Urbanis Platform — Technical Architecture
A concise partner-facing technical record aligned with the Technology page and current Product Status register.
Technical principles
Preserve distinctions that affect trust.
A source claim is not automatically a project fact; a reproducible calculation is not a guaranteed outcome; AI assistance is not professional approval.
Logical architecture
Six functional layers from permitted source to structured output.
Provenance-preserving extraction
Candidate values and statements with source, location, wording, raw value and extraction state.
CEA project model
Project objects, requirements, constraints, assumptions, alternatives, owners and dependencies.
Rules and design-case services
Conversions, completeness checks, calculations, sensitivity and explicit gates.
Review, change and approval
Corrections, issues, professional reviews, approval states and affected work.
Output and integration boundary
Comparisons, assumption registers, design-case summaries, decision records and supported exports.
CEA project data model
Source, project, model, review and control records remain connected.
Source records
Document, version, location, wording and permitted use.
Project records
Requirement, constraint, assumption, alternative, issue, risk and decision.
CEA objects
Site, crop, production target, environmental requirement, equipment, utility and supplier.
Model records
Owner, version, method, inputs, units, validity scope, tests and limitations.
Control records
Organisation, role, permission, dependency, approval state and audit event.
Material-value record
A technical value travels with its source and operating conditions.
The record retains original statement, source reference, raw value, normalised value, operating conditions, evidence status, extraction confidence, review status, validity scope, version and dependencies.
Confidence and authority
Extraction confidence, evidence status, review status and uncertainty are different fields.
- Extraction confidence
- Did the process read the source correctly?
- Evidence status
- What kind of evidence supports the value?
- Review status
- Has a responsible person accepted, corrected, rejected or left it unresolved?
- Uncertainty
- How uncertain is the real-world quantity even after correct extraction and review?
Bounded AI tasks
AI works on defined information tasks, not professional authority.
May assist
Classification, candidate extraction, terminology mapping, permitted retrieval and draft comparison or clarification text.
Task envelope
Named task, permitted sources, output schema, source references, model and task version, validation rules and review state.
Does not own
Source authority, supplier warranties, engineering or agronomic approval, commercial selection, project acceptance or live control.
Model governance
Calculations are versioned; design cases remain conditional.
Rules and completeness checks
Required fields, units, thresholds, compatibility and project gates.
Engineering and production models
Capacity, utilities, environmental loads, crop cycles and resource assumptions.
Techno-economic models
CAPEX, OPEX, revenue assumptions, sensitivity and design-case comparison.
Expert assumptions and AI outputs
Remain separately identified, owned, reviewed and limited.
Evaluation
Evaluate components separately before expanding the workflow.
Document extraction
Critical-field precision and recall, source-location accuracy, unit error, missing-field recall and reviewer time.
Retrieval and AI assistance
Source accuracy, context coverage, unsupported-output rate, abstention and reviewer outcomes.
Data and calculations
Schema coverage, dimensional consistency, reproducibility, benchmark deviation and affected-record detection.
End-to-end workflow
Time to reviewable comparison, unresolved critical inputs, review effort, decision-record completeness and critical-error escape.
Deployment boundary
Internal workflow first; organisational hardening next.
Current internal workflow, organisational hardening and later integration work are reported as separate states. The public brief contains no cloud-credit allocation page.
- Current internal workflow
- Versioned project records, permitted source files, document processing, rules, calculations, reviews and structured outputs.
- Organisational hardening
- Authentication, roles, organisation separation, monitoring, data lifecycle, backups, recovery and support.
- Later integration
- Project-system integrations, operating-data feedback, image and sensor workflows under defined conditions.
Interoperability
Structured for integration without claiming standards compliance.
Stable identifiers, explicit units, source references, versions and structured records preserve future mapping and export options. No certification or native compatibility is claimed.