Files
aitbc/docs/architecture
aitbc 573aae065b
Some checks failed
API Endpoint Tests / test-api-endpoints (push) Successful in 56s
Blockchain Synchronization Verification / sync-verification (push) Failing after 3s
CLI Tests / test-cli (push) Failing after 5s
Coverage Phase 1 (70% Target) / test-coverage-70 (push) Failing after 19s
Coverage Phase 2 (85% Target) / test-coverage-85 (push) Failing after 18s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Successful in 3s
Cross-Chain Functionality Tests / test-cross-chain-transactions (push) Successful in 4s
Cross-Chain Functionality Tests / test-multi-chain-consensus (push) Successful in 5s
Deploy to Testnet / deploy-testnet (push) Failing after 21s
Documentation Validation / validate-docs (push) Failing after 13s
Documentation Validation / validate-policies-strict (push) Successful in 4s
Integration Tests / test-service-integration (push) Failing after 2s
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Successful in 4s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 14s
Node Failover Simulation / failover-test (push) Successful in 9s
P2P Network Verification / p2p-verification (push) Successful in 5s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 51s
Package Tests / Python package - aitbc-core (push) Failing after 3s
Package Tests / Python package - aitbc-crypto (push) Successful in 22s
Package Tests / Python package - aitbc-sdk (push) Successful in 16s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 21s
Package Tests / JavaScript package - aitbc-token (push) Failing after 18s
Production Tests / Production Integration Tests (push) Failing after 1m9s
Python Tests / test-python (push) Failing after 3s
Security Scanning / security-scan (push) Failing after 41s
Smart Contract Tests / test-solidity (map[name:aitbc-contracts path:contracts]) (push) Failing after 6s
Smart Contract Tests / test-solidity (map[name:aitbc-token path:packages/solidity/aitbc-token]) (push) Failing after 7s
Smart Contract Tests / test-foundry (push) Failing after 20s
Smart Contract Tests / lint-solidity (push) Failing after 4s
Smart Contract Tests / deploy-contracts (push) Failing after 5s
Cross-Chain Functionality Tests / aggregate-results (push) Successful in 2s
Multi-Node Stress Testing / stress-test (push) Successful in 2s
Cross-Node Transaction Testing / transaction-test (push) Successful in 3s
feat: complete codebase remediation with all phases
Phase 1: Security fixes
- Added CORSMiddleware to marketplace-service with specific origins
- Fixed blockchain-node auth to fail closed on JWT errors
- Added security regression tests (test_cors_configuration.py, test_dispute_auth.py)

Phase 2: Repository cleanup
- Removed 51 fix/backup/legacy files
- Deleted marketplace-service-debug directory

Phase 3.1: Python version constraints
- Updated aitbc-crypto and aitbc-sdk with requires-python >=3.13
- Added explicit [tool.poetry].packages declarations

Phase 3.2: Agent service DI architecture
- Created aitbc-agent-core package with protocols and shared service
- Implemented adapters for agent-management and coordinator-api
- Created factory functions for gradual migration
- Added migration comments to existing integration files

Phase 4.1: Auth/utils extraction
- Created auth.py module with JWT validation and security utilities
- Created utils.py module with common helpers

Phase 4.2: Router decomposition
- Decomposed router.py into 10 domain modules (58 endpoints)
- Created route table snapshot for verification
- Preserved router_old.py as reference

Phase 5: App shell classification
- Documented app shell patterns across services

Phase 6: Quality gates
- Verified mypy type checking (75% error reduction)
- Analyzed logging inconsistencies with structlog migration plan
- Removed unused orjson dependency

Documentation:
- Created comprehensive remediation report
- Added architecture documentation for DI pattern
- Added quality analysis documents
2026-05-24 20:21:23 +02:00
..

AITBC Architecture Documentation

This directory contains comprehensive architecture documentation for the AITBC platform, covering system components, data flows, and technical implementation details.

📚 Document Structure

Core Architecture Documents

  1. 1_system-flow.md - System flow diagrams and data flow architecture
  2. 2_components-overview.md - High-level component overview and interactions
  3. 3_coordinator-api.md - Coordinator API architecture and endpoints
  4. 4_blockchain-node.md - Blockchain node architecture and consensus
  5. 5_marketplace-web.md - Marketplace web application architecture
  6. 6_trade-exchange.md - Trade exchange and matching engine
  7. 7_wallet.md - Wallet architecture and key management
  8. 8_codebase-structure.md - Codebase organization and module structure
  9. 9_full-technical-reference.md - Complete technical reference

Specialized Architecture

🎯 Quick Start

For New Developers

Start with these documents in order:

  1. 2_components-overview.md - Understand the big picture
  2. 1_system-flow.md - Learn how data flows through the system
  3. 8_codebase-structure.md - Navigate the codebase

For System Architects

Focus on these documents:

  1. 3_coordinator-api.md - API architecture
  2. 4_blockchain-node.md - Blockchain architecture
  3. 9_full-technical-reference.md - Complete technical details

For Infrastructure Engineers

Review these documents:

  1. edge_gpu_setup.md - Edge computing setup
  2. 6_trade-exchange.md - Exchange infrastructure
  3. 7_wallet.md - Wallet infrastructure

📊 Architecture Overview

System Components

┌─────────────────┐    ┌─────────────────┐    ┌─────────────────┐
│  Coordinator    │    │  Blockchain     │    │  Marketplace    │
│  API (8011)     │◄──►│  Node (8006)    │◄──►│  Web (8001)     │
└─────────────────┘    └─────────────────┘    └─────────────────┘
        │                      │                      │
        └──────────────────────┴──────────────────────┘
                               │
                    ┌───────────┴───────────┐
                    │                       │
              ┌─────┴─────┐         ┌─────┴─────┐
              │  Wallet   │         │  Exchange │
              │  Service  │         │  Service  │
              └───────────┘         └───────────┘

Key Technologies

  • Blockchain: Custom AITBC blockchain with Proof-of-Stake consensus
  • API: FastAPI-based coordinator API
  • Frontend: React-based marketplace web application
  • Wallet: Python-based wallet service with cryptography
  • Exchange: Matching engine for token trading
  • Edge Computing: GPU resource management for AI workloads

🚀 Development Workflow

Adding New Architecture Documents

  1. Create new markdown file in this directory
  2. Follow naming convention: number_title.md
  3. Update this README to include the new document
  4. Add cross-references to related documents
  5. Commit and push changes

Updating Architecture Documents

  1. Make changes to the relevant document
  2. Update cross-references if needed
  3. Update version number and date
  4. Commit with descriptive message
  5. Sync changes across all nodes

📝 Documentation Standards

  • Format: Markdown with proper heading hierarchy
  • Diagrams: Use ASCII art or mermaid for diagrams
  • Code Examples: Include working code snippets
  • Cross-References: Link to related documents
  • Version Control: Track document versions and dates
  • Language: English, clear and concise

🔍 Search and Navigation

Finding Specific Information

  • Use the MASTER_INDEX for comprehensive navigation
  • Search within this directory for specific topics
  • Follow cross-references between documents
  • Check the table of contents in each document

Document Categories

  • System Architecture: Overall system design and components
  • Component Architecture: Individual component details
  • Infrastructure: Deployment and infrastructure setup
  • Integration: Component integration and communication
  • Reference: Complete technical reference material

📞 Support and Contributions

Getting Help

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your documentation changes
  4. Test links and cross-references
  5. Submit a pull request

Last Updated: 2026-05-08
Version: 1.0
Status: Active documentation