Application design.
Site-specific application and carrier design matched to terrain and hazard.
No two jobs get the same recipe.
A released batch is not yet a treatment. At this step we reconcile the batch, the ground and the constraints of the job into something a crew can install, and the same platform ends up producing two very different jobs.
We build each pilot around the site: asset type, terrain, treatment objective, safety requirements, testing protocol, and regulatory pathway. No secured site, landowner, buyer, permit, or partner is implied by this page.
The site sets the design.
We build each pilot around the site: asset type, terrain, treatment objective, safety requirements, testing protocol, and regulatory pathway. A design has to answer to those seven inputs, and they differ from one job to the next.
The carrier is how the culture arrives intact.
Carrier design covers what the culture travels in and how it is delivered onto the material or the ground. Liquid culture makes a treatment applicable across terrain; the carrier turns that into a method for one slope or one pile.
Terrain governs what water does.
Hyphae physically enmesh soil particles and organic matter, and contribute compounds that hold those aggregates together. Aggregate structure governs how much rain enters a slope and how much runs across it, so slope, surface and drainage bear on where an application goes and how it is placed.
Two protocols, two hazard pictures.
Post-fire work is designed against erosion, runoff, sediment, and debris risk on burned ground. Pre-fire work is designed against the woody residuals created by fuel-reduction and vegetation-management work.
The hazard at a site also sets what is safe to ask of a crew, and step 04 works within that.
This describes how applications are designed. It is not a description of a completed deployment, and no site, agreement, or approval is claimed here.