Full Break Rules.

Base and non-hit cards

An opened pack first appears as one bundle containing every card saved at reveal. The vault shows its reveal-time hit count, 72-hour bundle offer window, and 75-hour automatic-resolution deadline.

Hit and non-hit status is locked against that break's saved reveal threshold. A later market-price change does not silently reclassify the cards.

• Store as Asset first shows a card-by-card preview. Confirming stores the listed hits as individual platform assets and forfeits the listed non-hits to platform custody; cancelling changes nothing.
• Trading the full bundle for a Second Chance Ticket forfeits the bundle, including any hits still inside it.
• Before automatic resolution, eligible full bundles can be manually traded for one Second Chance Ticket through the Traffic Light experience. At the deadline, untouched non-hit bundles receive one ticket directly without the game; untouched hit bundles store their hits and forfeit their non-hits.

Sealed product and opening-camera requirements

The published rip rule decides whether a claim must open live, lets its owner choose open-live or keep-sealed before the cutoff, or keeps every pack sealed. Only claims marked open-live enter the reveal queue.

For a live opening, the protection standard is to show the product identity and intact seal before opening, then keep the product, pack, and card reveal in a continuous, reviewable camera view.

• Auto-rip: the purchased pack is opened live.
• User choice: the owner may switch an unopened claim before the live/reveal window closes.

Camera compliance is reviewed from stream evidence; the platform does not currently certify it automatically.

Stream replay and exact reveal timestamp

A published reveal can retain the stream or replay URL, the exact timestamp entered for that opening, the pack's opening order, the server publication time, and a reveal version.

The Watch Reveal link in the vault returns to that saved proof. The timestamp identifies the relevant moment, while the replay itself remains subject to the stream host's availability and retention rules.

A saved link is evidence of the source used for the reveal; it is not a promise that a third-party host will preserve the video forever.

Front and back card images after opening

Each revealed physical card has separate front and back capture slots that remain distinct from catalog or reference art. The vault and protection review show which sides are complete or still missing.

Every captured image is stored as verified private bytes with its source, capture time, server record time, content hash, and authenticated admin recorder. A correction appends a new version with a reason while preserving every prior receipt.

Photos are available only to the owning account and authorized administrators; a missing side remains visibly missing rather than falling back to catalog art.

Reveal value and valuation source

Each revealed card can retain its reveal value, currency, source or provider details, lookup time, source link, and any manual override provenance. The bundle total and reveal-time hit threshold are saved with the reveal.

Current market estimates may be refreshed later for reference, but they do not silently rewrite the reveal snapshot, submitted sellback terms, payouts, XP, or ticket rewards.

The reveal-value source is not yet presented as a fully immutable vault receipt. All values are estimates, not guaranteed grades, sale prices, or future market values.

Current custody and shipment history

The vault asset records the beneficiary, ownership mode, current lifecycle status, and custody wallet when one applies. Asset events preserve important transitions from paid claim through reveal and final outcome.

A shipment record groups every included asset with its destination, quote and payment state, additions or fee waivers, preparation status, carrier, tracking number, shipped state, and delivery acknowledgement when recorded.

These records are not yet presented as one unified physical chain-of-custody timeline, and a storage location is not modeled. Sensitive address and tracking data may be redacted under the retention policy after fulfillment.

Missing, incorrect, damaged, and non-delivery claims

Once an administrator publishes the first protection policy, the vault provides a self-service flow for missing, incorrect, damaged, and non-delivery claims. Eligibility, filing deadlines, response targets, resolution targets, required evidence, and allowed remedies come from the immutable policy receipt pinned to that claim.

Evidence uploads are private, authenticated, checksum-verified files. Claim status, evidence additions, operator decisions, and completed remedies advance through a durable event history rather than replacing earlier records.

• Do not discard packaging or return an item until the operator gives instructions.
• For non-delivery, the carrier scan history and any carrier investigation become part of the review.
• A remedy is decided from the evidence and the applicable break and shipping terms; filing a report does not predetermine an outcome.

The workflow fails closed while protection is unconfigured. Card Break does not invent default deadlines or remedies; the exact active policy must be explicitly published first.

Insurance and signature confirmation for high-value shipments

Preparation creates an immutable assessment of the exact package contents and their recorded values under the shipment's pinned policy. The policy supplies the high-value threshold, coverage ceiling, permitted country and carrier codes, and required signature service.

Dispatch requires a carrier, carrier code, tracking number, expected-delivery timestamp, and an intact package assessment. A high-value package also requires the exact declared value, insurance evidence, signature service, and permitted route—or a specially authorized exception bound to that policy and assessment with the waived controls and reason audited.

Do not assume a parcel is insured or signature-required unless its shipment receipt expressly confirms the controls. An exception remains visible as an exception, not as completed coverage.