Skip to content

governance: authorize and record public documentation review #2

Description

@litroc

Required decision

The production approval gate is intentionally blocked until the organization authorizes real GitHub identities for both committed approver roles and those reviewers approve the exact documentation tree.

Current review candidate:

  • PR: feat: launch the public documentation platform #1
  • head commit: ebea806c7b322ed09e0aee4a148d69b3f8e9f67f
  • 65-document content-tree SHA-256: e945cd49123213d4c1d8c3aeb03fbd68b33b384f145219e4481f3b51d8fe7612
  • Product Owners scope: 54 documents
  • Security and Compliance Maintainers scope: 11 documents

Acceptance

  • An organization owner maps authorized GitHub identities to both roles in evidence/document-approval-authorities.json and changes its status only through a reviewed PR.
  • Product, technical, security, and licensing reviewers inspect the exact pending pages and public migration target index.
  • Each document is changed from review-candidate/pending only after its accountable review succeeds.
  • evidence/document-approval.json covers the exact final content digest and document ID set with role-matched reviewer decisions and dates.
  • npm run test:approval passes on the exact release candidate.

Do not use an administrator merge, bot comment, or this issue's closure as a substitute for the approval record.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions