This page documents the registry model, event recording and severity, badge computation, overlays and decay,
tier-based visibility, resolution marking, badge issuance (digital and physical), and example workflows.

When a business performs a lookup, the system checks for interaction records contributed by participating businesses across the registry.
This allows a business to observe existing operational history (when available) even if it has never interacted with the customer before.

Free participation provides meaningful operational awareness and is sufficient to pre-filter customers based on behavioral records.
Free-tier lookup results typically include:

• Badge presence and level (if a badge exists)
• Overlay indicators (e.g., open negatives present, resolved negatives present)
• Event impact level (severity/impact signal)
• Resolution status (open vs resolved, when applicable)
• Limited identifying information to confirm the subject match

Pro participation may allow expanded operational visibility beyond badge level and overlays, such as richer event detail, timelines, and supporting material
when available. Reporting business identity remains protected and is not disclosed to other businesses.

TrustEmporium does not disclose which business submitted a report to other businesses. The registry preserves reporting business confidentiality.

A querying business may optionally notify the customer that a lookup occurred. If enabled by the querying business,
the customer may receive an email indicating:

• that a lookup was performed
• which business performed it
• a general lookup result summary

TrustEmporium does not notify customers automatically.

TrustEmporium does not recommend or enforce decisions. Each participating business defines its own policies and determines how to use registry information,
including deposits, booking terms, recognition benefits for positive badge holders, or proceeding normally.

Each event typically includes:

• Subject identifier (email hash and/or phone hash)
• Event type (selected from the event library)
• Impact / severity value
• Status (open or closed)
• Timestamp
• Optional evidence attachments
• Optional resolution state (when applicable)

TrustEmporium uses a structured event library (positive, neutral, and negative event types). Businesses choose the event type that matches the operational scenario.
The library contains many additional event types beyond the examples shown across the site.

When appropriate, an event may include evidence attachments. Evidence is optional, and availability depends on the reporting workflow and tier.

Impact values allow businesses to record the operational weight of an event (e.g., minor inconvenience vs severe operational harm).
Impact is used by the overlay system to determine whether and how badge display is capped or suppressed.

Impact values follow directionality:

• Negative events: mild = lower negative impact, severe = higher negative impact.
• Positive events: mild = lower positive impact, severe = higher positive impact.

Exact values may vary by event type and are defined by the event library.

Badge levels range from 0 to 4. Higher levels reflect deeper positive interaction history across participating businesses,
within defined time bounds. Badge level is computed from positive evidence.

• Raw badge: the maximum badge level supported by positive interaction evidence.
• Displayed badge: the badge level shown after applying negative overlays (caps or suppression).

Negative events do not erase positive evidence. They affect display via overlays.

Open negative events may cap or suppress badge display. Severity and quantity of open negatives may increase overlay strength.
The underlying positive badge (raw) remains intact.

Closed negative events may continue to cap or suppress display for a period of time, then decay naturally.
When decay completes, overlay effects are removed and the displayed badge may return closer to the raw badge level.

When an incident is resolved, the event may be marked accordingly, but the original record remains preserved as historical context.
Resolution indicates closure; it is not a reset and is not a guarantee of future outcomes.

Subjects are referenced using hashed identifiers (e.g., email hash and/or phone hash). This supports consistent matching
across businesses while reducing unnecessary exposure of raw personal data in registry storage.

The registry functions as a ledger: events are written as business-reported history entries and retained as historical context.

Public surfaces may return limited existence/aggregate-style information only. Business dashboards provide operational context
based on authorization and tier.

• Free: badge presence/level, overlays, impact signals, resolution status, limited identification.
• Pro: may include expanded event-level detail and supporting material when available.

Reporting business identity remains protected.

Digital badge presence and level may be verified through TrustEmporium surfaces. Badge displays may reflect overlays.

Physical CR80 cards may be ordered. Cards typically include a badge identifier and a verification QR code that links to a TrustEmporium verification surface.
Physical badge cards do not imply endorsement; they provide a portable way to present verification.

Typical workflow:

• Badge exists (or is issued) for a subject
• Order is created for a physical card
• Card is produced with badge ID and verification QR
• Customer receives the card

1. Business checks a customer badge (lookup).
2. Badge is found with a level (example: Level 3) and overlay status (if any).
3. Business applies its own policy (example: optional perk or priority handling).
4. Outcome is business-defined and optional. TrustEmporium does not recommend actions.

1. Business performs an email/identifier lookup.
2. Customer is not found (no history available).
3. Business proceeds under normal policy.
4. After the experience, business records a positive event (example: “Left a generous tip”).

1. Business performs a lookup.
2. Customer is found with an open negative overlay (example: severe impact).
3. Business applies its own risk policy (example: require a non-refundable deposit).
4. Service proceeds under business-defined terms.
5. After the interaction, the business may log the actual outcome (positive, neutral, or negative) for its own records and to contribute to historical context.
6. TrustEmporium does not enforce outcomes — policies and decisions remain business-controlled.

Customers may accumulate positive interaction history across participating businesses. When badges are present, they provide a portable signal
of consistent positive interactions. Participation may be voluntary and pull-based.

A business may optionally notify a customer that a lookup occurred, including the business identity and a general result summary.
TrustEmporium does not send notifications automatically.

TrustEmporium does not score, rate, rank, label, recommend, or enforce decisions. It does not publish detailed records publicly.
It provides structured operational history and controlled access only.

Reporting accuracy remains the responsibility of the reporting business. Decision-making remains the responsibility of the business using the system.
TrustEmporium provides infrastructure only.