{
 "url": "https://activatedigital.ai/knowledge/guides/programmable-product-stack",
 "title": "The Programmable Product: What Becomes Possible When Software Can Read One",
 "description": "A programmable product combines persistent identity with resolution, sensing, memory, trust, context, decisions and actions. See what each decision needs.",
 "territory": "impl",
 "category": null,
 "direct_answer": "A physical product can become more than digitally addressable. Persistent identity can act as a **join key** to software capabilities that let the product resolve to services, become observable without a deliberate scan, gain spatial context, report physical condition, accumulate history, present stronger trust signals, sit behind explicit permissions, pull in external context, trigger decisions and connect to executable actions.",
 "last_verified": "2026-09-04",
 "verified_label": "Last verified",
 "datePublished": "2026-09-04",
 "dateModified": "2026-09-04",
 "legislation": [],
 "primary_sources": [
  {
   "url": "https://ref.gs1.org/standards/resolver/",
   "name": "GS1: GS1-Conformant Resolver Standard 1.2.1, August 2026. Used for product identity resolving to multiple machine-discoverable resources."
  },
  {
   "url": "https://ref.gs1.org/standards/digital-link/uri-syntax/1.7.0/",
   "name": "GS1: Digital Link URI Syntax 1.7.0, August 2026. Used for product identifiers represented in web-resolvable form."
  },
  {
   "url": "https://ref.gs1.org/standards/epcis/2.0.1/",
   "name": "GS1: EPCIS 2.0.1, current specification. Used for identified event history, where/when context and sensor elements."
  },
  {
   "url": "https://www.gs1.org/standards/epcis",
   "name": "GS1: EPCIS and CBV overview, accessed 4 September 2026. Supporting source for visibility, sensor and event-memory capabilities."
  },
  {
   "url": "https://www.bluetooth.com/learn-about-bluetooth/feature-enhancements/channel-sounding/",
   "name": "Bluetooth SIG: Channel Sounding, accessed 4 September 2026. Used for secure fine-ranging capability and its limits."
  },
  {
   "url": "https://www.bluetooth.com/learn-about-bluetooth/feature-enhancements/direction-finding/",
   "name": "Bluetooth SIG: Direction Finding, accessed 4 September 2026. Used to distinguish direction/positioning from ordinary BLE presence."
  },
  {
   "url": "https://www.firaconsortium.org/resource-hub/technical-faq",
   "name": "FiRa Consortium: UWB Technical FAQ, accessed 4 September 2026. Used for secure fine ranging and positioning architecture."
  },
  {
   "url": "https://carconnectivity.org/ccc-digital-key-certifications-surged-in-2025/",
   "name": "Car Connectivity Consortium: Digital Key certifications surged in 2025, 6 January 2026. Used for bounded production adoption evidence."
  },
  {
   "url": "https://carconnectivity.org/digital-key-use-cases/",
   "name": "Car Connectivity Consortium: Digital Key use cases, accessed 4 September 2026. Used for the separation between credential, ranging, entitlement and action."
  },
  {
   "url": "https://www.apple.com/uk/legal/privacy/data/en/find-my/",
   "name": "Apple: Find My and Privacy, 15 September 2025. Used as a bounded example of BLE observations operating through receiver/platform infrastructure with explicit privacy design."
  },
  {
   "url": "https://www.w3.org/TR/geolocation/",
   "name": "W3C: Geolocation, 2026 Candidate Recommendation. Used for the boundary that web geolocation exposes the hosting device's location, not proven product location."
  },
  {
   "url": "https://www.w3.org/news/2025/the-verifiable-credentials-2-0-family-of-specifications-is-now-a-w3c-recommendation/",
   "name": "W3C: Verifiable Credentials 2.0, 15 May 2025. Used for machine-verifiable credential capability and verification boundaries."
  },
  {
   "url": "https://sell.amazon.com/brand-registry/transparency/",
   "name": "Amazon: Transparency, accessed 4 September 2026. Used as a bounded serial-verification deployment example."
  },
  {
   "url": "https://health.ec.europa.eu/medicinal-products/falsified-medicines_en",
   "name": "European Commission: Falsified Medicines, accessed 4 September 2026. Used as a regulated serial verification and repository-state example."
  },
  {
   "url": "https://www.zebra.com/gb/en/resource-library/success-stories/boggi-milano-enhances-stock-accuracy-with-zebras-advanced-rfid-solutions.html",
   "name": "Zebra Technologies: Boggi Milano RFID case study, accessed 4 September 2026. Vendor-published customer evidence used only for bounded measured RFID outcomes."
  },
  {
   "url": "https://www.zebra.com/us/en/resource-library/success-stories/good-american-optimizes-retail-inventory-management-from-source-to-store.html",
   "name": "Zebra Technologies: Good American RFID case study, accessed 4 September 2026. Vendor-published customer evidence used only for bounded counting and inventory outcomes."
  },
  {
   "url": "https://www.carfax.com/value/",
   "name": "CARFAX: History-Based Value, accessed 4 September 2026. Used for identity plus item history plus market context producing an item-specific valuation."
  },
  {
   "url": "https://www.carfaxforlenders.com/products/history-based-value/",
   "name": "CARFAX for Lenders: History-Based Value, accessed 4 September 2026. Used for lending and loan-to-value application of item-specific history-based valuation."
  },
  {
   "url": "https://developer.ebay.com/api-docs/user-guides/static/trading-user-guide/compatible-parts-api-support.html",
   "name": "eBay Developers: Compatible parts API support, accessed 4 September 2026. Used for machine-operable vehicle/part compatibility."
  },
  {
   "url": "https://www.edp.ebay.com/api-docs/buy/static/api-browse.html",
   "name": "eBay Developers: Browse API compatibility, accessed 4 September 2026. Used for candidate-part compatibility status in machine commerce."
  },
  {
   "url": "https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/docs/specification/2026-07-28/server/tools.mdx",
   "name": "Model Context Protocol: Tools, 2026-07-28. Used for discoverable machine-invokable tools and their boundaries."
  },
  {
   "url": "https://blog.modelcontextprotocol.io/posts/2026-07-28/",
   "name": "Model Context Protocol: July 2026 release, 28 July 2026. Used for current MCP maturity and authorisation-hardening context."
  }
 ],
 "glossary_terms": [
  "https://activatedigital.ai/knowledge/glossary#epcis",
  "https://activatedigital.ai/knowledge/glossary#gs1",
  "https://activatedigital.ai/knowledge/glossary#nfc",
  "https://activatedigital.ai/knowledge/glossary#qr-code",
  "https://activatedigital.ai/knowledge/glossary#resolver",
  "https://activatedigital.ai/knowledge/glossary#serialisation",
  "https://activatedigital.ai/knowledge/glossary#unique-product-identifier"
 ],
 "watch": [],
 "decisions": [],
 "alternates": {
  "html": "https://activatedigital.ai/knowledge/guides/programmable-product-stack",
  "markdown": "https://activatedigital.ai/knowledge/guides/programmable-product-stack.md",
  "json": "https://activatedigital.ai/knowledge/guides/programmable-product-stack.json"
 }
}