Files
aitbc/apps/governance-service
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 Governance Service

Manages governance operations.

Installation

cd /opt/aitbc
poetry install --with governance-service

Database Setup

Create a separate database for the governance service:

sudo -u postgres psql -f apps/governance-service/scripts/setup-database.sql

Or manually:

CREATE DATABASE aitbc_governance;
CREATE USER aitbc_governance WITH PASSWORD 'password';
GRANT ALL PRIVILEGES ON DATABASE aitbc_governance TO aitbc_governance;

Running

# Development
python -m governance_service.main

# Production (systemd)
sudo systemctl start governance-service
sudo systemctl enable governance-service

Endpoints

  • GET /health - Health check
  • GET /governance/status - Get governance status
  • GET /v1/governance/profiles - Get governance profiles
  • GET /v1/governance/profiles/{profile_id} - Get specific profile
  • POST /v1/governance/profiles - Create new profile
  • GET /v1/governance/proposals - Get proposals
  • GET /v1/governance/proposals/{proposal_id} - Get specific proposal
  • POST /v1/governance/proposals - Create new proposal
  • GET /v1/governance/votes - Get votes
  • POST /v1/governance/votes - Create new vote
  • GET /v1/governance/treasury - Get DAO treasury
  • GET /v1/governance/analytics - Get governance analytics

Testing

Prerequisites

  • PostgreSQL running and aitbc_governance database created
  • Poetry dependencies installed

Database Setup

sudo -u postgres psql -f scripts/setup-database.sql

Start Service (Development)

python -m governance_service.main

Health Check

curl http://localhost:8105/health

Expected response:

{"status": "healthy", "service": "governance-service"}

Governance Status

curl http://localhost:8105/governance/status

Expected response:

{
  "status": "operational",
  "service": "governance-service",
  "message": "Governance service is running"
}

Get Governance Proposals

curl http://localhost:8105/v1/governance/proposals

Expected response:

[]

Create Governance Proposal

curl -X POST http://localhost:8105/v1/governance/proposals \
  -H "Content-Type: application/json" \
  -d '{
    "proposer_id": "test_proposer",
    "title": "Test Proposal",
    "description": "Test description",
    "category": "general",
    "voting_starts": "2026-05-01T00:00:00Z",
    "voting_ends": "2026-05-08T00:00:00Z"
  }'

Test Through Gateway

  1. Start the API gateway:

    python -m api_gateway.main
    
  2. Test governance endpoints through the gateway:

    curl http://localhost:8080/governance/health
    curl http://localhost:8080/governance/v1/governance/proposals
    

For comprehensive testing procedures, see MICROSERVICES_TESTING_GUIDE.md.

Service Configuration

  • Port: 8105
  • Database: aitbc_governance
  • Gateway route: /governance/*

Migration Status

Completed:

  • Extracted governance domain models (GovernanceProfile, Proposal, Vote, DaoTreasury, TransparencyReport)
  • Extracted governance services (GovernanceService with CRUD operations)
  • Set up database session management
  • Extracted governance router endpoints
  • Created systemd service configuration
  • Created database setup script

Remaining:

  • Remove governance routers from coordinator-api
  • Remove governance services from coordinator-api
  • Remove governance domain models from coordinator-api
  • Run database migration script to create aitbc_governance database
  • Install and enable systemd service
  • End-to-end testing with gateway

Note: The governance service is ~50K lines, so full removal from coordinator-api requires careful coordination to avoid breaking existing functionality. The foundation is in place for gradual migration.