Skip to main content

Change Register

This is the canonical change register for EchoHuman / Southville Forge infrastructure and project documentation.

Purpose​

  • Audits document what exists (current state)
  • Change register documents what changed and why (history)

Every completed project, service, or infrastructure change should add an entry here.

Entries (most recent first)​

2026-06-03 — Docsaurus Recovery and DocOps Governance​

Scope: Infrastructure documentation system recovery and governance framework

Summary:

  • Located canonical Docusaurus source on Vera filesystem
  • Created PROJECT-BOOTSTRAP.md as source-of-truth anchor file
  • Fixed local repository map to display all 23 Vera Git repos with full metadata
  • Created comprehensive DNS record map showing all 175 Cloudflare DNS records
  • Updated Cloudflare summary docs with DNS statistics
  • Added change-register.md (this file) and AGENTS.md for governance
  • Created finalize-docs-change.sh script for standardized workflow

Files created:

  • PROJECT-BOOTSTRAP.md
  • AGENTS.md
  • scripts/finalize-docs-change.sh
  • docs/cloudflare/dns-record-map.md
  • docs/reports/change-register.md

Files modified:

  • scripts/audit-vera-projects.py
  • docs/cloudflare/cloudflare-zone-index.md
  • docs/reports/cloudflare-audit-latest.md
  • sidebars.js
  • docs/vera/local-repo-map.md (regenerated)
  • docs/vera/project-map.md (regenerated)
  • docs/vera/unclassified-directories.md (regenerated)
  • docs/reports/vera-audit-latest.md (regenerated)
  • data/inventory/vera-projects.json (regenerated)

Infrastructure changes: None

Build status: PASSED

Deployment status: Ready (no deployment required for this task)

Notes:

  • This entry establishes the DocOps governance pattern
  • Future changes should follow: identify → change → document → build → report
  • AI agents should read AGENTS.md and PROJECT-BOOTSTRAP.md before any work

Entry Template​

Use this template for new entries. Copy and fill in the details:

### YYYY-MM-DD — Brief description

**Scope:** What project/service/infrastructure changed

**Summary:**
- What was done
- Why it was needed

**Source path:** `/path/to/source`

**Deployment target:** URL or server location

**Files changed:**
- `path/to/file.ext`

**Docs updated:**
- `docs/path/to/doc.md`

**Audit/Build result:** PASSED

**Deployment result:** Deployed / Pending / Not required

**Follow-up risks/warnings:**
- Any known issues or future work needed

Quick command to generate template:

./scripts/new-change-entry.sh "Description here"

Add new entries above this line.