4a707c2e15
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Successful in 4s
Deploy to Testnet / deploy-testnet (push) Successful in 1m45s
Documentation Validation / validate-docs (push) Failing after 13s
Documentation Validation / validate-policies-strict (push) Successful in 5s
Integration Tests / test-service-integration (push) Failing after 5s
Multi-Node Stress Testing / stress-test (push) Successful in 2s
Python Tests / test-python (push) Failing after 32s
Security Scanning / security-scan (push) Failing after 31s
Build Debian Miner Binary / build-miner (push) Failing after 5m50s
- Renamed ai-service to aitbc-ai-service - Renamed edge-api to aitbc-edge-api - Updated pyproject.toml files with new package names - Renamed directories and package modules - Updated references in documentation and scripts - All internal packages now follow aitbc- naming convention
1.7 KiB
1.7 KiB
Stub Services
This directory contains stub and placeholder services that are not yet fully implemented or are minimal implementations.
Services in this Directory
The following services have <10 files and are considered stubs or placeholders:
- hermes-service (4 files) - Hermes agent communication service
- monitor (7 files) - Monitoring stub
- monitoring-service (4 files) - Monitoring service stub
- plugin-service (4 files) - Plugin service stub
- aitbc-ai-service (8 files) - AI service stub
- compliance-service (9 files) - Compliance checking stub
- exchange-integration (9 files) - Exchange integration stub
- global-ai-agents (9 files) - Global AI agents stub
- global-infrastructure (9 files) - Global infrastructure stub
- multi-region-load-balancer (9 files) - Multi-region load balancer stub
- plugin-analytics (9 files) - Plugin analytics stub
- plugin-marketplace (9 files) - Plugin marketplace stub
- plugin-registry (9 files) - Plugin registry stub
- plugin-security (9 files) - Plugin security stub
- simple-explorer (9 files) - Simple blockchain explorer stub
- trading-engine (9 files) - Trading engine stub
Purpose
These services are placeholders for future functionality. They may be:
- Minimal implementations for testing
- Skeletons for future development
- Experimental features not yet production-ready
Active Services
Active services with full implementations remain in the parent apps/ directory:
- blockchain-node, coordinator-api, exchange, marketplace, wallet, etc.
Future Work
As stub services are fully implemented, they should be moved from this directory to the main apps/ directory.