Manufacturer and partners
01Create productIssuer, model, serial logic and claims.
02Choose evidenceGS1, QR, NFC or MetaAnchor according to risk.
03Commission the itemAn authorized event binds product and identifier.
KYA long-term vision
From product evidence to a Trust Network.
Manufacturers make products trust-ready. Autonomous agents verify before buying, match the physical delivery to the order and return purpose-bound trust signals to the network.
VISION PAGEThis page describes the intended product direction. The live MVP remains the evidence check on the main page.
Order-to-Physical TrustVISION
Issuer and productTRUST-READY
Before purchasePRE-PURCHASE RECEIPT
Order contextORDER LINE BOUND
Physical deliveryFRESH SCAN
Trust returnOUTCOME SIGNAL
LIVE MVPRegistry, evidence status, demo and physical-scan path
PROTOTYPESupplier onboarding, partner roles and Trust Receipts
VISIONAutonomous order matching, Trust Ladder and reputation return
Two sides. One network.
Products become ready. Agents become informed.
The supply side creates verifiable product evidence. The demand side consumes it before purchase and confirms what physically arrived.
Marketplace and autonomous agent
04Verify before purchaseIssuer, seller authority, claims and recall status.
05Match the deliveryA fresh physical scan is bound to the order line.
06Return the outcomeThe network receives a minimized trust signal.
KYA TRUST LADDER
Trust grows through verified events.
Trust cannot be bought and does not rise through volume alone. Every level requires stronger, independent evidence.
KYA Evidence Kernel · in development
Different evidence. One explainable trust decision.
Providers prove different things with different natural strengths. The Kernel normalizes them, enforces freshness and registry hard gates, then returns one purpose-bound result.
SHADOW ARCHITECTURE · NOT YET AUTHORITATIVE
Evidence providers
KYA EVIDENCE KERNEL
Target output
Fresh secure optical proof + active registryGENUINE · T2
GS1 QR without copy protectionINCONCLUSIVE · MAX T1
Old or replayed physical scanUNKNOWN · T0
Authentic proof but registry revokedREVOKED · T0
Different proofs enter
Each provider remains responsible for its raw proof. KYA does not pretend that all evidence is equally strong.
MetaAnchorSecure optical fingerprint
LIVE EVIDENCEGS1 QRPlain product reference
NEXT ADAPTERSecure NFCCryptographic chip proof
ROADMAPPublic blockchainsPolygon and ApeChain live; additional networks through chain adapters
SUPPORTINGNormalize. Challenge. Decide. Sign.
The open adapter interface translates evidence. Freshness, policy and provenance stay protected on the server.
Normalized contractsOne language for every provider
READYFreshness + anti-replaySingle-use challenge and short window
NEXTAdapter RegistryProvider selection without policy logic
NEXTVersioned Policy EngineRegistry hard gates and evidence weighting
PLANNEDReceipt + provenanceSigned, privacy-minimized, hash-linked
PLANNEDOne result for the agent
The output explains what is known, how strongly it is proven and why an agent may or may not proceed.
STATUSGENUINE / UNKNOWN
TRUST LEVELT0 – T5
REASONS[]MACHINE-READABLE
EVIDENCE LINKSPURPOSE-BOUND
TRUST RECEIPTSIGNED
What Shadow Mode means: the current C# MVP remains the official decision. The Kernel will evaluate the same cases in parallel until its outcomes and receipts pass the Golden Tests and cutover review.
Evidence-weighted, not review-driven
Fake trust must be expensive and reversible.
Open star ratings do not influence technical trust. KYA uses transaction-bound evidence and separates the reliability of every actor.
No order line means no fulfilment confirmation.
Old images, copied QR codes and replayed tokens do not count.
Repeated activity with the same counterparty has diminishing weight.
Returns, chargebacks, recalls and fraud findings update prior outcomes.
Identity in. Trust out.
Trust information can return to the platforms.
Identity, delegated authority and transaction reliability remain separate. Platforms receive only purpose-bound, privacy-minimized signals.
Who acts for whom?
Enterprise and open-agent platforms authenticate the caller and its delegated role.
Microsoft EntraERC-8004MasumiGoogleAWSSalesforceSAP
What is proven for this purpose?
Signed Trust Receipts can flow to marketplaces, gateways and policy engines without exposing private order data.
APIWebhooksVCMCPA2AERC-8004
Adapter readiness
One gateway. Six adapter groups.
Open standards run now. Provider-specific adapters remain safely disabled until a real customer supplies access and approves activation.
OFFExternal writes
OFFPayment execution
NONEExternal credentials
A prepared adapter is not a live partnership or account. Activation happens only after credentials, contractual rights, costs and security controls are approved.
Evidence before claims
What must be proven before the vision becomes product.
Two design partnersReal product volume and autonomous-purchase intent.
One order integrationA real catalog or marketplace order line.
One physical delivery flowFresh scan linked to the actual shipment.
A second evidence providerKYA must remain provider-neutral.
Shape the vision with real evidence
Bring one product flow into the KYA MVP.
Start with the simple evidence check on the main page. Expand only when a real partner and order flow justify it.