Technical Documentation Hub
Documentation method hub for technical writing, project documentation, runbooks, decision records and governance-oriented knowledge management.
This repository collects documentation practices, templates and project documentation references used across infrastructure, DevSecOps, Microsoft identity, operational security and regulated IT portfolio work.
The repository itself is a private working hub. The Vercel site is a public-safe static preview of selected documentation pages, not a public mirror of all private material.
The purpose is not to act as a public CV. The purpose is to make technical knowledge reusable, transferable and reviewable.
Purpose
Technical documentation is not only a description written after the work is done.
In operational and regulated environments, documentation is part of the control system:
Can another person understand the system?
Can a decision be reviewed later?
Can a change be traced?
Can an incident be reconstructed?
Can a handover happen without tribal knowledge?
Can evidence be separated from private customer data?
This repository is a central place for those patterns.
Scope
This hub covers:
- GitBook-style structured documentation
- GitLab/GitHub Markdown documentation
- Obsidian-style knowledge base structure
- project README patterns
- runbooks and operational notes
- decision records
- incident notes
- portfolio project documentation indexes
- project documentation cards
- portfolio spine roadmap and reading guidance
- cybersecurity governance perspective
- identity security and Active Directory perspective
- AI agent authority boundary governance
- public/private documentation boundaries
- audit and evidence-oriented writing
- Microsoft identity and Active Directory troubleshooting documentation
- lightweight documentation quality gate validation
- public-safe static documentation previewing
Repository structure
.github/workflows/
documentation-quality-gate.yml
docs/
AI_AGENT_ACCESS_BOUNDARIES_DEVSECOPS_GOVERNANCE.md
CYBERSECURITY_GOVERNANCE_PERSPECTIVE.md
DOCUMENTATION_PRINCIPLES.md
DOCUMENTATION_QUALITY_GATE.md
ESP32_GATEHOUSE_QUALITY_GATE_CASE_STUDY.md
IDENTITY_SECURITY_ACTIVE_DIRECTORY_PERSPECTIVE.md
KNOWLEDGE_BASE_STRUCTURE.md
LIGHTHOUSE_STATIC_PREVIEW_AUDIT_2026-06-23.md
OBSIDIAN_STYLE_WORKFLOW.md
PORTFOLIO_CODE_REPOSITORY_AUDIT_2026-06-23.md
PROJECT_DOCUMENTATION_INDEX.md
PORTFOLIO_NARRATIVE.md
PORTFOLIO_SPINE_ROADMAP.md
PUBLIC_STATIC_PREVIEW_BOUNDARY.md
QUALITY_GATE_ARCHITECTURE_DECISION.md
RBAC_LITE_LOCAL_DOCKER_ENVIRONMENT_CASE_STUDY.md
TECHNICAL_DOCUMENTATION_DEPLOYMENT_RECOVERY_SUMMARY_2026-06-23.md
VERCEL_AI_GATEWAY_LOCAL_TEXT_GENERATION_TEST.md
VERCEL_RECOVERY_CODES_HANDLING_NOTE.md
active-directory/
README.md
ad-ds-troubleshooting-guide.md
ad-ds-command-reference.md
ad-ds-interview-notes.md
evidence/
applied-skills-ad-ds-2026-05.md
tools/
build-vercel-static-site.mjs
validate_documentation_quality.py
templates/
technical-note-template.md
decision-record-template.md
indexes/
portfolio-projects.md
project-summaries.md
projects/
gatehouse.md
esp32-iot-security-governance-lab.md
rbac-lite.md
sadepois.md
local-first-wordpress-devsecops-kit.md
ai-itsm-compliance-auto.md
oaas-governance-note.md
haas.md
Key indexes and narratives
| Document | Purpose |
|---|---|
docs/PORTFOLIO_NARRATIVE.md | Explains the common theme across the portfolio |
docs/PORTFOLIO_SPINE_ROADMAP.md | Provides a reading roadmap for the project layer, interpretation layer and control/evidence layer |
docs/CYBERSECURITY_GOVERNANCE_PERSPECTIVE.md | Connects the portfolio to cybersecurity, MITRE-style threat reasoning, OWASP-style application security and container-hardening boundaries |
docs/IDENTITY_SECURITY_ACTIVE_DIRECTORY_PERSPECTIVE.md | Connects AD DS, identity security, RBAC, access chains and the idea of identity as a security boundary |
docs/AI_AGENT_ACCESS_BOUNDARIES_DEVSECOPS_GOVERNANCE.md | Documents a public-safe AI agent authority boundary governance lesson around scope control, approval gates and recovery principles |
docs/PORTFOLIO_CODE_REPOSITORY_AUDIT_2026-06-23.md | Records the source-level portfolio repository audit and prioritized improvement backlog |
docs/DOCUMENTATION_QUALITY_GATE.md | Explains the lightweight documentation quality gate and public/private boundary checks |
docs/PUBLIC_STATIC_PREVIEW_BOUNDARY.md | Defines the boundary between the private repository and the public-safe Vercel static preview |
docs/TECHNICAL_DOCUMENTATION_DEPLOYMENT_RECOVERY_SUMMARY_2026-06-23.md | Summarizes the Vercel static preview recovery work and why it matters |
docs/LIGHTHOUSE_STATIC_PREVIEW_AUDIT_2026-06-23.md | Records the final desktop/mobile Lighthouse baseline result after layout and SEO improvements |
docs/QUALITY_GATE_ARCHITECTURE_DECISION.md | Explains why different repositories use different governance controls instead of one forced model |
docs/ESP32_GATEHOUSE_QUALITY_GATE_CASE_STUDY.md | Case study for embedded Gatehouse quality gate design, validation failures and ruleset alignment |
docs/RBAC_LITE_LOCAL_DOCKER_ENVIRONMENT_CASE_STUDY.md | Case study for local Docker Compose validation, MariaDB healthcheck improvement and safe Git branch recovery in RBAC-Lite |
docs/VERCEL_AI_GATEWAY_LOCAL_TEXT_GENERATION_TEST.md | Local Vercel AI Gateway text-generation test, package setup, plugin limitation and credit-card verification boundary |
docs/VERCEL_RECOVERY_CODES_HANDLING_NOTE.md | Handling rule for Vercel recovery codes, safe storage boundaries and observed 404 troubleshooting context |
docs/active-directory/README.md | Index for AD DS troubleshooting, command references and learning evidence |
indexes/portfolio-projects.md | Short project-to-documentation mapping |
indexes/project-summaries.md | Structured summaries of the main portfolio projects, including evidence and boundaries |
Project documentation cards
| Project card | Purpose |
|---|---|
projects/gatehouse.md | Change governance and quality gate evidence |
projects/esp32-iot-security-governance-lab.md | Embedded / edge-device governance with CI evidence |
projects/rbac-lite.md | Access-control governance and audit trail thinking |
projects/sadepois.md | Applied platform context and governance narrative |
projects/local-first-wordpress-devsecops-kit.md | Local-first development baseline and handover structure |
projects/ai-itsm-compliance-auto.md | AI-assisted ITSM and compliance documentation consistency |
projects/oaas-governance-note.md | CI/CD trigger governance and operational documentation around a forked platform repository |
projects/haas.md | Managed-service style documentation for lab/home infrastructure |
Knowledge sections
| Section | Purpose |
|---|---|
docs/active-directory/ | Active Directory Domain Services troubleshooting and Microsoft identity operations notes |
Static preview
This repository can be rendered as a lightweight public-safe static documentation preview through Vercel.
The preview is generated by:
npm run vercel-build
The related configuration is:
vercel.json
package.json
tools/build-vercel-static-site.mjs
The static preview is not a production documentation platform. It is a selected, sanitized preview layer.
Quality gate
This repository includes a lightweight documentation quality gate:
python tools/validate_documentation_quality.py
The related GitHub Actions workflow is:
.github/workflows/documentation-quality-gate.yml
The gate checks for documentation hygiene issues such as accidental credential identifiers, private key material, unscoped production-readiness claims and missing documentation boundary sections.
Documentation principles
This repository follows a few simple principles:
1. Documentation should reduce operational ambiguity.
2. Documentation should make ownership and responsibility visible.
3. Documentation should separate public examples from private evidence.
4. Documentation should support handover, auditability and review.
5. Documentation should not overclaim project maturity.
6. Documentation should preserve the boundary between learning, portfolio work and production systems.
7. Public previews should contain only sanitized, public-safe material.
Portfolio documentation role
This hub can reference portfolio repositories, but it should not replace their own README files.
Each project should keep its own local documentation, while this repository acts as an index and method library.
Examples of documentation themes:
| Theme | Example repository type |
|---|---|
| Change governance | Gatehouse / quality gate projects |
| Access-control governance | RBAC / identity / tenant-isolation examples |
| Identity security | AD DS / groups / attributes / GPO / application access chains |
| AI agent governance | AI-assisted delivery boundaries, approval gates and recovery evidence |
| Embedded governance | ESP32 / edge-device governance labs |
| Local-first development | WordPress / Docker / safe local baseline |
| Cybersecurity governance | MITRE-style threat reasoning, OWASP-style application security and container-hardening boundaries |
| Microsoft identity operations | AD DS / DNS / replication / GPO troubleshooting notes |
| ITSM and automation | AI-assisted ITSM and compliance workflows |
| Operational service model | OaaS / operations and service-management notes |
What this is not
This repository is not:
- a production documentation repository
- a customer evidence archive
- a public storage location for private material
- a certification claim
- a replacement for project-specific documentation
- a marketing-first portfolio site
- a public mirror of all private notes
It is a working documentation hub with a public-safe static preview layer.
One-sentence summary
This repository organizes how technical knowledge is written, linked, reviewed, previewed and transferred across infrastructure, DevSecOps and regulated IT work.
Published documentation pages
- Documentation Quality Gate
- Quality Gate Architecture Decision
- Portfolio Narrative
- Portfolio Spine Roadmap
- Cybersecurity Governance Perspective
- Identity Security and Active Directory Perspective
- AI Agent Authority Boundaries in DevSecOps Workflows
- Portfolio Code Repository Audit 2026-06-23
- Public Static Preview Boundary
- Deployment Recovery Summary 2026-06-23
- Lighthouse Static Preview Audit 2026-06-23
- Vercel Recovery Codes Handling Note
- Vercel AI Gateway Local Text Generation Test
- RBAC-Lite Local Docker Environment Case Study
- ESP32 Gatehouse Quality Gate Case Study
- AD DS Troubleshooting Guide
- AD DS Command Reference