Broaden scope beyond "technology projects" to include data repositories and standards

[JohnRDOrazio]

Context

An audit of all repo documents against the CDCF bylaws and manifesto found that the documents consistently narrow the CDCF's scope to software/technology projects, omitting other chartered categories.

Problem

Bylaws purpose 1 charters the CDCF to steward four categories: open-source software, data repositories, technical standards, and digital platforms. Nearly every document in this repo treats the CDCF as if it only governs software projects:

• project-governance/lifecycle.md: "This document describes the stages through which a technology project passes within the CDCF."
• project-governance/project-types.md: "Foundation Projects are technology initiatives..."
• project-governance/project-vetting-criteria.md: "All technology projects submitted for CDCF incubation and graduation"
• README.md: "how the CDCF reviews, incubates, and graduates technology projects"

Data repositories and technical standards have no lifecycle pathway, no vetting criteria, and no governance structure defined for them. The standards/ track partially addresses standards but is framed as enabling software interoperability rather than as a co-equal purpose.

Suggested approach

• Broaden scope language in lifecycle, vetting, and README to cover all four bylaws categories
• Define lifecycle stages for data repositories and technical standards (may differ from software projects)
• Ensure vetting criteria accommodate non-software submissions
• Frame the standards track as a co-equal purpose aligned with bylaws purpose 2 (ecclesial data stewardship)

Affected files

• project-governance/lifecycle.md
• project-governance/project-types.md
• project-governance/project-vetting-criteria.md
• standards/overview.md
• README.md

Dependencies

Should be implemented after #8 / PR #9 is merged. ✅ PR #9 merged 2026-04-19.

Identified during bylaws/manifesto alignment audit.