# Programmable Object Interaction > [!important] Evidentiary status > **Programmable Object Interaction is a strong reconstruction from PDF page 40, not an independently verified established term.** The phrase is more legible than the expansion of UOI, but its status as a named framework remains unconfirmed. Programmable Object Interaction describes the notebook’s apparent idea that an object’s interface, capabilities, and permitted actions can be represented and changed in software instead of being permanently tied to one physical control surface or vendor application. ## Historical and Technical Context The notebook repeatedly encounters objects whose identity is programmable. A Raspberry Pi Zero can enumerate as storage, keyboard, serial device, network interface, or composite USB gadget. A phone becomes enterprise-owned through first-boot enrollment and firmware policy. An industrial controller combines PLC, HMI, gateway, Linux computer, and I/O roles. A cloud workload retains policy while moving across public, private, edge, and on-premises environments. Those examples support a technical reading of POI as interaction mediated by descriptors, APIs, schemas, policies, and state machines. They do not establish a formal specification. The reconstruction therefore distinguishes the visible phrase from the inferred larger framework. ## Role in Scanned_20260730-1802 POI is the operational counterpart to [[Universal Object Interaction|Universal Object Interaction]]. UOI asks for a common grammar; POI suggests that the grammar can be instantiated, translated, or modified for a particular object. This provides a conceptual bridge from USB gadget mode and industrial control to semantic interfaces and machine-mediated workflows. ## Notebook Evidence - `Scanned_20260730-1802.pdf`, PDF page 40: "\"POI programmable object interaction\"" - `Scanned_20260730-1802.pdf`, PDF page 40: "\"UOI\"" - `Scanned_20260730-1802.pdf`, PDF page 40: "\"TPI\"" **Visible evidence:** the phrase “POI programmable object interaction.” **Strong inference:** POI belongs to the same proposed ontology as UOI. **Unresolved ambiguity:** whether capitalization, wording, or the relationship among UOI, POI, and TPI was copied exactly. ## Relationships [[P4wnP1 A.L.O.A.|P4wnP1 A.L.O.A.]] is a concrete example of a programmable physical interface. [[groov EPIC|groov EPIC]] applies programmable interaction to industrial machines, while [[Core Data|Core Data]] illustrates how software objects acquire structured identity and state. [[Ontology Engineering|Ontology Engineering]] provides the normalized vocabulary needed to make those interfaces portable across domains. ## Cross-Notebook Significance The reconstruction provisionally relates POI to `Scanned_20260730-1845.pdf`, PDF page 1, where GPT-3, OpenAI, and APIs suggest software capable of generating or mediating interfaces. This is a plausible later development of the idea, not a confirmed direct reference. ## Missed Signals and Open Leads Locate other occurrences of POI and determine whether it referred to a project, product, protocol, or original concept. Do not assume TPI is “third-party interaction” or any other expansion without evidence. ## Sources - `Scanned_20260730-1802.md`, page-40 reconstruction and notebook-level synthesis. - `Scanned_20260730-1802.pdf`, PDF page 40, as represented in the completed Markdown reconstruction.