parks

1. Subject: Feature Integration: Cross-Subdomain Dynamic Event & Plant Lifecycle Matrix Hub

1. Description

We need to implement an elegant, dovetailed connection between our public spatial mapping layer (parks.bundini.co.uk) and our internal manager governance system (recreation.bundini.co.uk). Salman's team is tasked with building the unified UI interface and backend API transaction handlers using our central MySQL database infrastructure.

Use the structural data layout of "Maryan's Park" (1 Garden, 5 Beds, 11 Plants) as our core development baseline and prototype layout.

1. Core Technical Requirements

1. 1. Public Event UI & Field Tracking Layer (parks subdomain)

• Build a dynamic view for active Garden Events.
• Implement rapid click-to-log action triggers for physical beds. Users must be able to log:
  - Weeded (Status change flag)
  - Watered (Timestamp flag)
  - Comment (Text string)

1. 2. Operations & Care Grid Matrix (recreation subdomain)

• Construct an interactive plant inventory grid grouped cleanly by Bed ID.
• For each plant row nested within a bed container, provide an explicit operational checkbox matrix for field workers:
  - [ ] Planting (Triggers lifecycle birth state)
  - [ ] Pruning (Logs maintenance activity)
  - [ ] Propagating (Tracks stock reproduction)
  - [ ] Commenting (Appends qualitative observation notes)

1. 3. Backend Atomic Sync Pipeline (api.bundini.co.uk)

• Develop a transactional API endpoint (`POST /v1/events/log-matrix`) to process incoming form payloads.
• Ensure all database operations execute inside an atomic MySQL transaction block:
  - Insert log lines to `bed_action_logs` for general bed actions.
  - Insert matrix row modifications for specific `plant_id` entries.
  - Automatically append a tracking row into `operational_cycles` under the 'Do' phase to alert regional managers.
  - Automatically pipe live data updates upstream to compute metrics for percentages.recreation.bundini.co.uk.

1. DB Schema References to Extend

• `garden_events` (ID, garden_id, title, event_date)
• `plants` (ID, bed_id, common_name, botanical_name, status)
• `bed_action_logs` (ID, event_id, bed_id, plant_id, action_type, notes)

1. Acceptance Criteria
   1. Submitting the public event matrix successfully modifies data across both the spatial log and manager operational logs simultaneously.
   2. Form failure safely rolls back the database state with no partial entries.
   3. UI functions without distortion or performance lags when loading up to 20 beds at a single event.