When a store gets cloned
Project history
The decisions, releases and learning that shape this project. Expand a milestone to see the rationale and evidence.
2 milestones · Newest first
2026
· Product definitionDefined a detection-first MVPExpanded the initial manual-pilot proposal into a staged plan for detection, operator review, customer reports and owner-approved complaints.Expand decision details
Why this changed
Test whether finding and explaining suspected copies creates a useful starting point before scaling takedown workflows or monitoring.
Evidence & context
The October plan separates setup, detection and reporting, outbound validation, self-service and monitoring. Stage gates are targets to test, not achieved customer or enforcement outcomes.
· Product definitionDefined a manual pilot before buildingProposed five to ten authorised cases to test whether better evidence improves incident response.Expand decision details
Why this changed
Test effectiveness, effort and willingness to pay before automating the workflow. Define stop criteria and owner approval requirements at the outset.
Evidence & context
The draft v0.1 PRD is dated 23 September and explicitly marked pre-validation. The cases, takedown outcomes and commercial assumptions remain untested.