Agriculture Full Strategic Acceptance

This runbook validates the full Agriculture strategic plan after the MVP passes. It focuses on runtime behavior that proves the system can scale from small farms to managed plantations, aggregation/export, offline field teams, IoT-assisted operations, and market-linked settlement.

The rule remains the same: Agriculture provides context and operating model guidance. Shared primitives own the records and financial consequences.

Current Closure Path

The MVP acceptance path is considered complete only after both backend and browser tests pass:

1. Backend procedure smoke proves project/WBS funding, approved source work, obligation, payment batch, provider success callback, GL posting, and fund reports.
2. Browser smoke proves tenant users can complete the same flow from the UI without route leakage, raw internal IDs, duplicate primitive screens, or report drilldowns that navigate away.
3. Full strategic acceptance then adds offline sync, telemetry incidents, market snapshots, produce-to-buyer settlement, and cross-funding closure.

The backend work-to-payment acceptance pack has been proven with a committed trace where:

• project funds were received and posted to GL
• approved field work generated an approved obligation
• the obligation generated a controlled payment batch line
• duplicate source-line insertion was rejected
• the payment batch executed successfully
• payment GL posted with project, WBS, fund, source document, payee, and amount in narration
• Project Fund Position and Project Fund Utilization reports reconciled received, committed, paid, GL-posted, and available values

Acceptance Pack Summary

Code	Pack	Owning primitives	Completion proof
OFFLINE_EVIDENCE	Offline capture to approved evidence	Document Transactions, Events, Files, Reporting	Rejected sync rows create no impact; approved evidence supports field activity, attendance, obligations, or report facts.
TELEMETRY_INCIDENT	Telemetry to incident review	Resources, Events, Reporting, Integrations	Raw pings stay outside ERP; summaries, stale-device alerts, incidents, and review outcomes are reportable.
MARKET_PRICE_SETTLEMENT	Market snapshot to settlement price	Pricing, Contracts, Document Transactions, Reporting	Settlement or buyer sale retains snapshot, formula, premium/discount, override reason, and approval trail.
WORK_TO_PAYMENT_GL	Approved work to payment and GL	Events, Documents, Projects & WBS, Payments, GL	Approved work or attendance generates controlled obligations, payment batch lines, GL, and fund reporting.
PRODUCE_TO_BUYER_SETTLEMENT	Produce intake to buyer settlement	Inventory, Inspections, Billing, Documents, Payments	Lot, grade, stock movement, dispatch, buyer sale, settlement, and payout reconcile through reports.
FUND_CROSS_FUNDING_CLOSURE	Fund position and cross-funding closure	Projects & WBS, Document Transactions, GL, Reporting	Cross-funding exposure opens from approved request and closes after approved settlement posting.

Pack 1: Offline Capture To Approved Evidence

1. Create an offline work pack for a field team, device, location, work order, and expiry window.
2. Download or simulate the device package.
3. Capture activity, attendance, attachment, GPS/time, and idempotency references.
4. Upload the sync batch.
5. Review duplicates, conflicts, missing evidence, and attachment queue status.
6. Reject at least one row and approve at least one row.
7. Confirm approved rows create or update only the allowed downstream record.
8. Run the Agriculture Offline Sync Exceptions report.

Expected result: rejected rows remain auditable and cannot create payment, stock, billing, or GL impact. Approved rows preserve source device, operator, idempotency key, evidence link, and reviewer.

Pack 2: Telemetry To Incident Review

1. Register a field device or operational resource through the shared resource/location setup.
2. Assign it to a farm, field, checkpoint, worker group, vehicle, equipment, or project context.
3. Capture or simulate telemetry summaries such as stale device, low battery, sensor exception, camera incident, or checkpoint variance.
4. Convert an exception into a reviewable incident or report row.
5. Attach evidence links or external references where available.
6. Resolve or escalate the incident.
7. Run Agriculture Telemetry Summary and Agriculture Incident Review reports.

Expected result: ERP stores summaries, exceptions, incidents, evidence links, and decisions. ERP does not store high-frequency raw pings or live video as operational truth.

Pack 3: Market Snapshot To Settlement Price

1. Configure commodity, grade, UOM, currency, and market reference policy.
2. Import or simulate a market price snapshot with provider, market, quote time, currency, UOM, and confidence metadata.
3. Review and approve the snapshot.
4. Apply the snapshot to a pricing rule, buyer sale, producer contract, or settlement statement.
5. Apply grade premium/discount, currency/UOM conversion, transport/processing deductions, and any override reason.
6. Approve the settlement or sale.
7. Run Agriculture Market Price Snapshots and settlement/margin reports.

Expected result: market data is reference data until approved. Settlement and buyer-sale records retain the snapshot, formula inputs, override reason, and approver.

Pack 4: Approved Work To Payment And GL

1. Create or approve a field activity, worker attendance sheet, work completion report, or spending request.
2. Confirm the source record carries project, WBS/work package, fund source, cost category, payee/counterparty, and amount.
3. Generate a payment obligation from the approved source.
4. Open the shared Payments batch workspace.
5. Add selected approved obligations.
6. Confirm batch lines inherit source, project, WBS, fund source, payee, and remaining amount.
7. Attempt a duplicate source line and an over-remaining amount line.
8. Validate, approve, execute, and post GL where configured.
9. Run Project Fund Position and Project Fund Utilization reports.

Expected result: invalid lines are rejected by runtime validation. Valid lines reconcile from source document to payment batch, GL, and fund report.

Pack 5: Produce Intake To Buyer Settlement

1. Record harvest or produce intake from field/farm/source party context.
2. Perform grading or inspection through the shared inspection/QC primitive.
3. Create stock movement, lot, warehouse/bin, or dispatch context through Inventory.
4. Create buyer sale or dispatch document.
5. Create settlement statement or payable where applicable.
6. Generate payment batch from approved settlement/payable obligation.
7. Run intake, quality, dispatch readiness, settlement payable, and payment reports.

Expected result: lot, quality, stock, buyer sale, settlement, and payout references reconcile without Agriculture owning duplicate Inventory, QC, Billing, or Payment screens.

Pack 6: Fund Position And Cross-Funding Closure

1. Create and approve a funding source and fund receipt for Project A.
2. Create an approved cross-funding request where Project A funds Project B.
3. Confirm exposure opens in Project Cross-Funding Exposure report.
4. Create a cross-funding settlement from the exposure.
5. Approve and GL-post the settlement document.
6. Confirm the domain callback closes due-from and due-to exposure.
7. Re-run Project Fund Position, Utilization, and Cross-Funding Exposure reports.

Expected result: cross-funding is managed by Projects & WBS and GL, not Agriculture. Agriculture can reference the project context, but exposure and settlement reporting remain shared.

Drilldown Rules

Every report used in these packs must follow these rules:

• Drilldowns open an in-place dialog inside the report viewer.
• Row actions must not silently route away from the report unless the action is explicitly a navigation action.
• Hidden row context can carry internal IDs, but visible report columns should prefer document numbers, project codes, party names, account references, and status labels.
• Expired drilldown tokens should show a clear regenerate-report message.

Final 100% Criteria

The full Agriculture strategic plan is complete when:

1. MVP smoke test passes.
2. All six acceptance packs pass.
3. Capability state is visible tenant-side and managed only in Platform Admin.
4. Agriculture pages route to shared primitive owners instead of duplicating primitive management.
5. Offline, telemetry, market, field-work, produce, fund, payment, GL, and report paths preserve source traceability.
6. Negative controls prevent unapproved evidence, duplicate obligations, over-remaining payments, unfunded spending, and report drilldowns that lose context.

Strategic Non-Negotiables

• Service capabilities are managed from Platform Admin -> Companies -> Manage Services.
• Tenant Agriculture pages may show capability status, but should not mutate service activation or seed-pack state.
• Project funding, WBS, cross-funding, due-to/due-from accounting, and fund reports are shared Projects & WBS behavior.
• Payments are shared Payments behavior. Agriculture can contribute source documents and fund context, but should not own a separate payout engine.
• Reports run through the shared Reporting module. Agriculture can seed report definitions, filters, datasets, cards, drilldowns, and dashboards.
• Inventory, inspections/QC, POS, billing, operational items, and GL stay in their canonical modules.
• Drilldowns open dialogs inside the report viewer unless the user explicitly chooses a navigation action.
• User-facing screens should show names, codes, document numbers, account numbers, and business references, not raw database IDs.