Farm management¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
| Vertical | Farm |
| Prototype reference | Farm prototype (ConnectSoft.DesignPrototypes) |
| Managed edition | SelfOperated (D33, D34) |
| Data residency | tenant-region (D31) |
| Catalog | Examples catalog · Vision-to-Production path for this vertical |
Business problem¶
Field operations, inputs and yields are tracked on paper and phones with no connection to compliance or sales.
Product intent¶
Fields, crops, tasks, inputs, harvests and compliance records with offline mobile capture.
What the Factory makes different here: offline-first mobile from the Mobile Blueprint with queued writes.
Vision-to-Production path for this vertical¶
| Step | Factory platform | Agents | Blueprints |
|---|---|---|---|
| Vision and product plan | Agent Mesh, Control plane | Product Manager Agent, Mobile Developer Agent | vision |
| Architecture and domain | Template & Library (BC-02) | Enterprise Architect Agent | service, module, database |
| Experience | Template & Library, Factory Studio UX track | UX Designer Agent, Frontend Developer Agent | mobile |
| Recipe and generation | Template & Library (BC-15), Agent Mesh, Tools & MCP | Product Manager Agent, Mobile Developer Agent, Backend Developer Agent, QA Agent | module plan from the context map |
| Quality | Observability (BC-22), DevOps / GitOps | QA Agent | test |
| Delivery and provisioning | DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) | DevOps Agent, Infrastructure Architect Agent | — |
| Operations | Product Fleet Operations (BC-35..37) | — | handover, objectives, rollouts, incidents, off-boarding |
Delivery workflows exercised: research-and-ux-ui-design-workflows.
Generated product shape¶
C4Context
title Farm management system context
Person(user, "Users", "Farm users and operators")
System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
System_Boundary(product, "Farm management") {
System(ctx_Fields, "Fields", "fields, crops, seasons")
System(ctx_Operations, "Operations", "tasks, inputs, equipment")
System(ctx_Harvest, "Harvest", "yields, lots, sales")
}
Rel(user, ctx_Fields, "uses through the product gateway GW-07")
Rel(factory, ctx_Fields, "descriptor, health, rollouts, incidents, off-boarding")
Bounded contexts¶
| Context | Responsibility | Published events |
|---|---|---|
| Fields | fields, crops, seasons | SeasonStarted |
| Operations | tasks, inputs, equipment | TaskCompleted |
| Harvest | yields, lots, sales | LotRecorded |
Modules and templates¶
| Module | Template | Notes |
|---|---|---|
| Microservice ×3 | connectsoft-microservice |
|
| Mobile app | connectsoft-maui-base |
|
| Admin shell | connectsoft-blazor-shell |
|
| Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product. |
Prototype reference¶
Farm prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.
Operations as a managed product¶
Self-operated; upgrade offers through the fleet inventory.