REPRODUCIBLE EXAMPLES
See the result, not just the claim.
Each case defines disposable inputs, expected classifications, limitations and the next safe decision. No invented users, savings or benchmark numbers.
CHOOSE A CASE
Reproduce the example before trusting the workflow.
Every case uses disposable paths and explains which conclusions the result does not support.
REPRODUCIBLE PHOTO MERGE
What happens when the same photo has a different name?
DUPESPACE identifies renamed photos by complete content instead of copying them again. A matching relative path with different bytes remains a separate conflict for a person to resolve.
Read the test casePROJECT SAFETY CASETwo projects share a configuration file. Why must both copies stay?
Redundancy depends on purpose, not content alone. When two projects independently load matching configuration or packages, DUPESPACE should require context review or exclude them instead of removing one.
Read the test caseOUR PUBLICATION RULE
If we did not measure it, we do not publish a number.
- Version and scope are visible
- Paths and reports are redacted
- Limitations appear beside the result
- No result becomes automatic deletion advice