# ClaimPrism Roadmap

## Guiding objective
Build ClaimPrism into a **Claim Intelligence & Governance Platform** that becomes increasingly valuable and difficult to replace as customer claim, evidence and decision history accumulates.

## Phase 1 — Commercial 1.0
Target: a strong first commercial release, not an exhaustive platform.

### Completed foundations
- ZEODEC dark visual system across the main dashboard and Claim Governance workspace.
- Pro Review Workflow.
- Evidence Repository lifecycle and expiry alerts.
- Scheduled scans, monitoring and reporting.
- Governed Claim persistent identity and lifecycle foundation.
- Review/Evidence aggregate bridge.
- Claim Graph v1 usage intelligence.
- Approved Claim Library foundation.
- Semantic Drift Detection foundation.
- Approved Wording Reuse read-only proposal foundation.
- Precise Claim Source Location foundation.
- Dedicated Pro Claim Governance workspace exposing the accumulated governance model.

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

### Current priority — Commercial 1.0 readiness
Before expanding into new intelligence engines, make the current product commercially understandable, usable and shippable.

Priority areas:
- onboarding and first-run value communication;
- Free-to-Pro value communication and upgrade paths;
- packaging and customer-facing documentation;
- empty states and guidance for new users;
- focused hardening of real blockers to first commercial use;
- preserve the validated dark ZEODEC UI and existing Free/Pro boundaries.

Do not add speculative features merely to increase feature count.

## Phase 1.5 — Claim Graph expansion
Implemented foundation:
- group duplicate/reused claims across pages/products;
- track one governed claim across many live usage locations;
- Approved Claim Library;
- approved wording reuse proposals;
- semantic Claim Drift Detection;
- precise source locations.

Deferred until after Commercial 1.0 readiness:
- controlled editor execution using fresh verified source signatures and explicit human confirmation;
- richer claim usage visualization if product value justifies it;
- optional re-review orchestration built on explicit human action.

## Phase 2 — Intelligence
### Evidence Strength Engine
Classify claim support as:
- Strong
- Adequate
- Weak
- Missing
- Contradictory
- Expired

### Jurisdiction Engine
Initial scope:
- EU
- UK
- US
- Australia

### Pre-publication Guard
- Detect risky or unsupported claims before publication.
- Offer review/evidence actions.
- User keeps final publication decision.

These Phase 2 capabilities should begin only after the Commercial 1.0 readiness gap is defined and the current product can be sold and onboarded coherently.

## Platform phase
- Regulatory change impact analysis against customer claims.
- Claim Passport.
- Team/Agency workflows.
- Shopify connector.
- Public/private API.
- Additional CMS/e-commerce connectors.

## Defensibility / moat
Build cumulative assets rather than isolated features:
1. Regulatory Knowledge Graph.
2. Customer Claim Graph.
3. Decision / approval history.
4. Integrations and workflow embedding.

## Positioning direction
Avoid positioning ClaimPrism as only a "greenwashing scanner" or a single-regulation plugin.

Direction:
**Know what you claim. Prove it. Govern it.**

Working category:
**Claim Intelligence & Governance Platform**

ClaimPrism provides risk screening and governance workflow support. It is not a certification and does not provide a legal-compliance verdict.

## Scope discipline
Before adding a feature, ask:
1. Does it materially improve commercial value?
2. Does it deepen workflow embedding or cumulative data value?
3. Does it strengthen a roadmap capability rather than create a disconnected tool?
4. Can it be shipped and tested cleanly by our small team?

If the answer is mostly no, defer it.

## Release constraint
The WordPress.org-submitted `0.6.0` package remains frozen while under review unless the WordPress Plugins Team explicitly requests a change.