# ClaimPrism Pro roadmap

## Product direction

ClaimPrism Pro is the operational review layer for teams that need to manage environmental-marketing claim risk across WordPress and WooCommerce. It must remain a risk-screening and human-review workflow, not a legal-compliance verdict engine.

The Free edition remains useful for detection and prioritisation. Pro adds workflow, accountability, reporting, history and team-scale operations.

## 0.8.0 — Pro Review Workflow

Goal: make Pro materially more valuable than Free by turning findings into a managed review queue.

### Premium capabilities

1. Review status per finding
   - `open`
   - `in_review`
   - `resolved`
   - `accepted`

2. Internal notes
   - private reviewer notes attached to a finding
   - WordPress user and timestamp recorded

3. Assignment
   - optional WordPress user assignment
   - optimised for store managers, marketing reviewers and compliance collaborators

4. Review history / audit trail
   - status changes
   - assignment changes
   - note creation
   - actor and timestamp
   - recent per-finding history visible directly in the Pro queue

5. Advanced filters
   - severity
   - content type
   - rule
   - review status
   - assigned reviewer
   - keyword/content search

6. Pro export
   - export the filtered queue
   - include status, assignee and latest review metadata
   - respect the active rule filter
   - preserve CSV-injection protection

### Free/Pro boundary

Free keeps:
- product/page/post scanning
- editor checks
- background full-site scans
- finding context and official evidence links
- evidence-expiry alerts
- review-priority score and queue

Pro adds:
- review workflow state
- notes and assignments
- audit trail
- advanced operational filters
- workflow-aware exports

Premium implementation must remain behind Freemius premium-only guards so Freemius can strip it from the WordPress.org Free package.

## Implemented data model for 0.8.0

Detection rows remain separate from human-review state so rescans cannot erase review metadata.

### `wp_claimprism_review_state`

One current workflow record per finding fingerprint:

- `fingerprint` char(64) primary key
- `status` varchar(20), default `open`
- `assignee_id` bigint unsigned
- `note` text
- `updated_by` bigint unsigned
- `updated_at` datetime

The fingerprint is used instead of the transient finding row ID so workflow state can survive rescans when the same detected finding is recreated.

### `wp_claimprism_review_events`

Append-only audit log:

- `id` bigint unsigned primary key
- `fingerprint` char(64)
- `event_type` varchar(32)
- `old_status` varchar(20)
- `new_status` varchar(20)
- `assignee_id` bigint unsigned
- `note` text
- `actor_id` bigint unsigned
- `created_at` datetime

Indexes cover fingerprint, event type and created time.

## Persistence rule

A rescan currently replaces finding rows for a post. Therefore Pro workflow metadata keys off `fingerprint`, not the finding row ID. If an identical finding reappears, its review state survives. If the content changes enough to create a new fingerprint, it is intentionally treated as a new finding.

## UX target

The ClaimPrism dashboard is an operational queue rather than a static report:

- filter bar above Findings
- visible review-state badge
- assignee
- compact review action
- recent per-finding event history with actor and timestamp
- export respects the active filters

The default experience remains simple for single-site merchants, while Pro scales to agencies and internal marketing/compliance teams.

## 0.9.x — Monitoring and reporting

After the review workflow is stable:

- scan-to-scan change tracking
- new / recurring / removed findings
- evidence repository and evidence-expiry workflow
- configurable scheduled scans
- periodic review reports
- bulk actions
- deeper WooCommerce catalogue operations

## 1.0 Pro target

ClaimPrism Pro 1.0 should provide a complete human-review workflow for professional ecommerce teams:

- accountable review ownership
- audit trail
- evidence management
- historical trend/reporting
- team-scale operations
- agency-friendly workflows

Multi-site or externally hosted central management should be evaluated after the single-site workflow is proven commercially, rather than being a prerequisite for 1.0.

## Release discipline

Development for 0.8.0 happens on a feature branch. Do not deploy it to Freemius and do not change the WordPress.org review package until the workflow is implemented, automated CI is green, and the complete Pro workflow is manually validated in Local. Metadata/changelog preparation is the last release-candidate step after that manual validation.
