@bluefly/openstandardagents 0.2.5-RC → 0.2.7

package/website/content/docs/getting-started/5-Minute-Overview.md

@@ -1,85 +0,0 @@
----
-title: "5 Minute Overview"
----
-
-# 5-Minute Overview
-
-Get up to speed on OSSA in 5 minutes.
-
-## What is OSSA?
-
-**OSSA (Open Standard for Scalable Agents)** is like OpenAPI, but for AI agents.
-
-- **OpenAPI** = Standard format for REST APIs
-- **OSSA** = Standard format for AI agents
-
-## Why Does This Matter?
-
-### Before OSSA
-- Agents built with LangChain couldn't work with Anthropic SDK agents
-- Moving agents between teams required rewriting
-- No standard way to validate agent correctness
-- Framework lock-in everywhere
-
-### With OSSA
-- ✅ Agents work across any framework
-- ✅ Move agents between teams/organizations easily
-- ✅ Validate agents before deployment
-- ✅ No vendor lock-in
-
-## Core Concept
-
-OSSA defines agents using a **declarative YAML/JSON format**:
-
-```yaml
-apiVersion: ossa/v0.2.x
-kind: Agent
-
-metadata:
-  name: my-agent
-  version: 1.0.0
-  description: My first OSSA agent
-
-spec:
-  role: You are a helpful assistant
-  llm:
-    provider: openai
-    model: gpt-3.5-turbo
-  tools:
-    - type: function
-      name: greet_user
-      description: Greet a user by name
-```
-
-## Key Components
-
-| Component | What It Does |
-|-----------|--------------|
-| **Specification** | JSON Schema that defines the standard |
-| **CLI** | Validates and generates agent manifests |
-| **Examples** | Reference implementations for learning |
-| **agent-buildkit** | Reference implementation with production features |
-
-## What OSSA Is NOT
-
-- ❌ **Not a framework** - It's a standard
-- ❌ **Not a runtime** - It's a specification
-- ❌ **Not an orchestration tool** - It's a contract definition
-
-## Next Steps
-
-1. **Install OSSA CLI**: `npm install -g @bluefly/open-standards-scalable-agents`
-2. **Try the Hello World example**: See [Hello World Tutorial](Hello-World)
-3. **Create your first agent**: See [First Agent Creation](First-Agent)
-4. **Explore examples**: Check out [Examples & Patterns](../Examples/Getting-Started-Examples)
-
-## Learn More
-
-- [Installation Guide](Installation)
-- [Hello World Tutorial](Hello-World)
-- [Full Documentation](../Technical/Specification-Deep-Dive)
-
----
-
-**Time to next level**: ~15 minutes → [Hello World Tutorial](Hello-World)
-

package/website/content/docs/getting-started/First-Agent.md

@@ -1,196 +0,0 @@
----
-title: "First Agent"
----
-
-# First Agent Creation
-
-Build your first real OSSA agent with capabilities.
-
-## Overview
-
-In this guide, you'll create a complete agent with:
-- Multiple tools/capabilities
-- LLM configuration
-- Observability setup
-- Constraints and limits
-
-## Step 1: Choose Your Agent Type
-
-OSSA supports various agent types:
-
-- **chat** - Conversational agent
-- **workflow** - Workflow orchestration
-- **compliance** - Compliance checking
-- **monitoring** - System monitoring
-- **worker** - Task processing
-
-For this tutorial, we'll create a **chat** agent with web search capability.
-
-## Step 2: Generate Base Agent
-
-```bash
-ossa generate chat \
-  --name "Research Assistant" \
-  --description "An agent that can search the web and answer questions" \
-  --output research-assistant.ossa.yaml
-```
-
-## Step 3: Add Tools
-
-Edit `research-assistant.ossa.yaml` to add a web search tool:
-
-```yaml
-spec:
-  role: |
-    You are a research assistant. Your job is to:
-    1. Search the web for current information
-    2. Synthesize information from multiple sources
-    3. Provide accurate, well-sourced answers
-    
-    Always cite your sources and verify information.
-  
-  llm:
-    provider: openai
-    model: gpt-4
-    temperature: 0.3  # Lower for factual accuracy
-  
-  tools:
-    - type: http
-      name: web_search
-      description: Search the web for current information
-      endpoint: https://api.search-service.com/search
-      config:
-        method: POST
-        timeout: 10
-      auth:
-        type: apikey
-        credentials: SEARCH_API_KEY
-```
-
-## Step 4: Add Observability
-
-Add observability configuration:
-
-```yaml
-spec:
-  # ... existing config ...
-  
-  observability:
-    tracing:
-      enabled: true
-      exporter: otlp
-      endpoint: http://localhost:4318
-    metrics:
-      enabled: true
-      exporter: prometheus
-      endpoint: http://localhost:9090/metrics
-    logging:
-      level: info
-      format: json
-```
-
-## Step 5: Add Constraints
-
-Add cost and performance constraints:
-
-```yaml
-spec:
-  # ... existing config ...
-  
-  constraints:
-    cost:
-      maxTokensPerDay: 100000
-      maxCostPerDay: 10.00
-      currency: USD
-    performance:
-      maxLatencySeconds: 5.0
-      maxConcurrentRequests: 10
-      timeoutSeconds: 30
-```
-
-## Step 6: Validate
-
-Validate your complete agent:
-
-```bash
-ossa validate research-assistant.ossa.yaml --verbose
-```
-
-## Complete Example
-
-Your final agent should look like:
-
-```yaml
-apiVersion: ossa/v0.2.x
-kind: Agent
-
-metadata:
-  name: research-assistant
-  version: 1.0.0
-  description: An agent that can search the web and answer questions
-  labels:
-    environment: development
-    team: research
-
-spec:
-  role: |
-    You are a research assistant. Your job is to:
-    1. Search the web for current information
-    2. Synthesize information from multiple sources
-    3. Provide accurate, well-sourced answers
-    
-    Always cite your sources and verify information.
-  
-  llm:
-    provider: openai
-    model: gpt-4
-    temperature: 0.3
-    maxTokens: 2000
-  
-  tools:
-    - type: http
-      name: web_search
-      description: Search the web for current information
-      endpoint: https://api.search-service.com/search
-      config:
-        method: POST
-        timeout: 10
-      auth:
-        type: apikey
-        credentials: SEARCH_API_KEY
-  
-  constraints:
-    cost:
-      maxTokensPerDay: 100000
-      maxCostPerDay: 10.00
-      currency: USD
-    performance:
-      maxLatencySeconds: 5.0
-      maxConcurrentRequests: 10
-  
-  observability:
-    tracing:
-      enabled: true
-      exporter: otlp
-      endpoint: http://localhost:4318
-    metrics:
-      enabled: true
-      exporter: prometheus
-    logging:
-      level: info
-      format: json
-```
-
-## Next Steps
-
-1. ✅ First agent created
-2. → [Integration Patterns](../Examples/Integration-Patterns) - Connect multiple agents
-3. → [Migration Guides](../Examples/Migration-Guides) - Migrate from other frameworks
-4. → [Advanced Patterns](../Examples/Advanced-Patterns) - Enterprise patterns
-
-## Related
-
-- [Hello World Tutorial](Hello-World)
-- [Schema Reference](../Technical/Schema-Reference)
-- [Complete Examples](../Examples/Getting-Started-Examples)
-

package/website/content/docs/getting-started/Hello-World.md

@@ -1,184 +0,0 @@
----
-title: "Hello World"
----
-
-# Hello World Tutorial
-
-Create your first OSSA agent in 10 minutes.
-
-## Overview
-
-In this tutorial, you'll:
-1. Generate a minimal OSSA agent
-2. Understand the agent structure
-3. Validate the agent
-4. Learn what each field means
-
-## Step 1: Generate Your First Agent
-
-Use the OSSA CLI to generate a chat agent:
-
-```bash
-ossa generate chat --name "Hello World Agent" --output hello-world.ossa.yaml
-```
-
-This creates a minimal, valid OSSA agent manifest.
-
-## Step 2: Examine the Generated Agent
-
-Open `hello-world.ossa.yaml`:
-
-```yaml
-apiVersion: ossa/v0.2.x
-kind: Agent
-
-metadata:
-  name: hello-world-agent
-  version: 0.1.0
-  description: Hello World Agent
-
-spec:
-  role: |
-    You are a helpful chat assistant.
-    Answer questions clearly and concisely.
-  
-  llm:
-    provider: openai
-    model: gpt-3.5-turbo
-    temperature: 0.7
-  
-  tools: []
-```
-
-## Step 3: Understand the Structure
-
-### apiVersion & kind
-
-```yaml
-apiVersion: ossa/v0.2.x
-kind: Agent
-```
-
-- **apiVersion**: OSSA specification version
-- **kind**: Resource type (currently only "Agent")
-
-### metadata
-
-```yaml
-metadata:
-  name: hello-world-agent
-  version: 0.1.0
-  description: Hello World Agent
-```
-
-- **name**: Agent identifier (DNS-1123 format)
-- **version**: Semantic version
-- **description**: Human-readable description
-
-### spec
-
-```yaml
-spec:
-  role: |
-    You are a helpful chat assistant.
-    Answer questions clearly and concisely.
-  
-  llm:
-    provider: openai
-    model: gpt-3.5-turbo
-    temperature: 0.7
-  
-  tools: []
-```
-
-- **role**: System prompt/instructions for the agent
-- **llm**: Language model configuration
-- **tools**: Available capabilities (empty for basic chat)
-
-## Step 4: Validate Your Agent
-
-Validate the agent against the OSSA schema:
-
-```bash
-ossa validate hello-world.ossa.yaml
-```
-
-You should see:
-
-```
-✓ Agent manifest is valid OSSA v0.2.x
-```
-
-## Step 5: Add a Tool (Optional)
-
-Edit `hello-world.ossa.yaml` to add a greeting tool:
-
-```yaml
-spec:
-  role: |
-    You are a helpful chat assistant.
-    Answer questions clearly and concisely.
-  
-  llm:
-    provider: openai
-    model: gpt-3.5-turbo
-    temperature: 0.7
-  
-  tools:
-    - type: function
-      name: greet_user
-      description: Generate a personalized greeting
-      config:
-        handler: greet_handler
-```
-
-Validate again:
-
-```bash
-ossa validate hello-world.ossa.yaml
-```
-
-## Understanding the Complete Example
-
-For a fully annotated example with extensive comments, see:
-
-[examples/getting-started/hello-world-complete.ossa.yaml](https://github.com/blueflyio/openstandardagents/blob/main/examples/getting-started/hello-world-complete.ossa.yaml)
-
-This example includes:
-- Detailed comments for every field
-- All optional fields explained
-- Best practices
-- Usage examples
-
-## What You've Learned
-
-✅ OSSA agents are defined in YAML/JSON  
-✅ Agents have metadata (name, version, description)  
-✅ Agents have a spec (role, LLM, tools)  
-✅ OSSA CLI can validate agent correctness  
-✅ Tools extend agent capabilities  
-
-## Next Steps
-
-1. ✅ Hello World complete
-2. → [First Agent Creation](First-Agent) - Build a real agent
-3. → [Examples & Patterns](../Examples/Getting-Started-Examples) - See more examples
-4. → [Schema Reference](../Technical/Schema-Reference) - Deep dive into the spec
-
-## Common Questions
-
-**Q: Can I use a different LLM provider?**  
-A: Yes! OSSA supports OpenAI, Anthropic, Google, Azure, Ollama, and custom providers.
-
-**Q: What if I don't have tools?**  
-A: Tools are optional. A basic chat agent can have an empty tools array.
-
-**Q: How do I deploy this agent?**  
-A: OSSA is just a standard. Use agent-buildkit or your own deployment system.
-
-## Related
-
-- [5-Minute Overview](5-Minute-Overview)
-- [First Agent Creation](First-Agent)
-- [Complete Annotated Example](https://github.com/blueflyio/openstandardagents/blob/main/examples/getting-started/hello-world-complete.ossa.yaml)
-

package/website/content/docs/migration-guides/00-INDEX.md

@@ -1,76 +0,0 @@
----
-title: Migration Guides
-description: Migrate from existing AI frameworks to OSSA
-weight: 1
----
-
-# Migration Guides
-
-Comprehensive guides for migrating from popular AI agent frameworks to OSSA (Open Standard for Scalable Agents).
-
-## Available Guides
-
-### 🤖 Framework Migrations
-
-- **[Anthropic MCP to OSSA](./anthropic-mcp-to-ossa.md)** - Extend MCP servers with OSSA for production features
-- **[CrewAI to OSSA](./crewai-to-ossa.md)** - Migrate CrewAI crews to OSSA orchestration
-- **[LangChain to OSSA](./langchain-to-ossa.md)** - Convert LangChain agents to OSSA agents
-- **[Langflow to OSSA](./langflow-to-ossa.md)** - Transform visual flows into OSSA manifests
-- **[OpenAI to OSSA](./openai-to-ossa.md)** - Migrate OpenAI Assistants API to OSSA
-
-### 🔧 Platform Migrations
-
-- **[Drupal ECA to OSSA](./drupal-eca-to-ossa.md)** - Convert Drupal automation rules to OSSA agents
-
-## Migration Overview
-
-All OSSA migrations share common patterns:
-
-### 1. Assessment Phase
-- Inventory existing agents/workflows
-- Map components to OSSA equivalents
-- Identify production requirements
-
-### 2. Design Phase
-- Create OSSA agent manifests
-- Define capability schemas
-- Plan workflow execution
-
-### 3. Implementation Phase
-- Implement agent logic
-- Add monitoring and policies
-- Configure deployment
-
-### 4. Testing Phase
-- Unit test capabilities
-- Integration test workflows
-- Validate performance
-
-### 5. Deployment Phase
-- Deploy to target environment
-- Configure monitoring
-- Run smoke tests
-
-## Why Migrate to OSSA?
-
-### Production Features
-- ✅ **Multi-Protocol Support** - HTTP, gRPC, WebSocket, MCP, A2A
-- ✅ **Enterprise Monitoring** - Traces, metrics, logs, health checks
-- ✅ **Kubernetes Native** - Deploy and scale on K8s
-- ✅ **OpenAPI Integration** - REST APIs for all agents
-- ✅ **Compliance Ready** - ISO42001, SOC2, GDPR support
-
-### Framework Advantages
-- 🔓 **No Vendor Lock-in** - Use any LLM provider
-- 🌐 **Multi-Runtime** - Local, Docker, K8s, serverless
-- 🔌 **Interoperable** - Works with existing frameworks
-- 📊 **Observable** - Built-in monitoring and tracing
-- 🔒 **Secure** - Enterprise security and policies
-
-## Getting Help
-
-- **Documentation**: [OSSA Wiki](https://github.com/blueflyio/openstandardagents/wiki/home)
-- **Issues**: [GitHub Issues](https://github.com/blueflyio/openstandardagents/issues)
-- **Discord**: [OSSA Community](https://github.com/blueflyio/openstandardagents/discussions)
-
-Ready to migrate? Choose your framework above and get started!

package/website/content/docs/migration-guides/README.md

@@ -1,133 +0,0 @@
----
-title: "README"
----
-
-# Migration Guides
-
-Comprehensive guides for migrating to or extending with OSSA (Open Standards for Scalable Agents).
-
-## Available Guides
-
-### 1. [Anthropic MCP to OSSA](./Anthropic-MCP-to-OSSA.md)
-**Extend Anthropic Model Context Protocol servers with OSSA**
-
-- **Target Audience:** MCP server developers, Claude Desktop users
-- **Complexity:** Intermediate
-- **Time to Complete:** 2-4 hours
-- **Key Benefits:**
-  - Keep MCP compatibility
-  - Add HTTP/REST API support
-  - Enable production monitoring
-  - Deploy to Kubernetes
-  - Multi-protocol access (MCP + OpenAPI + A2A)
-
-**Topics Covered:**
-- MCP servers → OSSA agents
-- MCP tools → OSSA capabilities
-- MCP resources → OSSA data sources
-- Dual-mode implementation (stdio + HTTP)
-- Integration patterns
-- 3 complete before/after examples
-
----
-
-### 2. [LangChain to OSSA](./LangChain-to-OSSA.md)
-**Migrate Python LangChain agents to OSSA specification**
-
-- **Target Audience:** LangChain developers, Python AI engineers
-- **Complexity:** Intermediate to Advanced
-- **Time to Complete:** 4-8 hours
-- **Key Benefits:**
-  - Language-agnostic deployment
-  - Better orchestration
-  - Production-ready infrastructure
-  - Multi-framework support
-
----
-
-## Quick Decision Guide
-
-**Choose the right guide based on your current stack:**
-
-```
-Have MCP servers? → Use "Anthropic MCP to OSSA"
-├─ Already working in Claude Desktop?
-│  └─ Keep MCP, add OSSA for production features
-│
-Have LangChain agents? → Use "LangChain to OSSA"
-├─ Python-based AI workflows?
-│  └─ Migrate to OSSA for better orchestration
-│
-Starting fresh? → Check Getting Started guide
-└─ Use OSSA from day one
-```
-
-## Common Scenarios
-
-### Scenario 1: "I have MCP servers for Claude Desktop"
-→ **Use:** [Anthropic MCP to OSSA](./Anthropic-MCP-to-OSSA.md)
-- Extend with HTTP API
-- Add monitoring/metrics
-- Deploy to production
-
-### Scenario 2: "I have LangChain Python agents"
-→ **Use:** [LangChain to OSSA](./LangChain-to-OSSA.md)
-- Migrate to TypeScript/Node.js
-- Add multi-protocol support
-- Enable agent orchestration
-
-### Scenario 3: "I want to expose my agent via multiple protocols"
-→ **Use:** [Anthropic MCP to OSSA](./Anthropic-MCP-to-OSSA.md)
-- MCP for Claude Desktop
-- OpenAPI for REST clients
-- A2A for agent-to-agent communication
-
-## Migration Roadmap
-
-```
-1. Assessment (1-2 hours)
-   ├─ Inventory existing agents/servers
-   ├─ Identify required features
-   └─ Choose migration guide
-
-2. Planning (2-4 hours)
-   ├─ Map existing functionality to OSSA
-   ├─ Design agent manifest
-   └─ Plan deployment strategy
-
-3. Implementation (4-8 hours)
-   ├─ Create OSSA agent structure
-   ├─ Migrate business logic
-   ├─ Configure bridges (MCP, OpenAPI, etc.)
-   └─ Add monitoring
-
-4. Testing (2-4 hours)
-   ├─ Test all protocols
-   ├─ Verify backward compatibility
-   └─ Load testing
-
-5. Deployment (2-4 hours)
-   ├─ Deploy to target environment
-   ├─ Configure monitoring
-   └─ Update client configurations
-```
-
-## Support
-
-- **Documentation:** `/Users/flux423/Sites/LLM/agent-buildkit/docs/`
-- **Examples:** `/Users/flux423/Sites/LLM/agent-buildkit/.agents/`
-- **OSSA Spec:** [OSSA Complete Reference](../OSSA-COMPLETE-AGENT-REFERENCE.md)
-- **BuildKit CLI:** `buildkit agents --help`
-
-## Contributing
-
-Found an issue or want to add a migration guide?
-
-1. Create an issue: [GitLab Issues](https://github.com/blueflyio/documentation/-/issues)
-2. Submit a merge request with your guide
-3. Follow the existing structure and format
-
----
-
-**Last Updated:** 2025-11-10
-**Maintained By:** Agent BuildKit Team