TRU Technical Overview
A controlled technical walkthrough of how the Unit Identity Rail (Truth Rail) works — from issuance to enforced outcomes.
Architecture overview
TRU is a unit identity layer plus a verification rail.
Identity is issued per unit, bound to secure hardware, and resolved through the rail at verification time.
Every verification produces a defensible outcome (and optional event trail) that systems can rely on.
The rail is the mechanism that turns identity into enforcement — not just a label.
1) Unit identity issuance
Each product unit receives a unique identity at the source (manufacturer, authorized encoder, or controlled issuance point).
The identity is designed to persist beyond custody so the unit remains verifiable downstream.
- • Identity is per unit (not SKU-level)
- • Issued under controlled conditions
- • Prepared for downstream verification without app friction
2) Binding identity to secure hardware
TRU binds the unit identity to secure NFC/RFID tag hardware so identity is present on the physical object.
Binding ensures the system isn't just tracking records — it's linking identity to the unit in the world.
- • Tag binding at source / authorized points
- • Designed to resist simple copying / swapping
- • Supports multiple tag types based on product constraints
3) Verification on the Truth Rail
When a unit is tapped, TRU resolves the identity through the rail to produce a verification result.
Verification can occur at retail, receiving dock, returns desk, resale, or consumer touchpoints.
- Tap / scan triggers identity resolution
- Rail verifies identity and context
- Rules are evaluated (eligibility, channel status, etc.)
- A clear outcome is returned instantly
Verify the exact unit and enforce eligibility.
Prove authenticity before disputes start.
Deliver trusted content tied to verified units.
4) Enforced outcomes
TRU is designed to output outcomes that are simple to understand and easy to operationalize.
The value comes from enforcement: outcomes are reliable because identity is unit-level and verified through the rail.
- • Authentic / Not authentic
- • Return eligible / Not eligible
- • Channel allowed / Off-channel
- • Resale status and verification signals (optional)
- • Verified content access (optional)
Event trails & intelligence
TRU can record verification events as units move through the world.
This turns downstream noise into measurable signals: where fraud clusters, where diversion occurs, and where inventory contamination starts.
- • Verification events create measurable patterns
- • Supports operational analytics and investigations
- • Evidence for disputes and enforcement actions
Security posture (high-level)
This page is intentionally high-level. Detailed security and binding methods are shared under NDA during demo.
At a minimum, TRU is designed to resist common attacks: copying, replay, swapping, and spoofed identifiers.
- • Unit identity + controlled issuance
- • Secure binding to tag hardware
- • Verification logic on the rail (not on the tag)
- • Outcome enforcement via rules and context
We keep implementation details, keys, and exact binding methods off public pages. Buyers receive the deeper technical brief during the demo process.
What TRU is not
This prevents confusion and protects your evaluation process. TRU is infrastructure — not a marketing label.
- • Not a QR-code campaign
- • Not a SKU-level tracking tool
- • Not a static identifier that can be copied
- • Not 'compliance theater' — compliance is an outcome of unit identity
Request the demo + technical brief
Tell us your primary use case (Returns, Counterfeit, Gray Market). We'll send the right flow.