Some checks failed
API Endpoint Tests / test-api-endpoints (push) Successful in 46s
CLI Tests / test-cli (push) Failing after 2s
Documentation Validation / validate-docs (push) Failing after 9s
Documentation Validation / validate-policies-strict (push) Failing after 12s
Package Tests / Python package - aitbc-agent-sdk (push) Successful in 24s
Package Tests / Python package - aitbc-core (push) Successful in 19s
Package Tests / Python package - aitbc-crypto (push) Successful in 10s
Package Tests / Python package - aitbc-sdk (push) Successful in 16s
Package Tests / JavaScript package - aitbc-sdk-js (push) Successful in 5s
Package Tests / JavaScript package - aitbc-token (push) Successful in 10s
Production Tests / Production Integration Tests (push) Successful in 17s
Python Tests / test-python (push) Successful in 8s
Security Scanning / security-scan (push) Successful in 46s
Multi-Node Blockchain Health Monitoring / health-check (push) Failing after 3s
Integration Tests / test-service-integration (push) Failing after 11m28s
Add all documentation subdirectories to the curated markdown linting targets, replacing the previous exclusion-based approach with comprehensive coverage. Update validation to check for required README files across all hubs and verify priority documentation metadata markers. Implement lazy loading for optional dependencies (numpy, redis, bcrypt, jwt, websockets) in agent-coordinator and related modules to improve startup
Policy Documentation
Level: All Levels
Prerequisites: Familiarity with AITBC contribution and security expectations
Estimated Time: 10-20 minutes
Last Updated: 2026-04-27
Version: 1.0
🧭 Navigation Path:
🏠 Documentation Home → 📋 Policies → You are here
breadcrumb: Home → Policies → Overview
🎯 See Also:
- 🏛️ Governance Documentation - Coordination and ownership context
- 🔒 Security Documentation - Security-specific guidance
- 📚 About Documentation - Documentation standards and audit notes
- 🏠 Documentation Home - Main docs entry point
📦 Contents
- BRANCH_PROTECTION.md - Branch protection policy
- CLI_TRANSLATION_SECURITY_POLICY.md - CLI translation security policy
- DOTENV_DISCIPLINE.md - Environment file handling discipline
🧱 Purpose
This directory defines normative policy guidance for:
- branch and repository protection
- secure CLI and translation behavior
.envand environment-handling discipline
🚀 Next Steps
- Review
BRANCH_PROTECTION.mdbefore changing repository safeguards. - Use
DOTENV_DISCIPLINE.mdfor environment-related changes. - Keep policy docs aligned with the audit checklist in
../about/DOCUMENTATION_COMPLIANCE_AUDIT.md.
Last updated: 2026-04-27
Version: 1.0
Status: Policy index