Public Docs Separation Blueprint

⚠️ INTERNAL ONLY — Platform + Website Architecture
Not intended for public distribution.

Problem Statement

Internal documentation captures sensitive architecture, runbooks, and decision records. The future public AI/Ethics standards site must remain isolated so externally publishable content never leaks internal operations. This blueprint outlines how to separate concerns while planning a new, dedicated public property.

Non-Negotiables

• Never surface internal ADRs, incident reviews, or change management notes on the public site.
• Exclude operational runbooks, escalation trees, or alerting procedures from public content.
• Omit security posture specifics that would increase the attack surface or aid threat actors.

Target Architecture for the Public Site

• Repository: Create a dedicated repo (recommendation: rcs-standards-site) managed by the compliance and AI ethics working group.
• Framework: Adopt Astro with Starlight on a stable release channel for long-term documentation tooling.
• Governance: Establish an editorial review board, define a SemVer-based standards versioning policy, and maintain a public change log per release.

Publishing Model on Cloudflare Pages

• Host the public site in a single Cloudflare Pages project distinct from internal docs pipelines.
• Serve content from https://standards.example.com (final domain subject to branding review) with SEO features enabled.
• Enforce branch protection and preview workflows in the new repo before publishing.

Content Taxonomy

• Principles: High-level commitments the organization makes for AI/Ethics.
• Standards: Detailed, normative statements with SemVer identifiers.
• Controls: Implementable requirements that map standards to enforcement mechanisms.
• Compliance Mappings: Crosswalks to external regulations or industry frameworks.
• Reference Implementations: Sanitized, high-level exemplars without internal infrastructure specifics.

Relationship to Internal Docs

• Start with a manual “export and sanitize” workflow: internal authors curate excerpts suitable for public release, removing sensitive content.
• Track each exported artifact back to its internal source for traceability.
• Plan a deferred automation step: build a pipeline that redacts or transforms approved internal content into the public repo once governance tooling matures.

Next Steps (Docs Only)

• Socialize this blueprint with the platform, security, and compliance leads.
• Draft governance charters and review checklists for the future repo.
• Inventory internal materials that could become sanitized public content.