Skip to content

Menu

The technical record

Technical

To reach Transactable, fix R2.2 first.

Ladders

R1Catalog3 of 4Discoverable needs 2
R2Purchase1 of 4Transactable needs 3
R3Access2 of 2Discoverable needs 2
R4Terms8 of 8Agreeable needs 5
R6Binding1 of 4Provable needs 2
R7Seller2 of 4Agreeable needs 2
R8Product3 of 5Agreeable needs 2
R9Price5 of 5Agreeable needs 4
R10Agreement record1 of 3

Commercial certainty

Scored apart from the stages.

C2Fulfillment certainty2 of 5
C3Recourse1 of 5
C4Continuity1 of 5

2 gaps

C2.3Availability is stated only as in or out of stock.
C3.2No returns or cancellation document was found.

30 checks

The plan puts these fixes in order

Check	Outcome	Reason	Requests
`R1.4`An agent interface that answers product searches	To fix`not_met`	No agent interface answered a catalog query: the site publishes no UCP business profile, and no other agent interface lists its products.	1
`R2.2`Order links AI agents can build	To fix`not_met`	The platform could not be identified, so no documented cart link applies.	3
`R6.2`The agreement inside the payment	To fix`not_met`	No agreement record passes the buyer gate (R10.2): No payment challenge Lens met declares an agreement record's hash.	1
`R7.3`A registered company behind the site	To fix`not_met`	The site names no legal entity with a register identifier (leiCode, vatID, taxID, duns, iso6523Code, globalLocationNumber, or an identifier PropertyValue such as a CIK or a company number): not in the schema.org Organization of any page Lens read, the UCP profile or the DID document.	3
`R8.4`Signed product records	To fix`not_met`	The product page links no product record: no dpp link (an HTML link element or a Link header), and no schema.org hasDigitalProductPassport.	1
`R10.2`A checkable record of each agreement	To fix`not_met`	No payment challenge Lens met declares an agreement record's hash.	1