An identity that lasts.
A stable asset record designed to survive replacement tags, new documents and changes in custody. RFID, NFC and QR are entry points into the same history.
PHYSICAL ASSETS. CONNECTED RECORDS.
Every asset.
Its whole story.
A record that stays with the things that matter. Connecting physical assets, documentation and business workflows—from first registration to the next handoff.
In development / Early pilot conversations
PHYSICAL DIGITAL
RFID REGISTRY
ASSET / 000128
CONNECTED RECORDA history worth keeping.Identity · Evidence · Handoffs
ILLUSTRATIVE CONCEPT 01 — REGISTRY
ONE CONTINUOUS RECORDIdentifyDocumentVerify evidenceConnect workflows
01 / THE PLATFORM
The item is physical.
The context shouldn’t get lost.
Certificates in an inbox. Delivery notes in a folder. A serial number in a spreadsheet. We’re building a more connected way to work.
Evidence, in context.
Permissioned documents, version history and verifiable record references. Bring specifications, inspections and warranties back to the asset they describe.
The next step, connected.
Link delivery evidence and buyer acceptance to business obligations, with planned payment integrations and a clearer path to reconciliation.
02 / A RECORD IN PRACTICE
Scan the item.
See the context.
Explore an illustrative window-component record. One place for the item’s identity, supporting documentation and handoff history.
Interactive concept · Sample data only.
This is a design preview, not a live registry.
RFID / NFC / QR
Multiple ways into one record
Multiple ways into one record
REGISTRY EXPLORERSAMPLE
RR–000128
Architectural window assembly
Building components / Example record
- Asset identifier
- RR–000128
- Record type
- Manufactured component
- Tag reference
- NFC–DEMO–128
- Custody stage
- Received
- Evidence access
- Permissioned
◈ An asset’s record travels beyond a single tag.
Product specificationVersion 1.0 · Example document
PDFInspection recordVersion 1.1 · Example document
PDFDelivery confirmationVersion 1.0 · Example document
PDFIllustrative metadata. No customer documents are stored here.
- Asset registeredSTEP 01
Identity and initial specification associated.
- Inspection documentedSTEP 02
New evidence version added to the record.
- Delivery receivedSTEP 03
Handoff recorded for buyer review.
Example sequence. Payment requires separate authorization.
03 / WHERE IT STARTS
Practical records.
Real-world use.
Starting with supplier workflows. Designed with room for the people and businesses an asset reaches next.
INITIAL FOCUS
Suppliers & building products
Connect product specifications, inspections, delivery evidence and acceptance. Initial discovery is informed by two window suppliers willing to test; pilot scope remains to be agreed.
Collectibles & provenance
Bring issuer records, grading documentation and ownership history together. Evidence supports informed decisions; a tag alone does not prove authenticity.
Equipment & lifecycle records
Preserve service, warranty and handoff documentation as an asset moves between teams, locations and owners.
04 / BUILT TO CONNECT
A platform for businesses.
A toolkit for builders.
We’re planning reusable infrastructure alongside the hosted platform: a TypeScript SDK, documented APIs, an independent evidence verifier and hardware adapter examples.
Open-source components are planned. Packages and public documentation will be linked as they are released.
INTEGRATION CONCEPT● ● ●
// One asset. Connected context.const asset = {
id: "RR-000128",
identifiers: ["NFC", "QR"],
evidence: {
access: "permissioned",
history: "versioned"
},
workflow: {
acceptance: "explicit",
payment: "user-authorized"
}
};ILLUSTRATIVE MODEL · SDK IN DEVELOPMENT
DESIGNED AROUND TRUST
Keep private data private.
Permissioned access and off-chain document storage are central to the design.
Make claims verifiable.
Record integrity, issuer evidence and physical authenticity are distinct. The platform should make those distinctions clear.
Keep people in control.
A scan should never authorize a payment. Business acceptance and wallet approval remain separate actions.
LET’S BUILD THE NEXT CHAPTER
Your assets have a story.
Let’s make it accessible.
Have a supplier workflow, an integration idea or a potential pilot?
Talk directly with the founder.