# ClaimPrism Product State

_Last maintained: 2026-08-16_

## Current commercial baseline
- Current Pro development baseline: `0.10.0`.
- WordPress.org submitted package: `0.6.0` — **frozen while under review**.
- Main product repository: `parsec66/claimprism`.
- Strategic roadmap issue: `#28` — evolve ClaimPrism into a Claim Intelligence & Governance Platform.

## Recently completed and merged
- ZEODEC dashboard redesign foundation PR `#27`.
- Governed Claim foundation PR `#31`.
- Governed Claim Review/Evidence bridge PR `#33`.
- Claim Graph Usage Intelligence PR `#35`.
- Approved Claim Library foundation PR `#37`.
- Semantic Drift Detection foundation PR `#39`.
- Approved Wording Reuse foundation PR `#41`.
- Claim Source Location foundation PR `#45`.
- Claim Governance workspace v1 PR `#49` plus Usage baseline follow-up PR `#51`.
- Main ClaimPrism dashboard dark ZEODEC alignment PR `#53`.
- Commercial 1.0 first-run onboarding PR `#56`.
- Free-to-Pro dashboard value path PR `#58`.
- Zero-findings post-scan copy correction PR `#60`.
- Review Priority wide-screen layout correction PR `#62`.

The current product therefore exposes the accumulated governance foundations through a dedicated Claim Governance workspace, uses a consistent dark-dominant ZEODEC visual language, explains first-run value before the first scan and presents the Pro value path to Free users after first-run without obscuring Free scan results.

## Validated capabilities

### Core / dashboard
- Environmental marketing claim scanning for WordPress/WooCommerce.
- Risk prioritization and findings dashboard.
- CSV/export paths already present in Free/Pro as implemented.
- Full-store resumable scan flow.
- ZEODEC dark dashboard visual system aligned with Claim Governance.
- Semantic severity colors remain consistent across dashboard and workflow surfaces.
- First-run onboarding appears before useful scan history exists and disappears when the first scan starts.
- Free post-first-run users receive a compact Pro value path explaining Review Workflow, Evidence, Monitoring/Reports and Claim Governance.
- Zero-findings post-scan state correctly distinguishes a completed scan from a never-scanned site.
- Review Priority layout fills the available wide-screen information track without an artificial right-side gap.

Existing scan/dashboard flows were previously exercised locally. Do not re-run broad scan regressions unless changed code can affect them.

### Pro Review Workflow
- Review-state persistence keyed to finding fingerprint.
- Reviewer assignment and internal notes.
- Append-only review/audit history.
- Server-side filtering, search and pagination.
- Filtered Pro CSV export.
- Bulk review actions preserving audit history.

### Evidence Repository
Validated lifecycle capabilities include:
- create evidence;
- edit/update evidence;
- remove evidence;
- source URL and/or valid WordPress attachment validation;
- `updated_by` / `updated_at` audit metadata;
- filtering and empty states;
- status display;
- expiry/review dates and lifecycle alerts.

Focused local validation already completed for create, edit, update audit, remove, expiring/expired routing and clear state. Do not repeat those exact tests unless evidence lifecycle code changes.

### Monitoring / scheduling / reporting
- Pro monitoring storage separated from core findings and review state.
- New / recurring / removed scan classifications.
- Full scan-run boundaries and recent comparison views.
- Finding-level monitoring filters and history drill-down.
- Configurable scheduled scans.
- Operational 7 / 30 / 90 day review reports.
- CSV report export.

### Governed Claim foundation — Pro
The persistent governance foundation provides:
- stable governed claim record resolved from scanner `claim_key`;
- multiple finding fingerprints/usages mapped to one governed claim;
- existing occurrence fingerprints unchanged;
- lifecycle states restricted to `detected`, `evidence_required`, `in_review`, `approved`, `monitoring`, `re_review`;
- owner, approved wording/date, re-review date and actor/timestamp metadata;
- append-only lifecycle transition audit events;
- premium-only runtime.

The lifecycle is internal governance workflow, not legal/compliance certification.

### Governed Claim Review/Evidence bridge — Pro
A read-only aggregate layer composes existing primitives without duplicating them:
- one governed claim resolves all linked usage fingerprints;
- current review state and histories are read from Review Workflow;
- evidence rows are read from the existing Evidence Repository source of truth;
- aggregate summary exposes usage count, review-state counts and evidence totals/expiry coverage;
- no Review/Evidence data is copied into Governed Claim storage.

### Claim Graph v1 — Usage Intelligence — Pro
- One governed claim resolves all known usage edges/fingerprints.
- Each edge includes content ID/type/title where resolvable.
- First/last seen timestamps come from governed usage history.
- Presence is classified as `current`, `removed` or defensive `unknown`.
- Review Workflow status and Evidence Repository count are composed per usage.
- No new graph persistence table exists.

Presence semantics:
- `current`: fingerprint still exists in scanner findings source of truth;
- `removed`: fingerprint no longer exists but referenced WordPress content still exists;
- `unknown`: ClaimPrism cannot prove either state.

### Approved Claim Library foundation — Pro
- Governed Claim `approved_wording` remains the source of truth.
- Only `approved` or `monitoring` claims with non-empty approved wording are eligible.
- Entries expose stable ID, detected/approved wording, owner, approval/re-review and update metadata.
- Claim Graph and Review/Evidence summaries are composed live.
- Search/filter/order are deterministic.
- No duplicate Approved Claim persistence table exists.

`approved` remains an internal governance state, not a legal/compliance certification.

### Semantic Drift Detection foundation — Pro
- Deterministic comparison of approved wording against live scanner wording.
- Current usage classifications: `exact`, `normalized_match`, `changed`.
- Case/punctuation/whitespace normalization is explainable and deterministic.
- Removed/unknown usages are excluded from live drift evaluation.
- Missing approved wording returns typed defensive errors.
- No drift persistence table and no lifecycle auto-transition.

Drift is an internal governance signal, not a legal/compliance verdict.

### Approved Wording Reuse foundation — Pro
- Eligible governed claims must be `approved` or `monitoring` with non-empty approved wording.
- Target content must exist and use a supported editable post type/status.
- Proposal payload contains approved wording plus governance and target metadata.
- Existing usages, Claim Graph summary and drift context are composed live.
- The service remains read-only: no WordPress content/meta/media mutation or publishing API calls.

### Claim Source Location foundation — Pro
Current findings can be resolved to precise scanned WordPress source fields without changing fingerprints.

Supported source families:
- post title;
- post excerpt / WooCommerce short description;
- post content / WooCommerce long description;
- supported SEO title/description meta keys;
- featured and WooCommerce product-gallery image alt text.

Resolved locators expose:
- unchanged finding fingerprint and content identity;
- source type and concrete source key/reference;
- deterministic occurrence index;
- normalized character offsets;
- source signature hash for future stale-locator validation.

Ambiguous or unresolved locations are surfaced defensively rather than guessed.

### Claim Governance workspace v1 — Pro
The dedicated Pro workspace exposes the accumulated governance primitives in one coherent ZEODEC surface:
- Governed Claim Registry;
- lifecycle status, owner and re-review metadata;
- usage locations from the Customer Claim Graph;
- precise source location context;
- Semantic Drift state;
- Review/Evidence summary;
- approved wording context;
- controlled reuse proposal affordance.

The workspace does not create parallel governance persistence, auto-transition lifecycle states, mutate content or present compliance/legal verdicts.

Visual validation completed for:
- Review & Evidence summary geometry;
- Usage locations deterministic column geometry;
- shared baseline for Presence / Source Location / Review-Evidence / Drift badges.

### ZEODEC UI/UX state
Claim Governance and the main ClaimPrism dashboard share the same dark-dominant visual system:
- dark application surfaces inside the WordPress shell;
- white/silver hierarchy and cool-gray secondary copy;
- flat controls without decorative shadows;
- semantic status colors retained;
- green primary actions retained for validated CTAs;
- normalized HIGH severity badge token across Pro Review Workflow and Findings.

Presentation changes remain isolated from business/domain logic.

### Commercial 1.0 onboarding and value communication
Validated Commercial 1.0 UX work now includes:
- first-run onboarding with a simple Scan → Review findings → Pro governance explanation;
- first-scan CTA reusing the validated scanner action;
- explicit wording that findings are screening signals, not certification/compliance verdicts;
- Pro-specific Claim Governance affordance in licensed mode;
- Free post-first-run value panel explaining what Pro adds;
- preserved Free/Pro gating during local licensing/deactivation validation;
- corrected zero-findings post-scan guidance;
- corrected Review Priority wide-screen geometry.

## Customer documentation / packaging state
Commercial 1.0 packaging/documentation readiness is being synchronized under issue `#63`.

Current direction:
- `readme.txt` must describe the current Free/Pro product rather than only the older review/monitoring baseline;
- `README.md` must reflect the merged governance foundations and current Commercial 1.0 state;
- `docs/GETTING-STARTED.md` provides the customer path from installation through scan, findings and Pro governance workflow;
- release readiness must distinguish already validated UX/CI from final candidate checks still pending;
- CI packaging architecture is already coherent and does not currently require redesign.

## CI baseline
Repository CI includes:
- **WordPress.org Plugin Check**;
- **WordPress + WooCommerce integration**.

Governed Claim, aggregate, Claim Graph, Approved Claim Library, Semantic Drift, Approved Wording Reuse and Claim Source Location behavior are covered in WordPress Playground/runtime integration tests.

Recent Commercial 1.0 documentation/UI work has preserved green CI before merge where applicable.

## Local test environment
Primary local site:
- `claimprism-test-restored`

Additional clean Commercial 1.0 validation site:
- `claimprism-onboarding-test`

Direct dashboard path when WooCommerce is not installed:
- `/wp-admin/tools.php?page=claimprism`

Existing local findings/test data may be reused for targeted testing. Avoid unnecessary rescans.

## WordPress.org review
- Submission date: 2026-08-08.
- Submitted artifact/version: `0.6.0`.
- Do not replace or mutate the submitted package while review is pending unless the Plugins Team requests a change.

## Current immediate priority
The governance workspace, dark dashboard alignment, first-run onboarding, Free-to-Pro value communication and observed Commercial 1.0 empty-state/layout blockers are complete.

**Current priority: Commercial 1.0 packaging, customer documentation and final release-readiness definition.**

Immediate goals:
1. Keep customer-facing documentation aligned with the actual 0.10.0 Free/Pro product.
2. Ensure a new customer can understand install → scan → findings → Pro workflow/governance without external explanation.
3. Keep release gates honest: mark only validated CI/UX checks complete and retain genuinely pending final-candidate checks.
4. Harden only issues that materially block first commercial use; avoid speculative feature expansion.
5. Keep automatic content replacement out of scope until a later explicit-write slice validates a fresh source signature/locator immediately before a user-confirmed mutation.

Do **not** jump directly into Evidence Strength/Jurisdiction work until Commercial 1.0 readiness is complete and the current product is commercially understandable and shippable.

## Strategic product direction
ClaimPrism evolves from a green-claim scanner into a persistent governance system around each claim:

`Detected → Evidence required → In review → Approved → Monitoring → Re-review`

Long-term defensible assets:
1. Regulatory Knowledge Graph.
2. Customer Claim Graph.
3. Decision / approval history.
4. Integrations and workflow embedding.

## Do not retest list
Unless relevant code changes, do not ask for repeat manual verification of:
- evidence create/edit/remove lifecycle;
- evidence reference validation;
- evidence update audit metadata;
- expiring/expired evidence alert routing and clear state;
- basic scan/dashboard behavior previously exercised;
- 0.8.0 Review Workflow validation;
- 0.9.0 Monitoring/Reporting validation;
- Claim Governance Review & Evidence summary geometry;
- Claim Governance Usage locations alignment/baseline;
- dark ZEODEC dashboard visual pass and HIGH badge normalization;
- first-run onboarding disappearance after the first scan starts;
- Free-to-Pro dashboard value panel presentation;
- zero-findings post-scan copy;
- Review Priority wide-screen layout fill.

Manual testing should target only newly changed behavior or final release-candidate gates that genuinely require a fresh candidate.