Clarify "canonical standard" language to avoid overstating CDCF authority

[JohnRDOrazio]

Updated 2026-05-02: PR #9 has merged. File paths below have been updated to reflect the post-merge repo structure — the ai-governance/ research memos have moved to research/ with broadened (non-AI-specific) scope.

---

Context

An audit of all repo documents against the CDCF bylaws and manifesto found that several documents use "canonical" in ways that could imply the CDCF has or seeks ecclesiastical (canon law) authority.

Problem

The research/fragmented-catholic-digital-governance.md memo (formerly ai-governance/fragmented-catholic-ai-governance.md) repeatedly uses "canonical" to describe the CDCF's proposed standard:

"without a shared canonical protocol that could provide coherent institutional guidance"
"subsidiarity without a shared canonical foundation"
"The CDCF vetting standard is designed to fulfill that requirement: preserving local authority while establishing the mutual accountability that isolated local action cannot provide."

The bylaws specify that the Ecclesial Advisory Council provides only non-binding theological/canonical guidance. The CDCF is a 501(c)(3) civil nonprofit — it cannot issue canonical standards in the Church-law sense.

The document sometimes uses "canonical" loosely (meaning "standard" or "authoritative"), but the context — diocesan governance, episcopal decrees, CST — makes it read as a canon-law claim. This risks implying the CDCF positions itself as a quasi-canonical authority rather than a civil nonprofit offering voluntary, non-binding guidance and tools.

Suggested approach

• Distinguish between "canonical" (in the canon-law sense) and "canonical" (in the software/standards sense of "reference" or "authoritative")
• Where the document means "reference standard," use clearer language: "reference standard," "shared baseline," or "common framework"
• Where the document discusses actual canonical implications, make clear the CDCF's role is advisory and non-binding
• Add a note that the CDCF's standards are voluntary and do not carry canonical force

Affected files

• research/fragmented-catholic-digital-governance.md (primary)
• project-governance/committees.md (uses "canonical" in TCSC name)
• project-governance/definitions.md

Dependencies

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

Identified during bylaws/manifesto alignment audit.