PieceID signature workspace
Evidence File Studio
Turn a receipt, service paper, certificate or incomplete story into the next useful questions—without manufacturing a verdict.
Seller evidence request
Copy-ready language
Category evidence set
Document Claim Decoder
Read the scope—not just the logo at the top.
A document is useful when its issuer, subject, date, scope and limits can be reconciled. None of these document types should silently inherit a stronger claim.
Transaction evidence
May support seller, date, store and product-description context. It does not by itself prove the paper belongs to this object.
Intervention evidence
May support provider, date and stated work. It does not prove every component is original or that no earlier work occurred.
Process evidence
Read eligibility, inspected scope, exclusions, remedy and transferability. A tag without its terms is an incomplete claim.
Opinion evidence
Confirm issuer identity, methods, date, item match and correction policy through an independently found channel.
Attribute and value evidence
Read effective date, purpose, assumptions and inspected attributes. Valuation and authentication are different assignments.
Supporting context
Boxes, cards, dust bags and tools are portable. Reconcile them; never let them substitute for examining the object.
Digital destination evidence
Record the destination domain, displayed claim and date. A working link is not automatic proof of object-to-record binding.
Seven evidence standards
A record another person can challenge and follow.
- Name the claimHouse, model, reference, material, size and claimed period.
- Identify the sourceWho issued the evidence and how their identity was checked.
- Bind it to the objectExplain which non-sensitive attributes connect paper, record and item.
- Preserve the dateDistinguish purchase, inspection, service and appraisal dates.
- Keep the scopeState exactly what was inspected, serviced, valued or guaranteed.
- Expose the limitsUnknown, excluded, inaccessible or untested points remain visible.
- Record changeRepairs, replacements, refinishing, resizing and later condition belong in the history.
How other processes describe themselves
Read every service on its own published terms.
These primary-source doors are examples of different service models, not PieceID endorsements or substitutes for reading current terms.
Evidence Studio FAQ
Know what the workspace can—and cannot—do.
Does a receipt prove authenticity?
No. A receipt can support a transaction story, but it may be copied, altered, mismatched or misunderstood. Reconcile its seller, date, product description and identifiers with the object and source.
Does an official service invoice prove origin?
Only if the issuer explicitly makes that claim. A service record usually supports that a provider handled stated work on a stated date; do not expand it into a universal certificate.
Can PieceID verify a certificate number?
No. PieceID does not access issuer databases or validate certificate numbers. Contact the named issuer through an independently found official channel.
Are QR codes or chips definitive?
No. A working destination can be copied, redirected or attached to another object. Record the exact destination and compare the complete evidence file.
Where is my Studio information stored?
Nowhere. The Studio runs in this browser tab, sends no form data and uses no local or session storage. Closing or refreshing the page clears your draft.
Does the generated brief authenticate or value the item?
No. It organizes questions, evidence and disclosure language. It is not a verdict, certificate, appraisal or valuation.