Skip to content
Documentation

ADR-0006 Public Standards Docs as Separate Site

Status

Section titled “Status”

Accepted

Context

Section titled “Context”

AI/Ethics standards must be communicated publicly, but the existing internal documentation site (apps/docs, future https://docs.example.com) hosts sensitive architecture, security, and operational material. Publishing those details externally would expose incident response procedures, runbooks, and decision records that should stay internal. A clean separation is necessary so public audiences receive curated guidance without risking disclosure of internal processes.

Decision

Section titled “Decision”

Create and operate a dedicated public documentation site, hosted in its own repository and Cloudflare Pages project, to publish AI/Ethics global standards. The existing internal docs remain locked behind Cloudflare Access and continue to record operational context.

Rationale

Section titled “Rationale”
  • Segregating repositories and build pipelines prevents accidental exposure of internal files.
  • A distinct governance model enables compliance and ethics stakeholders to manage public messaging without depending on platform engineering release cadences.
  • Dedicated domain branding (e.g., https://standards.example.com) clarifies that content targets external audiences and is safe to share broadly.
  • Using the same Astro/Starlight tooling keeps authoring consistent while allowing tighter review controls around what becomes public.

Consequences

Section titled “Consequences”
  • Teams must maintain two documentation footprints: internal operational knowledge and public standards narratives.
  • Additional onboarding is required for the public repo, including editorial workflows and branch protections.
  • Release coordination includes a sanitization review to ensure no internal-only references slip into public materials.
  • Automation for exporting approved content must be built incrementally; manual processes introduce overhead in the interim.

Deferred Considerations

Section titled “Deferred Considerations”
  • Automated pipelines that redact or transform approved internal content into the public repo.
  • Localization and accessibility reviews for the public-facing site.
  • Integration with analytics and consent tooling suitable for a public domain.
  • Legal review workflows for standards that reference regulated markets.

Implementation Steps (Docs Only)

Section titled “Implementation Steps (Docs Only)”
  1. Draft a repository proposal (name: rcs-standards-site) and secure ownership by the compliance and AI ethics working group.
  2. Produce governance documents: editorial charter, SemVer versioning rules for standards, and a mandatory change log template.
  3. Document a manual export/sanitization checklist for content transitioning from internal docs to the public site.
  4. Outline the Cloudflare Pages deployment plan, including domain (standards.example.com placeholder) and SEO configuration requirements.
  5. Share this ADR and the architecture blueprint with stakeholders; collect sign-off before repository creation.

Verification Method

Section titled “Verification Method”
  • Governance board ratifies the new repository plan and associated charters.
  • Manual export checklist is in place and used for any pilot publication.
  • Cloudflare Pages deployment plan aligns with security expectations and does not reference internal infrastructure.
  • Internal docs retain Cloudflare Access enforcement, with no public URLs serving sensitive material.