Dulus
An AI agent for your desktop and terminal, on any model you choose. Hosted models run on Fuel, paid in $DULUS.
翻訳待ち
No updates detected yet. GitHub releases will appear here.
ISIC Rev.5 0129: Growing of other perennial crops -- cloud-itonami farm operations coordination actor
翻訳待ち
Loading the full README.
Read the full README ↗ISIC Rev. 5 0129 — Growing of Other Perennial Crops
A distributed actor for autonomous, compliant coordination of perennial-crop cultivation operations: cultivation-lot intake → field/crop-condition survey → treatment/scheduling advice → bamboo-culm/cork-bark/ornamental-pruning/spray field work → cultivation-record logging → compliance audit. Sealed LLM advisor; independent Governor enforcement; append-only audit ledger. Not field-equipment operation. Harvester/sprayer/applicator operation remains exclusive to licensed field-equipment operators, and this actor never finalizes a pesticide-application decision on its own.
ISIC 0129 is the residual (not-elsewhere-classified) perennial-crop growing division: perennial crops not already covered by 0121 (grapes), 0122 (tropical/subtropical fruits), 0123 (citrus fruits), 0124 (pome and stone fruits), 0125 (other tree and bush fruits and nuts), 0126 (oleaginous fruits), or 0127 (beverage crops). This build's concrete illustrative crops are bamboo (culm harvest), cork oak (bark stripping), and ornamental/nursery trees and shrubs — all grown and OWNED by the operator, which is what distinguishes ISIC 0129 from ISIC 0161 (support activities for crop production), a contractor that never owns the crop it services.
This actor coordinates the operator's own perennial-crop cultivation operations:
Out of scope:
The Governor is the separation-of-powers enforcement. It never trusts the advisor's confidence for anything safety- or compliance-relevant, and it always wins over the advisor.
:op-not-allowed) — includes
any proposal that would amount to direct field-equipment control:effect other than :propose
(:effect-not-propose):cultivation-lot-not-registered):no-spec-basis):evidence-incomplete):applicator-license-expired) —
only for chemical-application crop-operation types:sprayer-calibration-overdue) — only for chemical-application
crop-operation types:pre-harvest-interval-violated) — only
for chemical-application crop-operation types:restricted-entry-interval-violated) — only for chemical-application
crop-operation types:wind-speed-exceeded) — only for chemical-application crop-operation
types:buffer-zone-violated) — only for chemical-application crop-operation
types:field-equipment-or-pesticide-decision-blocked) — a HARD, PERMANENT
block, defense-in-depth against every op:crop-health-flag-unresolved):already-logged, double-commit guard):log-cultivation-record — the one real actuation event this actor
performs, always requires human sign-off even when the Governor is
otherwise clean:flag-crop-health-concern — a crop-health concern (pest, disease) is
never auto-resolved by advisor confidence alone:order-supplies above governor/supply-order-cost-threshold-usd
(5000 USD)governor/confidence-floor, 0.6)Closed allowlist — the advisor may only ever propose these four
operation types, all :effect :propose:
:log-cultivation-record — Log planting/harvest batch, yield/quality
data, plus safety/compliance parameters, into cultivation records (always
requires human sign-off):schedule-field-operation — Propose planting/harvesting/pruning
field-operation scheduling for the operator's own cultivation lot
(routine, low risk):flag-crop-health-concern — Surface a crop-health concern (e.g.
pest infestation, disease); always escalates:order-supplies — Propose fertilizer/pesticide/equipment
procurement (escalates above the cost threshold)This is the beginning of the README. Read the rest at the original. Read the full README ↗
:schedule-field-operation when clean, or
:order-supplies at or below the cost threshold