Acknowledge bylaws purposes 2-4: ecclesial partnerships, academic collaboration, learned societies

[JohnRDOrazio]

Context

An audit of all repo documents against the CDCF bylaws and manifesto found that three of the five chartered purposes receive little or no mention across the documentation.

Problem

The bylaws define five core purposes. Purposes 2, 3, and 4 are largely absent from the repo:

Purpose 2 — Ecclesial partnerships: Partner with Vatican entities, bishops' conferences, dioceses, and other Church institutions to organize, structure, preserve, and ethically manage ecclesiastical data (liturgical, scriptural, canonical, theological, historical).

• Almost no document mentions partnerships with Vatican entities or bishops' conferences
• Ecclesiastical data stewardship is not described as a CDCF function

Purpose 3 — Academic collaboration: Collaborate with Catholic universities and ecclesiastical faculties in theology, Scripture, canon law, moral theology, philosophy, and computer science/AI/data science.

• standards/committees.md mentions "Catholic university CS departments" once
• No document mentions collaboration with theology, Scripture, canon law, moral theology, or philosophy faculties
• No document describes academic partnerships as a source of projects or governance input

Purpose 4 — Learned societies: Work with Catholic learned societies involving clergy, religious, and lay professionals for interdisciplinary exchange between theology, pastoral practice, and technology.

• Not mentioned in any document in the repo

Additionally, project-governance/definitions.md defines "Member" as "An institution (diocese, school, health system) that formally supports the CDCF" — omitting Vatican entities, bishops' conferences, religious institutes, learned societies, and ecclesiastical faculties, all of which are explicitly named partner categories in the bylaws.

Suggested approach

• Update the definitions.md Member definition to include all bylaws partner categories
• Add language in README.md and governance documents acknowledging purposes 2-4
• Consider whether the committee structures should explicitly include seats for academic institutions and learned societies
• Frame the standards track (standards/overview.md) in terms of ecclesial data partnerships (purpose 2)

Affected files

• project-governance/definitions.md (Member definition)
• project-governance/committees.md (committee composition)
• standards/overview.md (ecclesial data partnership framing)
• README.md (mission/scope description)
• ai-governance/fragmented-catholic-ai-governance.md (landscape mapping)
• ai-governance/governance-as-code-catholic-ai.md (CDCF role description)
• ai-governance/ai-vetting-criteria.md (CDCF role description)

Dependencies

Should be implemented after #8 / PR #9 is merged.

Identified during bylaws/manifesto alignment audit.