Files
aitbc/docs/about/DOCUMENTATION_COMPLIANCE_AUDIT.md
aitbc b6529b548e
Some checks failed
Documentation Validation / validate-docs (push) Failing after 7s
Documentation Validation / validate-policies-strict (push) Failing after 2s
docs: update archive structure references and mark priority docs as complete
Consolidate completed/ and summaries/ into archive/ subdirectory, update all cross-references in README.md and compliance audit. Add multi-node blockchain workflow links to blockchain README. Remove broken governance best-practices link. Mark all priority document metadata checks as complete in compliance audit.
2026-04-27 12:13:02 +02:00

5.0 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 AuditYou are here

breadcrumb: Home → About → Compliance Audit


🎯 See Also:


🎯 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.md
  • 11_agents/README.md
  • agent-sdk/README.md
  • advanced/README.md
  • analytics/README.md
  • apps/README.md
  • archive/README.md
  • backend/README.md
  • beginner/README.md
  • blockchain/README.md
  • completed/README.md
  • contracts/README.md
  • deployment/README.md
  • development/README.md
  • exchange/README.md
  • expert/README.md
  • general/README.md
  • guides/README.md
  • governance/README.md
  • implementation/README.md
  • infrastructure/README.md
  • intermediate/README.md
  • maintenance/README.md
  • mobile/README.md
  • nodes/README.md
  • openclaw/README.md
  • packages/README.md
  • policies/README.md
  • reference/README.md
  • releases/README.md
  • reports/README.md
  • security/README.md
  • summaries/README.md
  • trail/README.md
  • website/README.md
  • workflows/README.md

Documented exceptions

  • cli-technical/ is a special external technical entry point with a compliant landing page
  • testing/ is a special external documentation entry point with a compliant landing page

Priority Document Checks

Core docs entry points

  • docs/README.md has Level, Prerequisites, Estimated Time, Last Updated, Version
  • docs/README.md has a navigation path and breadcrumb
  • docs/README.md links to MASTER_INDEX.md and the core learning paths
  • docs/beginner/README.md has standardized metadata and cross-links
  • docs/intermediate/README.md has standardized metadata and cross-links
  • docs/advanced/README.md has standardized metadata and cross-links
  • docs/expert/README.md has standardized metadata and cross-links
  • docs/project/README.md has standardized metadata and cross-links
  • docs/apps/README.md has standardized metadata and cross-links
  • docs/about/README.md links to the template standard and audit checklist

Historical or special content

  • docs/archive/README.md clearly marks archive content as historical
  • docs/archive/completed/README.md clearly marks completed work as historical
  • docs/implementation/README.md remains intentionally lightweight until a future cleanup pass

  • 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

  1. Review the directory tree and confirm each top-level docs area has an index.
  2. Confirm priority docs include the template fields and navigation sections.
  3. Record exceptions instead of leaving them ambiguous.
  4. 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/, summaries/, trail/, and workflows/.
  • The project and apps landing pages now include template-compliant related resources and quality metrics sections.
  • 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