Files
aitbc/.windsurf/skills/aitbc-ai-operator.md
aitbc f36fd45d28
Some checks failed
Blockchain Synchronization Verification / sync-verification (push) Successful in 4s
Documentation Validation / validate-docs (push) Successful in 12s
Documentation Validation / validate-policies-strict (push) Successful in 3s
Integration Tests / test-service-integration (push) Failing after 12s
Multi-Node Blockchain Health Monitoring / health-check (push) Successful in 3s
P2P Network Verification / p2p-verification (push) Successful in 2s
Python Tests / test-python (push) Successful in 10s
Security Scanning / security-scan (push) Successful in 31s
Implement RECEIPT_CLAIM transaction type
- Add status fields to Receipt model (status, claimed_at, claimed_by)
- Add RECEIPT_CLAIM handling to state_transition.py with validation and reward minting
- Add type field to Transaction model for reliable transaction type storage
- Update router to use TransactionRequest model to preserve type field
- Update poa.py to extract type from mempool transaction content and store only original payload
- Add RECEIPT_CLAIM to GasType enum with gas schedule
2026-04-22 13:35:31 +02:00

5.4 KiB

description, title, version
description title version
Atomic AITBC AI job operations with deterministic monitoring and optimization aitbc-ai-operator 1.1

AITBC AI Operator

Purpose

Submit, monitor, and optimize AITBC AI jobs with deterministic performance tracking and resource management.

Activation

Trigger when user requests AI operations: job submission, status monitoring, results retrieval, or resource optimization.

Input

{
  "operation": "submit|status|results|list|optimize|cancel",
  "wallet": "string (for submit/optimize)",
  "job_type": "inference|training|multimodal|ollama|streaming|monitoring",
  "prompt": "string (for submit)",
  "payment": "number (for submit)",
  "job_id": "string (for status/results/cancel)",
  "agent_id": "string (for optimize)",
  "cpu": "number (for optimize)",
  "memory": "number (for optimize)",
  "gpu": "number (for optimize)",
  "duration": "number (for optimize)",
  "limit": "number (optional for list)",
  "model": "string (optional for ollama jobs, e.g., llama2, mistral)",
  "provider_id": "string (optional for GPU provider selection)",
  "endpoint": "string (optional for custom Ollama endpoint)",
  "batch_file": "string (optional for batch operations)",
  "parallel": "number (optional for parallel job count)"
}

Output

{
  "summary": "AI operation completed successfully",
  "operation": "submit|status|results|list|optimize|cancel",
  "job_id": "string (for submit/status/results/cancel)",
  "job_type": "string",
  "status": "submitted|processing|completed|failed|cancelled",
  "progress": "number (0-100)",
  "estimated_time": "number (seconds)",
  "wallet": "string (for submit/optimize)",
  "payment": "number (for submit)",
  "result": "string (for results)",
  "jobs": "array (for list)",
  "resource_allocation": "object (for optimize)",
  "performance_metrics": "object",
  "issues": [],
  "recommendations": [],
  "confidence": 1.0,
  "execution_time": "number",
  "validation_status": "success|partial|failed"
}

Process

1. Analyze

  • Validate AI job parameters
  • Check wallet balance for payment
  • Verify job type compatibility
  • Assess resource requirements

2. Plan

  • Calculate appropriate payment amount
  • Prepare job submission parameters
  • Set monitoring strategy for job tracking
  • Define optimization criteria (if applicable)

3. Execute

  • Execute AITBC CLI AI command
  • Capture job ID and initial status
  • Monitor job progress and completion
  • Retrieve results upon completion
  • Parse performance metrics

4. Validate

  • Verify job submission success
  • Check job status progression
  • Validate result completeness
  • Confirm resource allocation accuracy

Constraints

  • MUST NOT submit jobs without sufficient wallet balance
  • MUST NOT exceed resource allocation limits
  • MUST validate job type compatibility
  • MUST monitor jobs until completion or timeout (300 seconds)
  • MUST set minimum payment based on job type
  • MUST validate prompt length (max 4000 characters)

Environment Assumptions

  • AITBC CLI accessible at /opt/aitbc/aitbc-cli
  • AI services operational (Ollama, exchange, coordinator)
  • Ollama endpoint accessible at http://localhost:11434 or custom endpoint
  • GPU provider marketplace operational for resource allocation
  • Sufficient wallet balance for job payments
  • Resource allocation system operational
  • Job queue processing functional
  • Ollama models available: llama2, mistral, codellama, etc.
  • GPU providers registered with unique p2p_node_id for P2P connectivity

Error Handling

  • Insufficient balance → Return error with required amount
  • Invalid job type → Return job type validation error
  • Service unavailable → Return service status and retry recommendations
  • Job timeout → Return timeout status with troubleshooting steps

Example Usage Prompt

Submit an AI job for customer feedback analysis using multimodal processing with payment 500 AIT from trading-wallet

Expected Output Example

{
  "summary": "Multimodal AI job submitted successfully for customer feedback analysis",
  "operation": "submit",
  "job_id": "ai_job_1774883000",
  "job_type": "multimodal",
  "status": "submitted",
  "progress": 0,
  "estimated_time": 45,
  "wallet": "trading-wallet",
  "payment": 500,
  "result": null,
  "jobs": null,
  "resource_allocation": null,
  "performance_metrics": null,
  "issues": [],
  "recommendations": ["Monitor job progress for completion", "Prepare to analyze multimodal results"],
  "confidence": 1.0,
  "execution_time": 3.1,
  "validation_status": "success"
}

Model Routing Suggestion

Fast Model (Claude Haiku, GPT-3.5-turbo)

  • Job status checking
  • Job listing
  • Result retrieval for completed jobs

Reasoning Model (Claude Sonnet, GPT-4)

  • Job submission with optimization
  • Resource allocation optimization
  • Complex AI job analysis
  • Error diagnosis and recovery

Coding Model (Claude Sonnet, GPT-4)

  • AI job parameter optimization
  • Performance tuning recommendations
  • Resource allocation algorithms

Performance Notes

  • Execution Time: 2-5 seconds for submit/list, 10-60 seconds for monitoring, 30-300 seconds for job completion
  • Memory Usage: <200MB for AI operations
  • Network Requirements: AI service connectivity (Ollama, exchange, coordinator)
  • Concurrency: Safe for multiple simultaneous jobs from different wallets
  • Resource Monitoring: Real-time job progress tracking and performance metrics