🎯 Architectural Purpose
In a mature Docs-as-Code ecosystem, project governance cannot rely on manual web forms or desktop word processors. Everything must be: 1. Scriptable in headless environments (zero interactive prompts required). 2. Version-controlled alongside source code in Git repositories. 3. Audited in CI/CD build pipelines before pull requests can be merged into production branches. 4. Exportable to executive formats (HTML/PDF) with embedded styling and full Arabic RTL typography support.
This technical guide provides actionable shell scripts, pipeline configurations, and headless recipes for automating Tasleemat across your enterprise toolchain.
flowchart LR
DEV["Developer / PM commit"] --> GIT["Git Repository Push"]
GIT --> CI["CI/CD Pipeline (GitHub Actions / GitLab)"]
subgraph Verification["Headless Quality Gates"]
CI --> V1["tasleemat test -v"]
CI --> V2["audit_forms.py (Schema Integrity)"]
CI --> V3["parity.py (1:1 EN/AR Structural Parity)"]
CI --> V4["validate_okf.py (Frictionless Package)"]
end
Verification --> EXPORT["Batch Exporter (export_deliverables.py)"]
EXPORT --> ARTIFACTS["Executive HTML / PDF Portals"]
💻 1. Headless CLI Scripting Recipes
The tasleemat CLI provides non-interactive flags designed for deployment scripts and automated workspace initialization.
A. Non-Interactive Project Workspace Scaffolding (init)
Generate a fully tailored project folder with zero interactive prompts:
#!/usr/bin/env bash
set -euo pipefail
PROJECT_CODE="PRJ-2026-CLOUD-01"
PROJECT_NAME="Enterprise Cloud Transformation"
PM_NAME="Sarah Al-Ahmad"
SPONSOR_NAME="Dr. Khalid Al-Mansour"
OUTPUT_DIR="./workspaces/${PROJECT_CODE}"
# Scaffold Tier 2 (Standard Enterprise) with Agile Pack in English and Arabic
tasleemat init \
--code "${PROJECT_CODE}" \
--name "${PROJECT_NAME}" \
--pm "${PM_NAME}" \
--sponsor "${SPONSOR_NAME}" \
--tier 2 \
--pack agile \
--lang both \
--out "${OUTPUT_DIR}"
echo "✅ Project workspace successfully scaffolded at ${OUTPUT_DIR}"
B. Automated Catalog Extraction in Scripts (list & search)
Query and parse deliverables inside automation workflows:
# Extract all risk-related deliverable IDs in JSON/Text format
tasleemat search "Risk" --lang en
# Count available Arabic templates
tasleemat list --lang ar | wc -l
C. Headless AI Configuration (config)
Configure LLM accounts in containerized build agents without user interaction:
# Configure Gemini provider in CI agent
tasleemat config set \
--provider gemini \
--model gemini-2.5-flash \
--key "${GEMINI_API_KEY}"
# View active configuration state
tasleemat config show
🖨️ 2. Batch Deliverable HTML & PDF Exporter (tools/export_deliverables.py)
Convert markdown deliverables into self-contained, publication-ready HTML documents with embedded CSS, typography fonts, and native Arabic Right-to-Left (RTL) styling:
# Export single English charter
python3 tools/export_deliverables.py \
forms/en/03_Initiating/01_Project_Charter/03_01_Project_Charter_Template.md \
-o ./dist/03_01_Project_Charter.html
# Export Arabic deliverable with native RTL styling
python3 tools/export_deliverables.py \
forms/ar/03_البدء/01_ميثاق_المشروع/03_01_ميثاق_المشروع_قالب.md \
-o ./dist/03_01_ميثاق_المشروع.html
# Batch export an entire project workspace directory recursively
python3 tools/export_deliverables.py ./my_project_workspace/
⚙️ 3. Enterprise CI/CD Pipeline Configuration
GitHub Actions Workflow Recipe (.github/workflows/governance_check.yml)
Implement this workflow to enforce that all project deliverables checked into Git pass structural parity, schema validity, and unit tests:
name: Enterprise Governance & Docs-as-Code Pipeline
on:
push:
branches: [ main, develop ]
pull_request:
branches: [ main ]
jobs:
governance-validation:
runs-on: ubuntu-latest
steps:
- name: Checkout Code Repository
uses: actions/checkout@v4
- name: Set up Python Environment
uses: actions/setup-python@v5
with:
python-version: "3.12"
cache: "pip"
- name: Install Tasleemat & Quality Dependencies
run: |
python -m pip install --upgrade pip
pip install -e .
pip install pytest typeguard pyyaml frictionless
- name: Run Schema & Governance Table Auditor
run: python3 tools/audit_forms.py
- name: Run 1:1 English-Arabic Parity Checker
run: python3 tools/parity.py forms/en forms/ar
- name: Run Open Knowledge Foundation (OKF) Data Package Validator
run: python3 tools/validate_okf.py
- name: Run Automated Master Test Suite (130+ Tests)
run: pytest tests/ -v
- name: Compile Executive Static Portal Site
run: python3 tools/generate_documentation_portal.py
- name: Upload Static Portal Artifacts
uses: actions/upload-artifact@v4
with:
name: enterprise-pmo-portal
path: site/
🔒 4. Production Security & Environment Best Practices
- API Key Hygiene:
- Never commit raw API keys into Git. Inject
GEMINI_API_KEYorOPENAI_API_KEYthrough CI/CD environment secrets or HashiCorp Vault. - Deterministic Offline CI:
- For pull request builds that must not incur API costs or external network dependencies, execute generation tests using the
--mockflag (tasleemat generate --mock). - Immutable Baseline Checks:
- In production audit workflows, compute SHA-256 hashes of approved baseline markdown files and assert that no modifications occur outside formal CCB change request pull requests.