@bluefly/openstandardagents 0.4.3 → 0.4.5

package/examples/showcase/data-processing-pipeline.ossa.yaml

@@ -0,0 +1,254 @@
+apiVersion: ossa/v0.4.5
+kind: Agent
+metadata:
+  name: data-processing-pipeline
+  version: 1.0.0
+  description: Data processing pipeline agent with ETL, transformation, and validation capabilities using pandas, dbt, and great_expectations
+  labels:
+    ossa.dev/category: data-processing
+    ossa.dev/tier: production-example
+    ossa.dev/autonomy: supervised
+    ossa.dev/domain: data-engineering
+  annotations:
+    ossa.dev/documentation: https://openstandardagents.org/agents/data-processing-pipeline
+    ossa.dev/tools: pandas,dbt,great_expectations
+    ossa.dev/a2a-enabled: "false"
+spec:
+  capabilities:
+  - type: function
+    name: etl.extract
+    description: Extract data from various sources
+    parameters:
+      type: object
+      properties:
+        source_type:
+          type: string
+          enum: [database, api, file, stream]
+          description: Type of data source
+        source_config:
+          type: object
+          description: Source connection configuration
+          properties:
+            url:
+              type: string
+            credentials:
+              type: object
+            options:
+              type: object
+        query:
+          type: string
+          description: Query or filter criteria
+      required: [source_type, source_config]
+  - type: function
+    name: etl.transform
+    description: Transform data using pandas and dbt
+    parameters:
+      type: object
+      properties:
+        transformation_type:
+          type: string
+          enum: [pandas, dbt, sql, custom]
+        rules:
+          type: array
+          items:
+            type: object
+            properties:
+              operation:
+                type: string
+                enum: [filter, aggregate, join, pivot, normalize]
+              parameters:
+                type: object
+        output_schema:
+          type: object
+          description: Expected output schema
+      required: [transformation_type, rules]
+  - type: function
+    name: etl.load
+    description: Load transformed data to destination
+    parameters:
+      type: object
+      properties:
+        destination_type:
+          type: string
+          enum: [database, data_warehouse, data_lake, file, api]
+        destination_config:
+          type: object
+        load_mode:
+          type: string
+          enum: [append, overwrite, upsert, merge]
+          default: append
+        batch_size:
+          type: integer
+          default: 1000
+      required: [destination_type, destination_config]
+  - type: function
+    name: validation.run
+    description: Validate data quality using great_expectations
+    parameters:
+      type: object
+      properties:
+        expectations:
+          type: array
+          items:
+            type: object
+            properties:
+              type:
+                type: string
+              column:
+                type: string
+              parameters:
+                type: object
+        checkpoint:
+          type: string
+          description: Great Expectations checkpoint name
+      required: [expectations]
+  role: |
+    You are a data processing pipeline specialist responsible for ETL operations,
+    data transformations, and data quality validation.
+
+    Your core responsibilities:
+    1. Data Extraction - Pull data from databases, APIs, files, and streams
+    2. Data Transformation - Apply business logic using pandas, dbt, SQL
+    3. Data Loading - Write processed data to destinations
+    4. Data Validation - Ensure data quality using great_expectations
+    5. Pipeline Orchestration - Coordinate multi-step data workflows
+
+    Tools and frameworks:
+    - pandas: In-memory data manipulation and analysis
+    - dbt: SQL-based data transformations and modeling
+    - great_expectations: Data quality validation and profiling
+
+    Always:
+    - Validate input data before processing
+    - Log transformation steps for audit trail
+    - Handle errors gracefully with retry logic
+    - Monitor data quality metrics
+    - Provide detailed processing statistics
+    - Respect memory limits and batch processing
+  llm:
+    provider: anthropic
+    model: claude-sonnet-4
+    temperature: 0.2
+    maxTokens: 16384
+    features:
+      promptCaching: false
+      tokenEfficiency: false
+      batchProcessing: true
+  tools:
+  - type: function
+    name: pandas.transform
+    description: Data manipulation and analysis using pandas
+  - type: function
+    name: dbt.transform
+    description: SQL-based transformation using dbt
+  - type: function
+    name: great_expectations.validate
+    description: Data validation using great_expectations
+  - type: function
+    name: database.connect
+    description: Connect to various databases
+  - type: function
+    name: file.read
+    description: Read files in various formats (CSV, JSON, Parquet, Excel)
+  - type: function
+    name: api.fetch
+    description: Fetch data from REST APIs
+  autonomy:
+    mode: supervised
+    humanApproval: true
+    approvalRequired:
+      - before_load
+      - on_validation_failure
+      - on_schema_change
+    escalation:
+      enabled: true
+      triggers:
+        - data_quality_failure
+        - transformation_error
+        - destination_unavailable
+      contacts:
+        - role: data_engineer
+          method: slack
+        - role: data_ops
+          method: pagerduty
+  observability:
+    metrics:
+      enabled: true
+      provider: prometheus
+      port: 9091
+      custom:
+        - name: records_processed
+          type: counter
+        - name: processing_duration
+          type: histogram
+        - name: validation_failures
+          type: counter
+        - name: data_quality_score
+          type: gauge
+    logging:
+      level: info
+      format: json
+      destination: stdout
+      structured: true
+    tracing:
+      enabled: true
+      provider: opentelemetry
+      samplingRate: 1.0
+  resources:
+    memory: 8Gi
+    cpu: 4000m
+    storage: 100Gi
+    gpu:
+      enabled: false
+    limits:
+      memory: 16Gi
+      cpu: 8000m
+  state:
+    persistence: redis
+    ttl: 86400  # 24 hours
+    schema:
+      type: object
+      properties:
+        pipeline_state:
+          type: string
+          enum: [idle, extracting, transforming, loading, validating, completed, failed]
+        processed_records:
+          type: integer
+        current_batch:
+          type: integer
+        last_checkpoint:
+          type: string
+        statistics:
+          type: object
+  scheduling:
+    enabled: true
+    cron: "0 2 * * *"  # Daily at 2 AM
+    timezone: UTC
+    maxConcurrent: 1
+  retry:
+    enabled: true
+    maxAttempts: 3
+    backoff:
+      type: exponential
+      initialDelay: 5s
+      maxDelay: 300s
+      multiplier: 2
+  security:
+    authentication:
+      required: true
+      methods:
+        - oauth2
+        - service_account
+    authorization:
+      rbac:
+        enabled: true
+        roles:
+          - data_engineer
+          - data_analyst
+          - pipeline_admin
+    dataClassification:
+      - PII
+      - sensitive
+    encryption:
+      at_rest: true
+      in_transit: true

package/examples/showcase/data-transformer.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Task
 metadata:
   name: data-transformer

package/examples/showcase/doc-generator.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: doc-generator

package/examples/showcase/full-power-agent.ossa.yaml

@@ -0,0 +1,350 @@
+# ─────────────────────────────────────────────────────────────────────────────
+# OSSA Showcase: Full-Power Agent Card
+# ─────────────────────────────────────────────────────────────────────────────
+# This manifest demonstrates EVERY feature OSSA supports.
+# Run: ossa agent-card generate examples/showcase/full-power-agent.ossa.yaml --stdout
+#
+# "Every Agent Needs a Contract" — this IS that contract.
+# One manifest. One standard. Every platform.
+# MCP connects tools. A2A connects agents. OSSA defines the contract.
+# ─────────────────────────────────────────────────────────────────────────────
+
+apiVersion: ossa/v0.4.5
+kind: Agent
+metadata:
+  name: enterprise-support-orchestrator
+  version: 2.1.0
+  description: >
+    Enterprise-grade multi-agent orchestrator with full MCP tool integration,
+    A2A agent-to-agent communication, autonomous escalation, cost governance,
+    and production observability. The definitive OSSA showcase.
+
+  # ── Agent Taxonomy ──
+  agentType: claude                       # Runtime: claude, kagent, openai, langchain, crewai
+  agentKind: orchestrator                 # Role: orchestrator, worker, reviewer, analyzer
+
+  agentArchitecture:
+    pattern: swarm                        # Pattern: swarm, pipeline, tree, graph
+    capabilities:
+      - handoff                           # Can transfer to other agents
+      - streaming                         # Supports streaming responses
+      - context                           # Maintains conversation context
+      - tools                             # Can call external tools
+      - vision                            # Can process images/screenshots
+      - code-execution                    # Can execute code safely
+    coordination:
+      handoffStrategy: automatic          # automatic, manual, hybrid
+      maxDepth: 5                         # Max orchestration depth
+    runtime:
+      scalability: horizontal             # horizontal, vertical, none
+      executionModel: streaming           # streaming, batch, request-response
+      preferredRegion: us-east-1
+
+  labels:
+    domain: enterprise-support
+    team: platform-engineering
+    environment: production
+    capability: support,escalation,routing,analysis
+    framework: a2a
+    tier: tier-3
+    compliance: soc2,gdpr
+
+  annotations:
+    documentation: https://docs.example.com/agents/enterprise-support
+    runbook: https://runbooks.example.com/enterprise-support
+    support: platform-eng@example.com
+    sla: "99.9%"
+
+spec:
+  # ── LLM Configuration ──
+  model:
+    provider: anthropic
+    name: claude-sonnet-4-5-20250929
+    temperature: 0.7
+    max_tokens: 8192
+
+  # ── System Prompt ──
+  system: |
+    You are an enterprise support orchestrator managing a team of specialist agents.
+    Route requests to the right specialist, maintain context across handoffs,
+    and ensure every customer interaction meets SLA requirements.
+
+    Specialist Team:
+    - @technical-support: Deep technical troubleshooting
+    - @billing-support: Billing, invoicing, subscription management
+    - @security-ops: Security incidents and access reviews
+    - @product-specialist: Feature requests and product guidance
+
+  # ── Tools ──
+  tools:
+    - name: route_to_specialist
+      description: Route customer request to appropriate specialist agent
+      input_schema:
+        type: object
+        required: [agentId, reason, priority]
+        properties:
+          agentId:
+            type: string
+            description: Target specialist agent ID
+          reason:
+            type: string
+            description: Why this specialist is appropriate
+          priority:
+            type: string
+            enum: [low, medium, high, critical]
+          context:
+            type: object
+            description: Conversation context to pass along
+
+    - name: search_knowledge_base
+      description: Search enterprise knowledge base for relevant articles
+      input_schema:
+        type: object
+        required: [query]
+        properties:
+          query:
+            type: string
+          category:
+            type: string
+            enum: [technical, billing, security, product, general]
+          limit:
+            type: integer
+            default: 5
+
+    - name: create_ticket
+      description: Create a support ticket in the ticketing system
+      input_schema:
+        type: object
+        required: [title, description, priority]
+        properties:
+          title:
+            type: string
+          description:
+            type: string
+          priority:
+            type: string
+            enum: [low, medium, high, critical]
+          assignee:
+            type: string
+
+    - name: check_sla_status
+      description: Check SLA compliance for current interaction
+      input_schema:
+        type: object
+        required: [ticketId]
+        properties:
+          ticketId:
+            type: string
+          includeHistory:
+            type: boolean
+            default: false
+
+  # ── Handoffs ──
+  handoffs:
+    - to: technical-support
+      condition: "user reports bugs, errors, or system issues"
+    - to: billing-support
+      condition: "user has billing, payment, or subscription questions"
+    - to: security-ops
+      condition: "user reports security incidents or needs access reviews"
+    - to: product-specialist
+      condition: "user requests features or needs product guidance"
+
+  # ── Autonomy ──
+  autonomy:
+    level: semi-autonomous
+    approval_required: false
+    allowed_actions:
+      - route_to_specialist
+      - search_knowledge_base
+      - create_ticket
+      - check_sla_status
+    blocked_actions:
+      - delete_account
+      - modify_billing
+      - grant_admin_access
+
+  # ── Constraints ──
+  constraints:
+    cost:
+      maxTokensPerDay: 500000
+      maxTokensPerRequest: 16384
+      maxCostPerDay: 50.00
+      currency: USD
+    performance:
+      maxLatencySeconds: 3.0
+      maxConcurrentRequests: 50
+      timeoutSeconds: 60
+    resources:
+      cpu: 500m
+      memory: 1Gi
+
+  # ── Observability ──
+  observability:
+    tracing:
+      enabled: true
+      exporter: otlp
+      endpoint: https://otel.example.com:4318
+      samplingRate: 1.0
+    metrics:
+      enabled: true
+      exporter: prometheus
+      endpoint: https://metrics.example.com/push
+    logging:
+      level: info
+      format: json
+
+  # ── Extensions ──
+  extensions:
+    # ── MCP Tool Servers ──
+    mcp:
+      servers:
+        - name: knowledge-base
+          description: Enterprise knowledge base search via MCP
+          transport:
+            type: stdio
+            command: npx
+            args: ["-y", "@example/mcp-knowledge-base", "--index", "support"]
+          version: "1.2.0"
+          capabilities:
+            resources:
+              subscribe: true
+              listChanged: true
+            tools:
+              listChanged: true
+            logging:
+              enabled: true
+              level: info
+
+        - name: ticketing-system
+          description: Jira/ServiceNow integration via MCP
+          transport:
+            type: sse
+            url: https://mcp.example.com/ticketing
+          version: "2.0.0"
+          capabilities:
+            tools:
+              listChanged: true
+
+      resources:
+        - uri: "kb://support/faq"
+          name: "Support FAQ"
+          description: "Frequently asked questions for customer support"
+          mimeType: "application/json"
+        - uri: "kb://support/runbooks"
+          name: "Runbooks"
+          description: "Operational runbooks for common issues"
+          mimeType: "text/markdown"
+
+    # ── A2A Agent Protocol ──
+    a2a:
+      enabled: true
+
+      protocol:
+        type: json-rpc
+        version: "2.0"
+        messageFormat: json
+        timeout: 60
+
+      endpoints:
+        - agentId: "@technical-support"
+          url: "https://agents.example.com/technical-support/a2a"
+          capabilities: ["debugging", "troubleshooting", "log-analysis"]
+          priority: 10
+
+        - agentId: "@billing-support"
+          url: "https://agents.example.com/billing-support/a2a"
+          capabilities: ["billing", "payments", "subscriptions"]
+          priority: 8
+
+        - agentId: "@security-ops"
+          url: "https://agents.example.com/security-ops/a2a"
+          capabilities: ["incident-response", "access-review", "threat-analysis"]
+          priority: 15
+
+        - agentId: "@product-specialist"
+          url: "https://agents.example.com/product-specialist/a2a"
+          capabilities: ["features", "roadmap", "product-guidance"]
+          priority: 5
+
+      routing:
+        strategy: priority-based
+        routingRules:
+          - name: "security-critical"
+            condition: "message.category == 'security' || message.priority == 'critical'"
+            target: "@security-ops"
+            priority: 20
+
+          - name: "technical-escalation"
+            condition: "message.category == 'technical' && message.complexity > 3"
+            target: "@technical-support"
+            priority: 10
+
+          - name: "billing-routing"
+            condition: "message.category == 'billing'"
+            target: "@billing-support"
+            priority: 8
+
+      delegation:
+        enabled: true
+        maxDepth: 3
+        timeout: 300
+        handoff:
+          enabled: true
+          preserveContext: true
+          handoffRules:
+            - name: "confidence-handoff"
+              condition: "confidence < 0.4"
+              target: "@technical-support"
+              message: "Low confidence — escalating to specialist"
+
+            - name: "vip-handoff"
+              condition: "customer.tier == 'enterprise'"
+              target: "@product-specialist"
+              message: "Enterprise customer requiring priority handling"
+
+      completionSignals:
+        enabled: true
+        signals: ["continue", "complete", "blocked", "escalate"]
+        handlers:
+          - signal: escalate
+            action: handoff
+            target: "@security-ops"
+          - signal: blocked
+            action: handoff
+            target: "@technical-support"
+          - signal: complete
+            action: notify
+
+      authentication:
+        type: jwt
+        jwt:
+          algorithm: RS256
+          issuer: agents.example.com
+
+      retryPolicy:
+        enabled: true
+        maxRetries: 3
+        backoff: exponential
+        retryableErrors:
+          - "UNAVAILABLE"
+          - "TIMEOUT"
+          - "RATE_LIMITED"
+
+      circuitBreaker:
+        enabled: true
+        failureThreshold: 5
+        successThreshold: 2
+        timeout: 120
+
+      observability:
+        tracing:
+          enabled: true
+          provider: opentelemetry
+          samplingRate: 1.0
+        metrics:
+          enabled: true
+          endpoint: "/metrics"
+        logging:
+          level: info
+          format: json