@bluefly/openstandardagents 0.4.3 → 0.4.5

package/examples/subagents-pipeline.ossa.yaml

@@ -0,0 +1,76 @@
+apiVersion: ossa/v0.4
+kind: Agent
+metadata:
+  name: content-pipeline
+  version: 1.0.0
+  description: Parent-child delegation pattern with subagents in a pipeline
+  agentType: claude
+  agentKind: orchestrator
+  agentArchitecture:
+    pattern: pipeline
+    capabilities:
+      - tools
+      - code
+      - context
+spec:
+  role: >
+    You orchestrate a content creation pipeline. Delegate research,
+    writing, and editing to specialized subagents in sequence.
+  llm:
+    provider: anthropic
+    model: claude-sonnet-4-5-20250514
+  subagents:
+    - name: researcher
+      kind: specialist
+      role: >
+        Research and gather information on the given topic.
+        Return structured notes with sources.
+      model: claude-sonnet-4-5-20250514
+      tools:
+        - web-search
+        - read-file
+        - summarize
+      contextIsolation: true
+      reportTo: content-pipeline
+      maxTokenBudget: 20000
+    - name: writer
+      kind: worker
+      role: >
+        Write content based on research notes. Follow the
+        specified tone, format, and length requirements.
+      model: claude-sonnet-4-5-20250514
+      tools:
+        - write-file
+        - format-markdown
+      contextIsolation: true
+      reportTo: content-pipeline
+      maxTokenBudget: 30000
+    - name: editor
+      kind: reviewer
+      role: >
+        Review and edit written content for clarity, accuracy,
+        grammar, and adherence to style guide.
+      model: claude-sonnet-4-5-20250514
+      tools:
+        - read-file
+        - write-file
+        - grammar-check
+      contextIsolation: true
+      reportTo: content-pipeline
+      maxTokenBudget: 15000
+    - name: fact-checker
+      kind: debugger
+      role: >
+        Verify factual claims in the content against reliable sources.
+        Flag any unverified or incorrect assertions.
+      tools:
+        - web-search
+        - read-file
+      contextIsolation: true
+      reportTo: content-pipeline
+      maxTokenBudget: 10000
+  constraints:
+    cost:
+      maxTokensPerDay: 1000000
+    performance:
+      timeoutSeconds: 300

package/examples/swarm-agent.ossa.yaml

@@ -0,0 +1,136 @@
+# OSSA v0.4.5 Example: Swarm Agent — OpenAI-Style Support Swarm
+#
+# Demonstrates the swarm pattern with hub-spoke coordination. A triage
+# coordinator routes conversations to specialist agents via automatic
+# handoffs. Each member handles a specific domain and can hand back to
+# triage when the query falls outside its scope.
+#
+# Key characteristics:
+#   - Hub-spoke model: triage agent is the central hub
+#   - Direct communication: agents hand off control directly
+#   - Assigned task coordination: triage decides who handles what
+#   - In-memory persistence: no durable task list needed
+
+apiVersion: ossa/v0.4.5
+kind: Agent
+metadata:
+  name: support-swarm
+  version: "1.0.0"
+  description: >-
+    An OpenAI Swarm-style customer support system. A triage coordinator
+    routes incoming queries to specialist agents (orders, returns, billing)
+    via automatic handoffs. Each specialist can hand back to triage when
+    it encounters an out-of-scope request.
+
+  agentKind: coordinator
+  agentType: a2a
+
+  agentArchitecture:
+    pattern: swarm
+    capabilities:
+      - handoff
+      - streaming
+      - context
+      - tools
+    coordination:
+      handoffStrategy: automatic
+      leaderAgent: triage-agent
+      teamModel: hub-spoke
+      communicationPattern: direct
+      taskCoordination: assigned
+      conflictResolution: leader-decides
+      taskPersistence: in-memory
+
+  labels:
+    domain: customer-support
+    pattern: swarm
+    framework: openai-swarm
+
+spec:
+  role: >-
+    You are the triage coordinator for a customer support swarm. Analyze
+    incoming customer messages and route them to the appropriate specialist
+    agent. If a specialist hands back to you, re-evaluate and route to a
+    different specialist or handle the query directly.
+
+  llm:
+    provider: openai
+    model: gpt-4o
+    temperature: 0.2
+    maxTokens: 1024
+
+  team:
+    model: hub-spoke
+    lead: triage-agent
+    delegateMode: false
+
+    members:
+      - name: order-agent
+        kind: teammate
+        role: >-
+          Handle order-related queries: order status, shipment tracking,
+          order modifications, and cancellations.
+        model:
+          provider: openai
+          name: gpt-4o-mini
+        tools:
+          - lookup_order
+          - track_shipment
+          - cancel_order
+        contextIsolation: true
+        handoffs:
+          - to: triage-agent
+            condition: "Query is not order-related"
+          - to: returns-agent
+            condition: "Customer wants to return an ordered item"
+
+      - name: returns-agent
+        kind: teammate
+        role: >-
+          Process returns and exchanges. Validate return eligibility, generate
+          return labels, and track return shipments.
+        model:
+          provider: openai
+          name: gpt-4o-mini
+        tools:
+          - initiate_return
+          - check_return_status
+          - generate_return_label
+        contextIsolation: true
+        handoffs:
+          - to: triage-agent
+            condition: "Query is not returns-related"
+          - to: billing-agent
+            condition: "Customer asks about refund timing or amount"
+
+      - name: billing-agent
+        kind: teammate
+        role: >-
+          Handle billing and payment queries. Look up invoices, process
+          refunds, and answer payment-related questions.
+        model:
+          provider: openai
+          name: gpt-4o-mini
+        tools:
+          - lookup_invoice
+          - process_refund
+          - check_payment_status
+        contextIsolation: true
+        handoffs:
+          - to: triage-agent
+            condition: "Query is not billing-related"
+
+    taskList:
+      coordination: assigned
+      persistence: in-memory
+      stateModel:
+        - pending
+        - in-progress
+        - completed
+      dependencyTracking: false
+      waveExecution: false
+      lockingStrategy: none
+
+    communication:
+      pattern: direct
+      broadcastEnabled: false

package/examples/swarm-handoff.ossa.yaml

@@ -0,0 +1,67 @@
+apiVersion: ossa/v0.4
+kind: Agent
+metadata:
+  name: customer-support-swarm
+  version: 1.0.0
+  description: OpenAI Swarm pattern - triage agent routes to specialists via handoffs
+  agentType: openai
+  agentKind: coordinator
+  agentArchitecture:
+    pattern: swarm
+    capabilities:
+      - handoff
+      - tools
+      - context
+    coordination:
+      handoffStrategy: automatic
+      teamModel: swarm
+spec:
+  role: >
+    You are the triage agent for customer support. Route incoming
+    requests to the appropriate specialist agent.
+  llm:
+    provider: openai
+    model: gpt-4o
+  team:
+    model: swarm
+    lead: triage
+    delegateMode: capability-match
+    members:
+      - name: triage
+        kind: team-lead
+        role: >
+          Route customer requests to the correct specialist.
+          Analyze intent and handoff to sales, support, or billing.
+        tools:
+          - classify-intent
+      - name: sales-agent
+        kind: teammate
+        role: >
+          Handle sales inquiries, product information, pricing,
+          and purchase assistance.
+        tools:
+          - product-catalog
+          - pricing-api
+          - create-quote
+      - name: support-agent
+        kind: teammate
+        role: >
+          Handle technical support, troubleshooting, and bug reports.
+        tools:
+          - knowledge-base
+          - ticket-system
+          - diagnostic-tool
+      - name: billing-agent
+        kind: teammate
+        role: >
+          Handle billing inquiries, invoices, refunds, and payment issues.
+        tools:
+          - billing-api
+          - invoice-lookup
+          - refund-process
+    communication:
+      channel: direct-message
+      consensus: leader-decides
+    deployment:
+      backend: in-process
+      maxConcurrency: 4

package/examples/tasks/batch-email-sender.yaml

@@ -1,6 +1,6 @@
 # Example: Batch Email Sender Task
 # A deterministic batch task that sends emails to multiple recipients
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Task
 metadata:
   name: batch-email-sender

package/examples/tasks/data-transform.yaml

@@ -1,6 +1,6 @@
 # Example: Data Transform Task
 # A pure function task that transforms data between formats
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Task
 metadata:
   name: data-transform

package/examples/tasks/publish-content.yaml

@@ -1,6 +1,6 @@
 # Example: Publish Content Task
 # A deterministic task that publishes content - no AI required
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Task
 metadata:
   name: publish-content

package/examples/team-agent.ossa.yaml

@@ -0,0 +1,159 @@
+# OSSA v0.4.5 Example: Team Agent — Claude Code Lead-Teammate Team
+#
+# Demonstrates the lead-teammate pattern modeled after Claude Code Agent
+# Teams. An Opus lead orchestrates Sonnet workers and a Haiku explorer.
+# The lead operates in delegate mode (never implements directly), while
+# teammates self-claim tasks from a shared, file-backed task list with
+# dependency tracking and wave execution.
+#
+# Key characteristics:
+#   - Lead-teammate model with delegate mode
+#   - Shared task list with self-claim coordination
+#   - File-backed persistence with dependency tracking
+#   - Mailbox communication (async, inbox-based)
+#   - Mixed model tiers (Opus lead, Sonnet workers, Haiku explorer)
+#   - In-process deployment with fixed scaling
+
+apiVersion: ossa/v0.4.5
+kind: Agent
+metadata:
+  name: fullstack-dev-team
+  version: "1.0.0"
+  description: >-
+    A Claude Code-style development team for fullstack feature implementation.
+    An Opus lead decomposes tasks and coordinates three teammates: a backend
+    worker (Sonnet), a frontend worker (Sonnet), and a codebase explorer
+    (Haiku). Teammates self-claim tasks from a shared list, communicate via
+    mailbox, and work in isolated directories.
+
+  agentKind: team-lead
+  agentType: a2a
+
+  agentArchitecture:
+    pattern: lead-teammate
+    capabilities:
+      - tools
+      - code
+      - context
+      - function-calling
+      - memory
+    coordination:
+      handoffStrategy: automatic
+      leaderAgent: lead
+      maxDepth: 2
+      teamModel: lead-teammate
+      communicationPattern: mailbox
+      taskCoordination: self-claim
+      conflictResolution: leader-decides
+      taskPersistence: file-backed
+      dependencyTracking: true
+
+  labels:
+    domain: development
+    pattern: lead-teammate
+    framework: claude-code
+
+spec:
+  role: >-
+    You are the lead of a fullstack development team. Your job is to:
+    1. Analyze the user's feature request and decompose it into tasks.
+    2. Create tasks in the shared task list with clear descriptions and
+       dependency relationships.
+    3. Monitor teammate progress and resolve blockers.
+    4. Synthesize completed work into a final deliverable.
+    You operate in delegate mode — you NEVER write code directly. Instead,
+    you coordinate your teammates who do the implementation work.
+
+  llm:
+    provider: anthropic
+    model: claude-opus-4-20250514
+    temperature: 0.4
+    maxTokens: 8192
+    profile: deep
+
+  team:
+    model: lead-teammate
+    lead: lead
+    delegateMode: true
+
+    members:
+      - name: backend-worker
+        kind: teammate
+        role: >-
+          Implement backend features: API endpoints, database schemas,
+          business logic, and server-side tests. Work in the backend/
+          directory. Claim tasks from the shared list and mark them
+          complete when done.
+        model:
+          provider: anthropic
+          name: claude-sonnet-4-20250514
+        tools:
+          - read_file
+          - write_file
+          - bash
+          - grep
+          - glob
+        contextIsolation: true
+        workingDirectory: /backend
+
+      - name: frontend-worker
+        kind: teammate
+        role: >-
+          Implement frontend features: React components, API integration,
+          styling, and UI tests. Work in the frontend/ directory. Claim
+          tasks from the shared list and mark them complete when done.
+        model:
+          provider: anthropic
+          name: claude-sonnet-4-20250514
+        tools:
+          - read_file
+          - write_file
+          - bash
+          - grep
+          - glob
+        contextIsolation: true
+        workingDirectory: /frontend
+
+      - name: codebase-explorer
+        kind: researcher
+        role: >-
+          Explore the codebase to answer questions from the lead and other
+          teammates. Search for patterns, find dependencies, and analyze
+          architecture. Read-only — never modify files.
+        model:
+          provider: anthropic
+          name: claude-haiku-4-5-20250514
+        tools:
+          - read_file
+          - grep
+          - glob
+        contextIsolation: true
+        workingDirectory: /
+
+    taskList:
+      coordination: self-claim
+      persistence: file-backed
+      stateModel:
+        - pending
+        - in-progress
+        - completed
+        - blocked
+      dependencyTracking: true
+      waveExecution: true
+      lockingStrategy: file-lock
+
+    communication:
+      pattern: mailbox
+      broadcastEnabled: false
+
+    deployment:
+      backend: in-process
+      scaling: fixed
+
+  constraints:
+    cost:
+      maxTokensPerDay: 2000000
+      maxCostPerDay: 100.00
+      currency: USD
+    performance:
+      timeoutSeconds: 300

package/examples/team-lead-teammate.ossa.yaml

@@ -0,0 +1,83 @@
+apiVersion: ossa/v0.4
+kind: Agent
+metadata:
+  name: code-review-team
+  version: 1.0.0
+  description: Claude Code teams pattern - lead delegates to specialized reviewers
+  agentType: claude
+  agentKind: team-lead
+  agentArchitecture:
+    pattern: lead-teammate
+    capabilities:
+      - tools
+      - code
+      - context
+      - handoff
+    coordination:
+      teamModel: lead-teammate
+      communicationPattern: task-list
+      taskCoordination: dependency-wave
+      conflictResolution: leader-decides
+      taskPersistence: file-backed
+      dependencyTracking: true
+spec:
+  role: >
+    You lead a code review team. Analyze pull requests and delegate
+    specific review tasks to specialized teammates.
+  llm:
+    provider: anthropic
+    model: claude-sonnet-4-5-20250514
+  team:
+    model: lead-teammate
+    lead: lead-reviewer
+    delegateMode: task-list
+    members:
+      - name: lead-reviewer
+        kind: team-lead
+        role: >
+          Senior code reviewer. Analyze PRs, break down review into tasks,
+          delegate to specialists, and synthesize final review.
+        model: claude-sonnet-4-5-20250514
+        tools:
+          - read-file
+          - grep
+          - git-diff
+      - name: security-reviewer
+        kind: specialist
+        role: >
+          Security vulnerability scanner. Check for OWASP top 10,
+          injection attacks, authentication flaws, and data exposure.
+        tools:
+          - sast-scan
+          - dependency-check
+          - read-file
+        maxTokenBudget: 15000
+      - name: style-checker
+        kind: teammate
+        role: >
+          Code style and formatting reviewer. Verify adherence to
+          project conventions, naming, and documentation standards.
+        tools:
+          - eslint
+          - prettier
+          - read-file
+      - name: test-reviewer
+        kind: teammate
+        role: >
+          Test coverage reviewer. Verify test adequacy, check edge cases,
+          and validate test assertions.
+        tools:
+          - run-tests
+          - coverage-report
+          - read-file
+    taskList:
+      persistence: file-backed
+      format: markdown
+      path: review-tasks.md
+      dependencyTracking: true
+    communication:
+      channel: task-list
+      consensus: leader-decides
+    deployment:
+      backend: in-process
+      maxConcurrency: 4

package/examples/templates/ossa-compliance.yaml

@@ -1,6 +1,6 @@
 # OSSA v0.1.9 Compliance Configuration for __ARCHIVE_REPORTS
 
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: 'ComplianceConfiguration'
 metadata:
   name: '__ARCHIVE_REPORTS-compliance'

package/examples/unified/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/workflows/batch-email-campaign.yaml

@@ -1,6 +1,6 @@
 # Example: Batch Email Campaign Workflow
 # Demonstrates loops, parallel execution, and batch processing
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Workflow
 metadata:
   name: batch-email-campaign

package/examples/workflows/content-review-publish.yaml

@@ -1,6 +1,6 @@
 # Example: Content Review and Publish Workflow
 # Demonstrates mixed Task + Agent composition
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Workflow
 metadata:
   name: content-review-publish

package/examples/workflows/simple-etl.yaml

@@ -1,6 +1,6 @@
 # Example: Simple ETL Workflow
 # Demonstrates sequential Tasks with data transformation
-apiVersion: ossa/v0.4.1
+apiVersion: ossa/v0.4.5
 kind: Workflow
 metadata:
   name: simple-etl

package/openapi/agents-md-service.yaml

@@ -263,7 +263,7 @@ components:
       properties:
         repo_path:
           type: string
-          example: /Volumes/AgentPlatform/repos/bare/blueflyio/agent-protocol.git
+          example: /path/to/repos/agent-protocol.git
         branch:
           type: string
           example: main

package/openapi/core/unified-agent-gateway.openapi.yaml

@@ -513,7 +513,7 @@ components:
         gitlab_package:
           type: string
           description: GitLab package to use (if available)
-          example: "@llm/my-agent@1.0.0"
+          example: "@llm/supercali-fragilisticagent@1.0.0"
 
     AgentResponse:
       type: object

package/openapi/ossa-cli-enhancements.openapi.yaml

@@ -21,7 +21,7 @@ info:
 servers:
   - url: http://localhost:4000/api/v1
     description: Local development server
-  - url: https://api.blueflyagents.com/api/v1
+  - url: https://mesh.blueflyagents.com/api/v1
     description: Production API server
 
 tags:
@@ -514,8 +514,8 @@ components:
                 type: number
               examples:
                 type: array
-                  items:
-                    type: string
+                items:
+                  type: string
 
     ExampleGenerationRequest:
       type: object

package/openapi/ossa-cli.yaml

@@ -68,7 +68,7 @@ components:
           pattern: '^[a-z0-9-]+$'
           minLength: 3
           maxLength: 50
-          example: 'my-agent'
+          example: 'supercali-fragilisticagent'
         version:
           type: string
           pattern: '^\d+\.\d+\.\d+$'

package/openapi/protocols/sse-streams.yaml

@@ -401,7 +401,7 @@ components:
           type: string
           format: uri
           description: Agent URI of sender
-          example: agent://example.com/my-agent
+          example: agent://example.com/supercali-fragilisticagent
         streamId:
           type: string
           format: uuid

package/openapi/protocols/websocket-events.yaml

@@ -112,7 +112,7 @@ components:
               type: string
               format: uri
               description: Agent URI (agent://domain/agent-id)
-              example: agent://example.com/my-agent
+              example: agent://example.com/supercali-fragilisticagent
             capabilities:
               type: array
               items:
@@ -353,7 +353,7 @@ components:
           type: string
           format: uri
           description: Agent URI of sender
-          example: agent://example.com/my-agent
+          example: agent://example.com/supercali-fragilisticagent
         correlationId:
           type: string
           format: uuid

package/openapi/release-automation.openapi.yaml

@@ -17,7 +17,7 @@ info:
 servers:
   - url: http://localhost:4000/api/v1
     description: Local development server
-  - url: https://api.blueflyagents.com/api/v1
+  - url: https://mesh.blueflyagents.com/api/v1
     description: Production API server
 
 tags: