Reasoning starts with the ecological function required on site, then species are selected to answer the specific needs
PerenOS reasons from site conditions to plant communities
1. Context input
2. Pressure inference
3. Functional priorities
4. Community proposal
South-facing urban fringe, clay-loam, 0.4 ha, England
Drought stress (high), UHI (medium), pollinator corridor (high)
Drought buffering, soil stabilisation, late nectar provision
Achillea, Eryngium, Stipa, Centaurea · 47 spp · BNG +12%
01
Entry at any stage of the project
PerenOS enters at whatever stage ecological reasoning remains open — before spatial decisions, after them, or alongside design software. Practitioners can define communities, take outputs into their CAD tool, and return to refine the design.
02
Community-scale reasoning, landscape-scale composition
The design unit is the plant community. Species interactions, succession, and competition are modelled within each one — riparian edge, meadow zone, woodland margin — and reasoned about across the landscape as a whole.
03
Project accompaniment after handover
PerenOS stays with the project through establishment, monitoring, and adaptive maintenance. Where conditions diverge from projections, adaptations are proposed against the original reasoning record.
04
The output is a defensible argument
Every output carries the reasoning that produced it: site inputs considered, trade-offs resolved, uncertainties named at the level of confidence available. The reasoning record itself is the documentation.
05
Practitioner judgment stays central
PerenOS proposes, justifies, and surfaces uncertainty — but the practitioner holds the design decision. Outputs are arguments to evaluate, not specifications to accept.