Fix "filial submission" language in project-types.md

[JohnRDOrazio]

Context

An audit of all repo documents against the CDCF bylaws and manifesto found language in project-governance/project-types.md that conflicts with the bylaws' governance structure.

Problem

project-types.md states:

The Foundation is participated and governed by Church institutions themselves — dioceses, episcopal conferences, and bodies of the Holy See — and operates in filial submission to the Church hierarchy.

The bylaws establish the CDCF as an independent 501(c)(3) with a Board of Directors that has civil governance authority, and an Ecclesial Advisory Council that provides non-binding guidance. Saying the Foundation "is participated and governed by Church institutions themselves" and "operates in filial submission to the Church hierarchy" describes hierarchical subordination that goes beyond what the bylaws define. The EAC's advice is explicitly non-binding.

This language could create expectations of hierarchical authority over Foundation decisions that the bylaws do not grant.

Suggested approach

Revise to frame the CDCF's relationship to the Church hierarchy accurately: the Foundation partners with and serves Church institutions, and seeks alignment with Church teaching through the Ecclesial Advisory Council's non-binding guidance — but it is not canonically subordinate to the hierarchy in its civil governance.

Affected files

• project-governance/project-types.md

Dependencies

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

Identified during bylaws/manifesto alignment audit.

[JohnRDOrazio]

Important clarification from project maintainer — this reframes the issue:

The "filial submission" language is not incorrect per se — it is correctly applied to the governance of Catholic data itself. Catholic data that falls under the jurisdiction of ecclesial bodies (Dioceses, Bishops' Conferences, Vatican Dicasteries) — such as liturgical calendars, canonical records, sacramental data, doctrinal content — requires filial submission to competent Church authority. The Church has jurisdiction over its own data, and the CDCF's role is to steward that data faithfully.

The issue is that the current language in project-types.md applies "filial submission" too broadly — to the Foundation's governance as a whole — rather than scoping it precisely to where it applies.

The revised framing should distinguish:

1. Catholic data governance (liturgical, canonical, scriptural, theological, historical data under ecclesial jurisdiction) → filial submission to competent Church authority is required
2. Technical and practical implementation (how software is built, what architecture is used, deployment decisions) → ecclesial guidance is advisory and non-binding
3. Civil governance of the Foundation (finances, strategy, compliance, personnel) → governed by the Board of Directors as a 501(c)(3)

So rather than removing "filial submission," the fix should scope it correctly: the Foundation operates in filial submission to Church authority with respect to the Catholic data it stewards, while maintaining independence in its technical implementation and civil governance.