parks

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

1. 1. Ticket Meta-Configuration

• Project: PROJECT BUNDINIPARKS
• Tracker: Feature
• Status: New
• Priority: High
• Target Version: v1.0-Alpha
• Assigned To: Salman

---

1. 2. 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) using one centralized MySQL database.

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

---

1. 3. Required Redmine Environment Custom Fields
   To track this sprint's environment impact correctly inside Redmine, the system administrator must verify the existence of the following Custom Fields (Administration -> Custom fields -> Issues):

1. Target Subdomain * Format: Key/value list * Possible Values: `parks.bundini.co.uk`, `recreation.bundini.co.uk`, `percentages.recreation.bundini.co.uk`
2. Impacted DB Tables * Format: Text * Default Value: `garden_events, plants, bed_action_logs, operational_cycles`
3. Deployment Node * Format: String * Description: Target AWS infrastructure node ID.

---

1. 4. Granular Technical Requirements

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

• Objective: Allow volunteers on the public-facing map site to execute fast context-logging without administrative panel access.
• UI Element: Build a dynamic frontend modal window triggered on clicking a specific physical `bed_id` within a `garden_event` map layout.
• Fields & Actions: * [Weeded] Action: A simple click toggle that sets an array flag. * [Watered] Action: A click toggle that auto-generates a dynamic ISO timestamp. * [Comment] Input: A character-limited text box (max 500 characters) stripped of raw HTML tags to prevent cross-site scripting (XSS).

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

• Objective: Provide internal park managers with an explicit checklist matrix categorized structurally by physical location.
• UI Layout: A clean, CSS-Grid table matching the exact data matrix of Maryan's Park. Group all assets hierarchically under their parent `garden_id`.
• Matrix Checkbox Actions per Plant ID: * `[ ] Planting`: Triggers a lifecycle status initialization (`status = 'planned'`). * `[ ] Pruning`: Appends a dedicated pruning metadata flag to the backend logs. * `[ ] Propagating`: Flags the vegetative plant for lineage reproduction tracking. * `[ ] Commenting`: Opens a hidden inline text node when checked to record field health logs.

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

• Objective: Handle high-concurrency form submissions safely without leaving orphaned records.
• API Route: `POST /v1/events/log-matrix`
• Database Constraints: * The execution block must run inside an isolated MySQL Transaction Connection Pool (`START TRANSACTION;`). * If any single action check in the frontend matrix arrays fails validation, trigger a complete `ROLLBACK;`. * On clean data ingestion, perform an immediate `COMMIT;` and automatically write a tracking row to the `operational_cycles` table under the status tag `'Do'`. This provides the automated bridge to feed real-time performance analytics metrics upstream to the `percentages` subdomain dashboards.

---

1. 5. Dev Sandbox Verification Data Matrix
   Use this array map during localized sandbox testing to replicate Maryan's Park:

Parent Location	Bed Identifier	Target Flora Inventory	Permitted Matrix Checkboxes
:---	:---	:---	:---
Maryan Park (Garden 1)	`B1`	3x Lavender, 1x Rose Bush	Planting, Pruning, Commenting
Maryan Park (Garden 1)	`B2`	2x Boxwood Shrubbery	Pruning, Propagating
Maryan Park (Garden 1)	`B3`	5x Fern Clusters	Weeded, Watered, Commenting