Files
aitbc/docs/project/1_files.md
aitbc 19d415a235
Some checks failed
Blockchain Synchronization Verification / sync-verification (push) Failing after 3s
CLI Tests / test-cli (push) Failing after 3s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Successful in 2s
Cross-Chain Functionality Tests / test-cross-chain-transactions (push) Successful in 3s
Cross-Chain Functionality Tests / test-cross-chain-bridge (push) Has been skipped
Cross-Chain Functionality Tests / test-multi-chain-consensus (push) Successful in 2s
Cross-Chain Functionality Tests / aggregate-results (push) Has been skipped
Deploy to Testnet / deploy-testnet (push) Successful in 1m12s
Documentation Validation / validate-docs (push) Failing after 8s
Documentation Validation / validate-policies-strict (push) Successful in 3s
Integration Tests / test-service-integration (push) Successful in 2m6s
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Successful in 2s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 4s
P2P Network Verification / p2p-verification (push) Successful in 4s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 32s
Package Tests / Python package - aitbc-core (push) Successful in 14s
Package Tests / Python package - aitbc-crypto (push) Successful in 12s
Package Tests / Python package - aitbc-sdk (push) Successful in 9s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 8s
Package Tests / JavaScript package - aitbc-token (push) Successful in 17s
Python Tests / test-python (push) Successful in 15s
Security Scanning / security-scan (push) Successful in 27s
Node Failover Simulation / failover-test (push) Successful in 7s
Multi-Node Stress Testing / stress-test (push) Successful in 6s
Cross-Node Transaction Testing / transaction-test (push) Successful in 4s
feat: add SQLCipher database encryption support and consolidate agent documentation
- Add SQLCipher encryption for ait-mainnet database with configurable flag
- Add db_encryption_enabled and db_encryption_key_path config settings
- Implement encryption key loading and PRAGMA key setup via connection events
- Add shutdown_db function for proper database cleanup
- Export middleware classes in aitbc/__init__.py
- Fix import path in sync.py for settings
- Remove duplicate agent documentation from docs
2026-05-03 12:00:38 +02:00

2.0 KiB

AITBC Repository File Structure

This document describes the current organization and status of files and folders in the repository. A current snapshot appears first, followed by a short list of related docs.

Last updated: 2026-04-27

Current Snapshot

This is the authoritative layout of the repository root at /opt/aitbc.

/opt/aitbc/
├── apps/
├── cli/
├── contracts/
├── dev/
├── docs/
├── examples/
├── extensions/
├── infra/
├── packages/
├── plugins/
├── scripts/
├── systemd/
├── tests/
├── website/
├── build/            # generated output
├── venv/             # local virtualenv
└── agent_registry.db # runtime database

Main directories at a glance

  • apps/ — application and service packages
  • cli/ — CLI entrypoints and command modules
  • contracts/ — Solidity contracts and deployment tooling
  • dev/ — developer utilities and local helpers
  • docs/ — documentation tree, including guides/, project/, infrastructure/, reference/, and workflows/
  • packages/py/ — shared Python libraries (aitbc-agent-sdk, aitbc-core, aitbc-crypto, aitbc-sdk)
  • plugins/ — plugin integrations such as Ollama
  • scripts/ — CI, deployment, development, monitoring, service, testing, utility, and wrapper scripts
  • systemd/ — standardized service units
  • tests/ — repository-wide test suites and fixtures
  • website/ — public site, dashboards, docs portal, and wallet assets

Notes

  • Repo root: /opt/aitbc
  • Legacy home paths: historical only
  • Deployment docs: see docs/project/3_infrastructure.md and docs/project/5_done.md

See Also

  • docs/project/3_infrastructure.md
  • docs/project/5_done.md
  • docs/guides/getting-started/

This page intentionally stays short. For detailed historical context, use the infrastructure and completed-deployments docs above.