@bluefly/openstandardagents 0.4.3 → 0.4.5

package/examples/migrations/swarm-to-ossa/after-handoffs.ossa.yaml

@@ -15,7 +15,7 @@
 # ============================================================================
 # Sales Agent - Entry Point
 # ============================================================================
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: sales-agent
@@ -81,7 +81,7 @@ spec:
 # ============================================================================
 # Order Verification Agent
 # ============================================================================
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: order-verification-agent
@@ -160,7 +160,7 @@ spec:
 # ============================================================================
 # Payment Processing Agent
 # ============================================================================
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: payment-processing-agent
@@ -270,7 +270,7 @@ spec:
 # ============================================================================
 # Fulfillment Agent
 # ============================================================================
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: fulfillment-agent
@@ -339,7 +339,7 @@ spec:
 # ============================================================================
 # Supervisor Agent
 # ============================================================================
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: supervisor-agent
@@ -421,7 +421,7 @@ spec:
 # ============================================================================
 # Workflow Orchestration (Bonus: NOT POSSIBLE in Swarm!)
 # ============================================================================
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Workflow
 metadata:
   name: order-processing-workflow

package/examples/migrations/swarm-to-ossa/after-triage-agent.ossa.yaml

@@ -10,7 +10,7 @@
 # - 50% less code
 # - Enterprise features built-in
 
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: customer-service-triage
@@ -139,7 +139,7 @@ spec:
 
 ---
 # Sales Agent (equivalent to sales_agent in Swarm)
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: sales-agent
@@ -223,7 +223,7 @@ spec:
 
 ---
 # Refunds Agent (equivalent to refunds_agent in Swarm)
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: refunds-agent

package/examples/minimal/agent.yml

@@ -132,7 +132,7 @@ api:
 #
 # To create a new agent from this template:
 #
-#   ossa init my-agent --template minimal
+#   ossa init supercali-fragilisticagent --template minimal
 #   # Then customize agent.yml with your values
 #
 # To run this agent locally:

package/examples/mr-reviewer-with-governance.ossa.yaml

@@ -0,0 +1,130 @@
+apiVersion: ossa/v0.4.5
+kind: Agent
+metadata:
+  name: mr-reviewer
+  version: 1.0.0
+  description: Automated merge request reviewer with Cedar governance
+  labels:
+    category: code-review
+    risk-level: medium
+    environment: production
+
+spec:
+  role: |
+    You are an automated code reviewer that analyzes merge requests,
+    provides constructive feedback, and ensures code quality standards.
+
+    You operate under strict governance controls with Cedar policies
+    enforcing authorization and quality gates.
+
+  llm:
+    provider: anthropic
+    model: claude-sonnet-3-5
+    temperature: 0.3
+    maxTokens: 4000
+
+  # NEW: Governance configuration
+  governance:
+    authorization:
+      # Standard agent clearance (can use medium-risk tools)
+      clearance_level: 2
+
+      tool_permissions:
+        - tool: gitlab_api
+          risk_level: medium
+          requires_approval: false
+        - tool: llm_inference
+          risk_level: low
+          requires_approval: false
+        - tool: code_analysis
+          risk_level: medium
+          requires_approval: false
+
+      # Reference Cedar policies by ID
+      policy_references:
+        - agent-tool-medium-risk
+        - mr-review-policy
+
+    quality_requirements:
+      # High confidence required for production
+      confidence_threshold: 85
+      test_coverage_threshold: 80
+      security_score_threshold: 90
+      max_vulnerability_count: 0
+
+    compliance:
+      frameworks:
+        - SOC2
+      data_classification: internal
+      audit_logging_required: true
+
+  tools:
+    - name: gitlab_api
+      description: GitLab API for accessing MR data
+      risk_level: medium
+
+    - name: code_analysis
+      description: Static code analysis tools
+      risk_level: medium
+
+    - name: llm_inference
+      description: LLM inference for code review
+      risk_level: low
+
+  workflow:
+    steps:
+      - id: fetch_mr
+        name: Fetch MR Changes
+        description: Retrieve MR diff and metadata from GitLab
+        tool: gitlab_api
+
+      - id: analyze
+        name: Analyze Code
+        description: Run static analysis on changed files
+        tool: code_analysis
+        depends_on:
+          - fetch_mr
+
+      - id: review
+        name: Generate Review
+        description: Generate detailed code review using LLM
+        tool: llm_inference
+        depends_on:
+          - analyze
+
+      - id: post_comment
+        name: Post Review Comment
+        description: Post review feedback to MR
+        tool: gitlab_api
+        depends_on:
+          - review
+
+  monitoring:
+    metrics:
+      - name: review_quality_score
+        type: gauge
+        description: Quality score of generated reviews
+
+      - name: confidence_score
+        type: gauge
+        description: Confidence in review accuracy
+
+      - name: reviews_completed
+        type: counter
+        description: Total reviews completed
+
+  # Quality gates enforced by Cedar policies
+  deployment:
+    environments:
+      - name: staging
+        quality_gate:
+          min_confidence: 70
+          min_coverage: 60
+          min_security: 70
+
+      - name: production
+        quality_gate:
+          min_confidence: 85
+          min_coverage: 80
+          min_security: 90
+          max_vulnerabilities: 0

package/examples/multi-agent/conditional-router.ossa.yaml

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

package/examples/multi-agent/parallel-execution.ossa.yaml

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

package/examples/multi-agent/sequential-pipeline.ossa.yaml

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

package/examples/multi-agent-research-workflow.ossa.yaml

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

package/examples/multi-platform/single-manifest/agent.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: multi-platform-demo

package/examples/observability/activity-stream-full.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: activity-tracked-agent

package/examples/openai/basic-agent.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: basic-openai-agent

package/examples/ossa-templates/01-code-assistant.ossa.yaml

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

package/examples/ossa-templates/02-security-scanner.ossa.yaml

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

package/examples/ossa-templates/03-ci-pipeline.ossa.yaml

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

package/examples/ossa-templates/04-code-reviewer.ossa.yaml

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

package/examples/ossa-templates/05-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/ossa-templates/06-compliance-validator.ossa.yaml

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

package/examples/ossa-templates/07-workflow-orchestrator.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Workflow
 metadata:
   name: workflow-orchestrator

package/examples/ossa-templates/08-content-writer.ossa.yaml

@@ -7,7 +7,7 @@
 # Showcases: Drupal extension, async processing (Messenger), ECA integration
 # ============================================================================
 
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: content-writer

package/examples/ossa-templates/09-test-generator.ossa.yaml

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

package/examples/ossa-templates/10-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/ossa-templates/11-react-performance-expert.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: react-performance-expert

package/examples/ossa-templates/12-typescript-type-safety-expert.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: typescript-type-safety-expert

package/examples/ossa-templates/13-accessibility-champion.ossa.yaml

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

package/examples/ossa-templates/14-security-hardening-agent.ossa.yaml

@@ -1,4 +1,4 @@
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Agent
 metadata:
   name: security-hardening-agent

package/examples/pipeline-agent.ossa.yaml

@@ -0,0 +1,196 @@
+# OSSA v0.4.5 Example: Pipeline Agent — Data Processing Pipeline
+#
+# Demonstrates the pipeline pattern for sequential data processing. A
+# coordinator manages four team members arranged as sequential stages:
+# ingest, transform, validate, and export. Each stage has specific tools
+# for its responsibility and hands off to the next stage upon completion.
+#
+# Key characteristics:
+#   - Pipeline pattern with sequential stages
+#   - Hub-spoke team model (coordinator manages stage transitions)
+#   - Each member represents one pipeline stage
+#   - Stage-specific tool sets
+#   - Assigned task coordination (coordinator assigns stage work)
+#   - Database-backed persistence for auditability
+
+apiVersion: ossa/v0.4.5
+kind: Agent
+metadata:
+  name: data-processing-pipeline
+  version: "1.0.0"
+  description: >-
+    A data processing pipeline with four sequential stages: ingest (fetch and
+    normalize raw data), transform (apply business rules and enrichment),
+    validate (quality checks and schema validation), and export (write to
+    destination systems). Each stage is an independent agent with its own
+    tools and model.
+
+  agentKind: coordinator
+  agentType: workflow
+
+  agentArchitecture:
+    pattern: pipeline
+    capabilities:
+      - tools
+      - function-calling
+      - streaming
+    coordination:
+      handoffStrategy: conditional
+      leaderAgent: pipeline-controller
+      maxDepth: 1
+      teamModel: hub-spoke
+      communicationPattern: shared-file
+      taskCoordination: assigned
+      conflictResolution: leader-decides
+      taskPersistence: database
+      dependencyTracking: true
+
+  labels:
+    domain: data
+    pattern: pipeline
+    environment: production
+
+spec:
+  role: >-
+    You are the pipeline controller for a four-stage data processing workflow.
+    For each data batch:
+    1. Assign the batch to the ingest stage to fetch and normalize raw data.
+    2. Pass the normalized output to the transform stage for enrichment.
+    3. Send transformed data to the validate stage for quality checks.
+    4. Route validated data to the export stage for delivery.
+    Monitor each stage for errors. If a stage fails, log the error and skip
+    to the next batch. Maintain pipeline metrics (throughput, error rate,
+    latency per stage).
+
+  llm:
+    provider: anthropic
+    model: claude-sonnet-4-5-20250929
+    temperature: 0.1
+    maxTokens: 2048
+    profile: fast
+
+  team:
+    model: hub-spoke
+    lead: pipeline-controller
+    delegateMode: true
+
+    members:
+      - name: ingest-stage
+        kind: teammate
+        role: >-
+          Stage 1: Data Ingestion. Fetch raw data from configured sources
+          (APIs, S3 buckets, databases). Normalize into a common internal
+          format (JSON Lines). Handle pagination, rate limiting, and partial
+          failures. Output normalized records to the shared staging area.
+        model:
+          provider: anthropic
+          name: claude-haiku-4-5-20250514
+        tools:
+          - fetch_api
+          - read_s3
+          - query_database
+          - write_staging
+        contextIsolation: true
+        workingDirectory: /pipeline/ingest
+        handoffs:
+          - to: pipeline-controller
+            condition: "Ingestion complete or fatal error"
+
+      - name: transform-stage
+        kind: teammate
+        role: >-
+          Stage 2: Data Transformation. Read normalized records from staging.
+          Apply business rules: field mapping, currency conversion, date
+          normalization, and entity enrichment from reference tables. Output
+          enriched records to the transform output area.
+        model:
+          provider: anthropic
+          name: claude-haiku-4-5-20250514
+        tools:
+          - read_staging
+          - apply_mapping
+          - enrich_entity
+          - write_transform_output
+        contextIsolation: true
+        workingDirectory: /pipeline/transform
+        handoffs:
+          - to: pipeline-controller
+            condition: "Transformation complete or fatal error"
+
+      - name: validate-stage
+        kind: teammate
+        role: >-
+          Stage 3: Data Validation. Read transformed records and run quality
+          checks: schema validation, referential integrity, business rule
+          assertions, and anomaly detection. Flag invalid records and produce
+          a validation report. Output clean records to the validated area.
+        model:
+          provider: anthropic
+          name: claude-sonnet-4-5-20250929
+        tools:
+          - read_transform_output
+          - validate_schema
+          - check_integrity
+          - write_validated_output
+        contextIsolation: true
+        workingDirectory: /pipeline/validate
+        handoffs:
+          - to: pipeline-controller
+            condition: "Validation complete or fatal error"
+
+      - name: export-stage
+        kind: teammate
+        role: >-
+          Stage 4: Data Export. Read validated records and write to destination
+          systems: data warehouse, analytics database, or external APIs.
+          Handle batching, idempotency, and delivery confirmation. Produce
+          an export receipt with record counts and delivery timestamps.
+        model:
+          provider: anthropic
+          name: claude-haiku-4-5-20250514
+        tools:
+          - read_validated_output
+          - write_warehouse
+          - call_external_api
+          - write_export_receipt
+        contextIsolation: true
+        workingDirectory: /pipeline/export
+        handoffs:
+          - to: pipeline-controller
+            condition: "Export complete or fatal error"
+
+    taskList:
+      coordination: assigned
+      persistence: database
+      stateModel:
+        - pending
+        - in-progress
+        - completed
+        - failed
+        - skipped
+      dependencyTracking: true
+      waveExecution: false
+      lockingStrategy: optimistic
+
+    communication:
+      pattern: shared-file
+      broadcastEnabled: false
+
+    deployment:
+      backend: distributed
+      scaling: auto
+
+  constraints:
+    cost:
+      maxTokensPerDay: 1000000
+      maxCostPerDay: 40.00
+      currency: USD
+    performance:
+      maxLatencySeconds: 60
+      maxConcurrentRequests: 10
+      timeoutSeconds: 300
+
+  lifecycle:
+    max_turns: 100
+    turn_timeout: 60s
+    checkpoint_interval: 10