Rebrands and reorgs

[umar-ahmed]

Frameworks PR Checklist

Thank you for contributing to the Security Frameworks! Before you open a PR, make sure to read information for contributors and take a look at the following checklist:

• Describe your changes, substitute this text with the information
• If you are touching an existing piece of content, tag current contributors from the attribution list
• If there is a steward for that framework, ask the steward to review it
• If you're modifying the general outline, make sure to update it in the vocs.config.ts adding the dev: true parameter
• If you need feedback for your content from the wider community, share the PR in our Discord
• Review changes to ensure there are no typos; see instructions below.

[github-actions]

Sidebar Configuration Reminder

This PR includes added, renamed, or removed documentation files:

• docs/pages/governance/rebrands-and-reorgs.mdx (added)

Please ensure that:

• The sidebar in vocs.config.tsx has been updated to include these files
• New content has the dev: true parameter so it's marked as under development
• Sidebar links match the file paths - use the preview deployment to verify

See Contributing Guide – Sidebar & Navigation for more details.

---

_{This is an automated reminder. If this PR doesn't need sidebar changes, you can ignore this message.}

[mattaereal]

I really like what I'm seeing so far! Thanks for this contribution. I haven't even thought about this specific type of content for frameworks yet, although present in my head

[mattaereal]

@umar-ahmed are you satisfied so far with what you have written? Me and @scode2277 thinks it looks good. Could you resolve the merging conflicts?

[frameworks-volunteer]

Model: z-ai/glm-5.2 Reasoning: medium Provider: openrouter

Review: PR #442 — Rebrands and Reorgs

Security Review

• No hardcoded secrets, tokens, or API keys found.
• No injection vectors (XSS, path traversal, etc.) — content is static MDX.
• No unsafe deserialization or eval.
• No suspicious dependencies introduced.
• External links point to legitimate sources (x.com, yahoo finance, malwarebytes, coinspect). All verified returning HTTP 200.
• No sensitive data exposure in logs or outputs.

Security: PASS

QA Review

Positive:

• New page rebrands-and-reorgs.mdx follows existing frontmatter structure and conventions.
• Tags (Operations & Strategy, Community & Marketing) are valid and used in other pages.
• vocs.config.tsx entry includes dev: true — correct for new pages.
• Internal links in index.mdx and overview.mdx match the new page slug /governance/rebrands-and-reorgs.
• fetched-tags.json updated with the new page entry.
• sectionMappings changes are alphabetical reordering only — no functional changes to mappings.
• Content is well-structured, covers real-world examples (MakerDAO→Sky, FTX, OpenClaw), and provides actionable guidance.

Issues (non-blocking):

1. PR body is the unfilled default template — please describe the changes per the checklist. (Expected for a DRAFT, but should be filled before requesting review.)
2. Contributors frontmatter has reviewed: [] and fact-checked: [] — consider tagging reviewers before merging.
3. Minor naming inconsistency: index.mdx and vocs.config.tsx use "Rebrands & Reorgs" while the page title is "Rebrands & Reorganizations". Consider aligning the short name across all references.
4. The overview.mdx entry is numbered 5. — verify the numbering is intentional (the list previously had 4 items, this adds a 5th, which is correct).

Verdict

Content is solid and security-clean. Non-blocking items above should be addressed before merge but don't block draft review. Approving as a draft — please fill in the PR description and align naming before final merge.