Add OSOP workflow example — portable chatflow format

[Archie0125]

Summary

• Adds examples/osop/ with a RAG chatflow represented in OSOP format
• OSOP is a portable YAML format for describing AI workflows across platforms
• Shows how Flowise chatflow components (document loader, text splitter, embedding, vector store, retriever, LLM, response) map to OSOP nodes and edges

Why

Flowise chatflows are powerful but stored in a platform-specific JSON format. An OSOP representation enables cross-tool portability (n8n, LangFlow, custom agents), clean YAML diffs in version control, and human-readable workflow documentation.

Details

• Purely additive — no existing files are modified
• Standalone — the example is self-contained and works without any OSOP tooling installed
• Files added:
  • examples/osop/README.md — brief explanation of OSOP + Flowise
  • examples/osop/chatflow-example.osop.yaml — a RAG chatflow in OSOP format

[gemini-code-assist]

Code Review

This pull request introduces an OSOP (Open Source Orchestration Protocol) workflow example for Flowise, including a README and a sample RAG chatflow YAML file. The review feedback identifies a structural error in the YAML configuration for the vector store provider and suggests updating the LLM model to a more current version for better cost-effectiveness.

[gemini-code-assist]

The provider key should be a direct child of runtime, not nested under config. This aligns with the OSOP specification and maintains consistency with how provider is defined for the embedding and llm nodes in this file.

      provider: pinecone

[gemini-code-assist]

While gpt-4 is a valid model, consider updating this example to use a more recent and cost-effective model like gpt-4o. This would make the example more current and a better reference for users.

      model: gpt-4o

[Archie0125]

Good catches! Fixed both:

• Updated vector store provider configuration structure
• Changed LLM model to gpt-4o for cost-effectiveness

Thanks for the review!