Some checks failed
Documentation Validation / validate-docs (push) Failing after 9s
Documentation Validation / validate-policies-strict (push) Failing after 3s
Integration Tests / test-service-integration (push) Successful in 1m59s
Python Tests / test-python (push) Successful in 23s
Security Scanning / security-scan (push) Successful in 1m48s
P2P Network Verification / p2p-verification (push) Successful in 3s
Blockchain Synchronization Verification / sync-verification (push) Failing after 9s
Multi-Node Blockchain Health Monitoring / health-check (push) Successful in 2s
Remove obsolete aitbc-gpu.service references across documentation, scripts, and deployment files. GPU functionality is now unified into aitbc-marketplace.service (port 8007). Update blockchain health check to use gitea-runner hostname for aitbc2. Clarify WAL mode comment in database.py to reference btrfs raid instead of generic disk I/O errors. Mark cross-link validation checks as complete in compliance audit.
5.3 KiB
5.3 KiB
Documentation Compliance Audit
Level: All Levels
Prerequisites: Familiarity with the AITBC docs tree and template standard
Estimated Time: 15-20 minutes
Last Updated: 2026-04-27
Version: 1.0
🧭 Navigation Path:
🏠 Documentation Home → 📖 About → ✅ Compliance Audit → You are here
breadcrumb: Home → About → Compliance Audit
🎯 See Also:
- 📋 Template Standard - Required metadata and structure
- 🎯 10/10 Roadmap - Quality goals and remediation themes
- 📊 Organization Analysis - Historical structure review
- 🏠 Documentation Home - Main docs entry point
- 🧭 Master Index - Full documentation catalog
🎯 Audit Scope
This checklist tracks the current remediation target:
- missing top-level index pages
- standardized metadata on priority documents
- breadcrumbs and cross-links on high-traffic pages
- historical exceptions that should remain intentionally archived
- repeatable validation so docs do not drift again
✅ Top-Level Index Coverage
Required directory indexes
about/README.md11_agents/README.mdagent-sdk/README.mdadvanced/README.mdanalytics/README.mdapps/README.mdarchive/README.mdbackend/README.mdbeginner/README.mdblockchain/README.mdcontracts/README.mddeployment/README.mddevelopment/README.mdexchange/README.mdexpert/README.mdgeneral/README.mdguides/README.mdgovernance/README.mdimplementation/README.mdinfrastructure/README.mdintermediate/README.mdmaintenance/README.mdmobile/README.mdnodes/README.mdopenclaw/README.mdpackages/README.mdpolicies/README.mdreference/README.mdreleases/README.mdreports/README.mdsecurity/README.mdtrail/README.mdwebsite/README.mdworkflows/README.md
Documented exceptions
cli-technical/is a special external technical entry point with a compliant landing pagetesting/is a special external documentation entry point with a compliant landing page
✅ Priority Document Checks
Core docs entry points
docs/README.mdhasLevel,Prerequisites,Estimated Time,Last Updated,Versiondocs/README.mdhas a navigation path and breadcrumbdocs/README.mdlinks toMASTER_INDEX.mdand the core learning pathsdocs/beginner/README.mdhas standardized metadata and cross-linksdocs/intermediate/README.mdhas standardized metadata and cross-linksdocs/advanced/README.mdhas standardized metadata and cross-linksdocs/expert/README.mdhas standardized metadata and cross-linksdocs/project/README.mdhas standardized metadata and cross-linksdocs/apps/README.mdhas standardized metadata and cross-linksdocs/about/README.mdlinks to the template standard and audit checklist
Historical or special content
docs/archive/README.mdclearly marks archive content as historicaldocs/archive/completed/README.mdclearly marks completed work as historicaldocs/implementation/README.mdremains intentionally lightweight until a future cleanup pass
✅ Cross-Link Checks
- Root docs point at the current hierarchy, not obsolete paths
- Beginner, project, and app landing pages point at each other where appropriate
- About pages link back to the template standard and the audit checklist
- Release notes link from the master index and release index
- Policy and governance documents cross-reference each other cleanly
✅ Validation Steps
- Review the directory tree and confirm each top-level docs area has an index.
- Confirm priority docs include the template fields and navigation sections.
- Record exceptions instead of leaving them ambiguous.
- Re-run the docs validation workflow after making any navigation changes.
📝 Current Remediation Notes
- Historical content stays in place unless it is clearly duplicated or misleading.
- The goal is discoverability and consistency, not flattening every directory.
- The following directories now have landing pages added in this pass:
about/,deployment/,development/,guides/,governance/,mobile/,nodes/,policies/,reference/,releases/,reports/,trail/, andworkflows/. - The project and apps landing pages now include template-compliant related resources and quality metrics sections.
- Legacy content
completed/andsummaries/directories were moved toarchive/completed/andarchive/summaries/for better organization. - Cross-link fixes applied: main README.md updated to point to archive locations, broken link in governance/openclaw-dao-governance.md removed.
- MASTER_INDEX.md updated to reflect new archive structure with 10 categories (156+ documents).
- Any future docs area should either include a README index or be documented here as an intentional exception.
Last updated: 2026-04-27
Version: 1.0
Status: Audit checklist