diff --git a/bottemplates/content-moderation.gbai/content-moderation.bas b/bottemplates/content-moderation.gbai/content-moderation.bas deleted file mode 100644 index 0ab85ae36..000000000 --- a/bottemplates/content-moderation.gbai/content-moderation.bas +++ /dev/null @@ -1,37 +0,0 @@ -' Content Moderation Workflow with AI -USE KB "community-guidelines" -USE TOOL "image-analysis" -USE TOOL "text-sentiment" - -ORCHESTRATE WORKFLOW "content-moderation" - -STEP 1: BOT "content-analyzer" "scan content" - ' Multi-modal content analysis - -STEP 2: BOT "policy-checker" "verify guidelines" - ' Check against community standards - -IF toxicity_score > 0.7 OR contains_explicit_content = true THEN - STEP 3: BOT "auto-moderator" "remove content" - PUBLISH EVENT "content_removed" -ELSE IF toxicity_score > 0.4 THEN - STEP 4: HUMAN APPROVAL FROM "moderator@platform.com" - TIMEOUT 3600 ' 1 hour for borderline content - ON TIMEOUT: APPROVE WITH WARNING -END IF - -' Enhanced LLM for context understanding -result = LLM "Analyze content context and cultural sensitivity" - WITH OPTIMIZE FOR "quality" - WITH MAX_COST 0.05 - -IF result.contains("cultural_sensitivity_issue") THEN - STEP 5: BOT "cultural-advisor" "review context" -END IF - -' Learn from moderation decisions -BOT SHARE MEMORY "moderation_patterns" WITH "content-analyzer-v2" - -PUBLISH EVENT "moderation_complete" - -TALK "Content moderation completed" diff --git a/bottemplates/customer-support-workflow.gbai/customer-support-workflow.bas b/bottemplates/customer-support-workflow.gbai/customer-support-workflow.bas deleted file mode 100644 index 39b1ef6b9..000000000 --- a/bottemplates/customer-support-workflow.gbai/customer-support-workflow.bas +++ /dev/null @@ -1,54 +0,0 @@ -' Example: Customer Support Workflow with Enhanced Orchestration -' This demonstrates the new ORCHESTRATE WORKFLOW, event system, and bot memory sharing - -USE KB "support-policies" -USE TOOL "check-order" -USE TOOL "process-refund" - -' Set up event handlers -ON EVENT "approval_received" DO - TALK "Manager approval received, processing refund..." -END ON - -ON EVENT "timeout_occurred" DO - TALK "Approval timeout, escalating to director..." -END ON - -' Main workflow orchestration -ORCHESTRATE WORKFLOW "customer-complaint-resolution" - -STEP 1: BOT "classifier" "analyze complaint" - ' Classifier bot analyzes the complaint and sets variables - -STEP 2: BOT "order-checker" "validate order details" - ' Order checker validates the order and warranty status - -' Conditional logic based on order value -IF order_amount > 100 THEN - STEP 3: HUMAN APPROVAL FROM "manager@company.com" - TIMEOUT 1800 ' 30 minutes - ON TIMEOUT: ESCALATE TO "director@company.com" - - ' Wait for approval event - WAIT FOR EVENT "approval_received" TIMEOUT 3600 -END IF - -STEP 4: PARALLEL - BRANCH A: BOT "refund-processor" "process refund" - BRANCH B: BOT "inventory-updater" "update stock levels" -END PARALLEL - -STEP 5: BOT "follow-up" "schedule customer check-in" - DELAY 86400 ' 24 hours later - -' Share successful resolution patterns with other support bots -BOT SHARE MEMORY "successful_resolution_method" WITH "support-bot-2" -BOT SHARE MEMORY "customer_satisfaction_score" WITH "support-bot-3" - -' Sync knowledge from master support bot -BOT SYNC MEMORY FROM "master-support-bot" - -' Publish completion event for analytics -PUBLISH EVENT "workflow_completed" - -TALK "Customer complaint resolved successfully!" diff --git a/bottemplates/customer-support-workflow.gbai/package.json b/bottemplates/customer-support-workflow.gbai/package.json deleted file mode 100644 index e64442191..000000000 --- a/bottemplates/customer-support-workflow.gbai/package.json +++ /dev/null @@ -1,21 +0,0 @@ -{ - "name": "Customer Support Workflow", - "description": "Advanced customer support workflow with multi-agent orchestration, event handling, and bot memory sharing", - "version": "1.0.0", - "author": "General Bots", - "category": "customer-support", - "keywords": ["workflow", "orchestration", "customer-support", "multi-agent"], - "features": [ - "Multi-step workflow orchestration", - "Human approval integration", - "Event-driven coordination", - "Cross-bot memory sharing", - "Parallel processing", - "Automatic escalation" - ], - "requirements": { - "tools": ["check-order", "process-refund"], - "knowledge_bases": ["support-policies"], - "bots": ["classifier", "order-checker", "refund-processor", "inventory-updater", "follow-up"] - } -} diff --git a/bottemplates/marketing-campaign.gbai/marketing-campaign.bas b/bottemplates/marketing-campaign.gbai/marketing-campaign.bas deleted file mode 100644 index 251d22f9d..000000000 --- a/bottemplates/marketing-campaign.gbai/marketing-campaign.bas +++ /dev/null @@ -1,45 +0,0 @@ -' Marketing Campaign Automation -USE KB "brand-guidelines" -USE TOOL "social-media-post" -USE TOOL "email-sender" -USE TOOL "analytics-tracker" - -ORCHESTRATE WORKFLOW "marketing-campaign" - -STEP 1: BOT "audience-segmenter" "analyze target demographics" - ' AI-powered audience analysis - -STEP 2: BOT "content-creator" "generate campaign materials" - ' Multi-modal content generation - -' Smart LLM routing for different content types -email_content = LLM "Create engaging email subject line" - WITH OPTIMIZE FOR "cost" - -social_content = LLM "Create viral social media post" - WITH OPTIMIZE FOR "quality" - WITH MAX_LATENCY 5000 - -STEP 3: PARALLEL - BRANCH A: BOT "email-scheduler" "send email campaign" - BRANCH B: BOT "social-scheduler" "post to social media" - BRANCH C: BOT "ad-manager" "launch paid ads" -END PARALLEL - -' Wait for initial results -WAIT FOR EVENT "campaign_metrics_ready" TIMEOUT 7200 - -STEP 4: BOT "performance-analyzer" "analyze results" - -IF engagement_rate < 0.02 THEN - STEP 5: BOT "optimizer" "adjust campaign parameters" - PUBLISH EVENT "campaign_optimized" -END IF - -' Share successful campaign patterns -BOT SHARE MEMORY "high_engagement_content" WITH "content-creator-v2" -BOT SHARE MEMORY "optimal_timing" WITH "scheduler-bots" - -PUBLISH EVENT "campaign_complete" - -TALK "Marketing campaign launched and optimized!" diff --git a/bottemplates/order-processing.gbai/order-processing.bas b/bottemplates/order-processing.gbai/order-processing.bas deleted file mode 100644 index 208adafc9..000000000 --- a/bottemplates/order-processing.gbai/order-processing.bas +++ /dev/null @@ -1,40 +0,0 @@ -' E-commerce Order Processing Workflow -USE KB "order-policies" -USE TOOL "validate-payment" -USE TOOL "reserve-inventory" -USE TOOL "send-confirmation" - -ORCHESTRATE WORKFLOW "order-processing" - -STEP 1: BOT "fraud-detector" "analyze transaction" - ' AI-powered fraud detection - -STEP 2: BOT "inventory-checker" "verify availability" - ' Check stock levels and reserve items - -IF fraud_score > 0.8 THEN - STEP 3: HUMAN APPROVAL FROM "security@store.com" - TIMEOUT 900 ' 15 minutes for high-risk orders - ON TIMEOUT: REJECT ORDER -END IF - -IF payment_method = "credit_card" THEN - STEP 4: BOT "payment-processor" "charge card" -ELSE - STEP 4: BOT "payment-processor" "process alternative" -END IF - -STEP 5: PARALLEL - BRANCH A: BOT "shipping-optimizer" "select carrier" - BRANCH B: BOT "inventory-updater" "update stock" - BRANCH C: BOT "notification-sender" "send confirmation" -END PARALLEL - -' Share successful processing patterns -BOT SHARE MEMORY "fraud_indicators" WITH "fraud-detector-backup" -BOT SHARE MEMORY "shipping_preferences" WITH "logistics-bot" - -' Publish completion event -PUBLISH EVENT "order_processed" - -TALK "Order processed successfully!" diff --git a/examples/customer-support-workflow.bas b/examples/customer-support-workflow.bas deleted file mode 100644 index fbec217e1..000000000 --- a/examples/customer-support-workflow.bas +++ /dev/null @@ -1,21 +0,0 @@ -' Example Workflow: Customer Support Process -USE KB "support-policies" -USE TOOL "check-order" -USE TOOL "process-refund" - -ORCHESTRATE WORKFLOW "customer-support" - STEP 1: BOT "classifier" "analyze complaint" - STEP 2: BOT "order-checker" "validate order" - - IF order_amount > 100 THEN - STEP 3: HUMAN APPROVAL FROM "manager@company.com" - TIMEOUT 1800 - END IF - - STEP 4: BOT "refund-processor" "process refund" - - BOT SHARE MEMORY "resolution_method" WITH "support-team" - PUBLISH EVENT "case_resolved" -END WORKFLOW - -TALK "Support case processed successfully!" diff --git a/examples/order-checker-tool.bas b/examples/order-checker-tool.bas deleted file mode 100644 index 155c5666f..000000000 --- a/examples/order-checker-tool.bas +++ /dev/null @@ -1,12 +0,0 @@ -' Example Tool: Simple Order Checker -USE TOOL "database" - -WHEN called WITH order_id DO - order = GET order FROM database WHERE id = order_id - - IF order.exists THEN - RETURN order.status, order.amount, order.date - ELSE - RETURN "not_found", 0, "" - END IF -END WHEN diff --git a/examples/simple-chatbot.bas b/examples/simple-chatbot.bas deleted file mode 100644 index 758afa2b5..000000000 --- a/examples/simple-chatbot.bas +++ /dev/null @@ -1,18 +0,0 @@ -' Example Regular Bot: Simple Chatbot -USE KB "faq" - -TALK "Hello! How can I help you today?" - -WHEN user_says "help" DO - TALK "I can help you with orders, returns, and general questions." -END WHEN - -WHEN user_says "order status" DO - order_id = ASK "What's your order number?" - status = CALL TOOL "check-order" WITH order_id - TALK "Your order status is: " + status -END WHEN - -WHEN user_says "goodbye" DO - TALK "Thank you for contacting us! Have a great day!" -END WHEN