Observed source material
The 21 September records include the .net decision-support description and the .com trading presentation. Their common name does not establish one operator or implementation. The first discusses analysis; the second describes funding and trading. These are page observations, not proof that either workflow operates or that one site's disclaimer explains the other site's responsibilities.
The boundary between information and execution needs an interface contract
A product explanation should identify what passes between information and action. Ask whether an output is only displayed, sent to a separate provider or capable of becoming an instruction after approval. The responsible supplier should define the accepted input and the returned status at each boundary. These are questions for documenting an actual offer, not a finding that Prompt Lispro Fin uses any particular integration or external service.
Requirements for further verification
The next evidence would be a consistent specification and agreement tied to an identified provider and exact domain. It would allow an assessment to follow a real boundary instead of assembling a product from separate descriptions. We have not transmitted an instruction, inspected a private interface or tested trading. The status remains unknown, with the distinction between promotional architecture and demonstrated implementation kept explicit.