Documentation · Governance · Evidence

Documentation Quality Gate

Selected public-safe documentation pages from a private technical documentation hub. The focus is documented, controlled and reviewable technical delivery.

Documentation Quality Gate

Purpose

This repository uses a lightweight documentation quality gate to reduce accidental privacy, credential and overclaiming risks in technical documentation.

The goal is not to create a heavy compliance platform. The goal is to keep the documentation hub safe, reviewable and reusable.

What the gate checks

The validator checks Markdown files for:

Required documentation boundary style

Longer technical documents under docs/ should usually include at least one of these sections:

## Scope
## Non-goals
## Public/private boundary
## What this is not

This keeps the repository aligned with the hub principle:

Technical documentation should be useful without exposing private environments or overclaiming maturity.

Public/private boundary

This quality gate is intended to prevent documentation from accidentally including:

How to run locally

From the repository root:

python tools/validate_documentation_quality.py

Expected result:

DOCUMENTATION QUALITY GATE: PASSED

CI workflow

The GitHub Actions workflow is located at:

.github/workflows/documentation-quality-gate.yml

The workflow runs on Markdown documentation changes and on manual dispatch.

Non-goals

This gate does not replace:

It is a lightweight repository-specific guardrail for documentation hygiene.