Designed
The behaviour and acceptance boundary are specified.
Product status
Current Platform implementation and validation status.
This page distinguishes implemented software behaviour, internal use, organisational deployment, research evidence and later roadmap work.
Last reviewed:
The core Platform workflow is implemented and internally usable. Use in a selected organisational beta scope is recorded separately; production hardening remains incomplete.
Implementation status vocabulary
Implemented internally
The behaviour exists in the internal code and workflow.
Internally usable
The behaviour can be used by Crop Urbanis for its intended bounded workflow.
Used in a selected beta scope
Use has been recorded in a specifically agreed organisational beta scope.
Production-hardened
Operational controls, reliability and administration meet the defined production threshold.
Under active development
Work is being implemented or hardened but has not reached the next status.
Planned later extension
The capability is not part of the current implementation boundary.
Capability implementation register
Each capability maps to one current status and states its observable behaviour, limitation and next validation.
Project baseline and requirements
Internally usable- Intended behaviour
- Project baseline and requirements
- Observable now
- An internal user can create a project record, register permitted source material, record requirements, constraints, owners and unresolved questions, and prepare the baseline for review.
- Known limitation
- Coverage and reviewer agreement have not been published as an external validation result.
- Next validation
- Measure schema coverage and reviewer agreement across defined CEA decision contexts.
Supplier evidence and configuration comparison
Internally usable- Intended behaviour
- Supplier evidence and configuration comparison
- Observable now
- An internal user can register permitted supplier documents, retain source references, map selected claims to project requirements and prepare a comparison and clarification record for review.
- Known limitation
- Correct extraction or comparison does not verify supplier warranties, compliance or project applicability.
- Next validation
- Fix and run a benchmark for one document and equipment class with professional review.
Scenario and decision analysis
Internally usable- Intended behaviour
- Scenario and decision analysis
- Observable now
- An internal user can create conditional design cases from explicit assumptions, apply versioned calculations, compare sensitivities and prepare a reviewable decision record.
- Known limitation
- A reproducible design case remains conditional on its inputs and is not a forecast, guarantee or investment recommendation.
- Next validation
- Run benchmark and seeded-change tests on a limited calculation set and document reviewer outcomes.
Decision continuity
Under active development- Intended behaviour
- Decision continuity
- Observable now
- The current record preserves reviews, rationale, unresolved conditions and downstream requirements; dependency-based change-impact coverage is being extended.
- Known limitation
- Change-impact logic identifies potentially stale work; it does not determine or approve the revised technical conclusion.
- Next validation
- Measure affected-record recall, false affected-record rate and review-state correctness after seeded changes.
Validation and evidence boundaries
Internal use
Internal usability establishes that a bounded workflow can be performed; it does not establish customer adoption or production readiness.
Selected beta use
This status is assigned only to the capability and scope for which use is documented; it is not inherited by the whole Platform.
Production hardening
No capability is labelled production-hardened without a defined reliability, security, administration and support threshold.
Research is separate
Research questions and evaluation maturity are reported on the Research page and do not upgrade implementation status.
Organisational deployment hardening
Access and organisation controls
Authentication, organisation separation, roles, auditability and administration are being hardened for selected deployment scopes.
Reliability and data operations
Monitoring, backup, recovery, retention, export and deletion behaviour must meet the agreed organisational threshold.
Roadmap status
Current hardening work
Organisational controls, evaluation, reliability and repeatable deployment.
Later extensions
Broader integrations, operating-evidence workflows and cross-project learning only under governed evidence and data conditions.