Product Operations Module — live product activation, handoffs and learning

Design only. Preserve canonical ownership: Comms owns campaign and publishing direction; Production owns creative execution and QA; Approvals owns external authorization; Sales owns qualification and agreements; Farm ERP owns field truth and fulfilment context; Finance owns invoices/payments; Portfolio & BA receives material new initiatives. Do not create a project, new public claims, external campaign, production asset, lead, agreement or payment during design.

Authorize a read-only additive-link feasibility assessment only. Confirm the exact canonical links for product → Product Action Request → Comms campaign → Production/Approvals → enquiry/Sales/Farm/Finance outcomes. Preserve all existing module owners and approval gates. Do not implement, create a project, trigger campaigns, publish, contact leads, create agreements or write financial/farm records until a subsequent implementation decision.

Authorize the narrow first-release charter only: Product index/workbench; additive Product Action Request/Link records; product attribution on Comms campaigns and canonical website enquiries; read-only outcome aggregation; Farm Explorer Live and SiteSense Lite validation. Exclude direct publishing, lead outreach, Sales/Farm/Finance writes, bulk migration and generic workflow/task/CRM replacement. Establish and approve a G3 baseline before implementation.

Implement only the approved first-release charter and G3 baseline: additive Product Action/Link records; product attribution on Comms campaigns and website enquiries; Products index/workbench; read-only outcome aggregation; Farm Explorer Live and SiteSense Lite proof chains. Preserve module ownership and existing approval guards. Any scope extension requires a governed change decision.

Execution, monitoring and production-safe validation completed for the narrow additive first release. No public activation, publishing, buyer, Farm ERP or Finance record was created.

Daniel explicitly approved G5 after reviewing the Farm Explorer Live workbench. Release accepted. Product remains live in Product Operations; delivery project proceeds to G6 closure and benefits review.

Daniel explicitly approved G6. Close the delivery project. Product Operations remains the durable operating module; Farm Explorer Live remains a live product and its benefits review remains scheduled for 2026-11-13.

## Problem GAB now has 17 live products delivered by completed projects, but the Product Registry is a catalogue rather than a working operating home. The follow-up actions that make a product valuable—public activation, commercial conversion, service readiness, evidence maintenance and benefits review—are distributed across valid owner modules. A CEO or agent cannot open a product, identify the next action, begin the right governed workflow and see the returned outcome in one traceable place. ## Root cause The registry, operational-feedback loop and module workflows exist independently. The current OS has no reusable product-level action/request object and no product-to-campaign linkage. F

## Feasibility assessment — 2026-08-13 ### Existing usable spine - `products` is the enduring product registry and is already linked to `operational_feedback`, operational transitions and benefits reviews by `product_id`. - `comms_campaigns` is already the stable Comms parent for strategy, posts, Production grouping, approvals through posts, and engagement. - `production_requests` already retain `campaign_id` in metadata; Production can therefore inherit product context through a campaign rather than receive a duplicate product field. - Sales, Farm and Finance already own buyers, supply agreements, farm truth, invoices and buyer payments. Invoice/payment chain can remain derived from an agr

## Benefits and measures Product Operations should reduce the time and ambiguity between a product becoming live and its first governed operating action. Measures: live products with explicit owner/next action; time from action request to accepted destination record; campaign-to-product attribution completeness; product actions with a returned outcome; product-attributed qualified demand/agreements; feedback and benefits-review ageing. Baseline is not yet measured and must be recorded before performance claims.

## Product Operations Module — First Release Charter ### Sponsor and owner Sponsor: Daniel Nsowah. Delivery owner: GAB OS / Product Operations. ### Objective Create a reusable internal Product Operations capability so every live product has a discoverable operating home, an explicit next action, governed cross-module follow-up and product-level learning—without duplicating the operating modules that execute the work. ### Scope in 1. Product index and product detail/workbench for live registry products. 2. Additive Product Action Request and Product Action Link records. 3. Reusable action types: Public Activation, commercial follow-up, service readiness, evidence/data-quality review, benef

Projects close at G6 and register only enduring products. Product Operations then becomes the ongoing cross-module coordination surface. Historical project tasks are preserved as lineage but are never the product tracker. Existing live products are onboarded incrementally, beginning with Farm Explorer Live and one EIRAS product. No bulk migration of operational records; links are added only through governed, additive paths.

G5 accepted Product Operations as the persistent operating home for Farm Explorer Live and other delivered products. Product Operations coordinates bounded action requests and typed links only; Comms, Production, Approvals, Sales, Farm and Finance retain their source authority.

Projects close at G6 and register only enduring products. Product Operations then becomes the ongoing cross-module coordination surface. Historical project tasks are preserved as lineage but are never the product tracker. Existing live products are onboarded incrementally, beginning with Farm Explorer Live and one EIRAS product. No bulk migration of operational records; links are added only through governed, additive paths.