MinistryCentral Europe
Purpose
This document defines where canonical authority resides within MinistryCentral Europe’s content, platform, and documentation ecosystem.
It exists to:
- Prevent ambiguity about “who decides”
- Provide a reference point during disagreements or uncertainty
- Protect contributors and editors from unintentional overreach
- Ensure consistency across documentation, courses, and platforms
This is a normative reference. It does not describe workflows or tasks.
Core Principle
Not all content is equal. Authority depends on context, scope, and impact.
Authority is assigned to roles, not tools.
Levels of Canonical Authority
1. System-Level Canonical Authority
(Highest authority)
Applies to:
- Platform architecture
- Knowledge base structure
- Publishing rules
- Governance policies
- Canonical documents
Held by:
- Project Lead
- Designated Platform / Technical Stewards
Characteristics:
- Changes affect the entire system
- Decisions are binding once approved
- Silent changes are not permitted
Examples:
- Changing KB category structure
- Modifying publishing rules
- Altering canonical documents
2. Content-Level Canonical Authority
(Editorial authority)
Applies to:
- Official documentation
- Published KB articles
- Course-related instructional material
Held by:
- Content Editors
- Curriculum or Content Leads (within their scope)
Characteristics:
- Authority is bounded by governance rules
- Editors may improve clarity and consistency
- Substantive changes must follow review rules
Examples:
- Editing an onboarding guide
- Updating instructional wording
- Preparing content for publication
3. Contribution-Level Authority
(Provisional authority)
Applies to:
- Drafts
- Suggestions
- Source material
- Instructor submissions
Held by:
- Contributors
- Instructors
- Subject-matter reviewers
Characteristics:
- Contributions are non-canonical by default
- Content becomes authoritative only after approval
- Contributors are protected from responsibility for final decisions
Examples:
- Drafting lesson outlines
- Submitting documentation proposals
- Providing feedback or revisions
Tool Neutrality
Authority is not determined by the tool used.
Specifically:
- Notion does not confer authority
- Word documents do not confer authority
- Echo KB publication does not create authority on its own, although the Echo KB on the help.ministrycentral-europe.org site is the FIRST and primary location of authority, followed by Notion.
Authority flows from role and approval, not location.
Conflict Resolution Rule
When there is uncertainty or disagreement:
- Identify the level of authority involved
- Refer to this Canonical Authority Model
- Defer to the appropriate role holder
- Escalate only when scope exceeds delegated authority
No contributor or editor is expected to resolve authority conflicts independently.
Relationship to Other Documents
This model is referenced by:
- Content, Platform & Documentation Operations Guide
- Documentation Contribution Guide
- Content Editor Playbook
- Status Lifecycle & Canonical Rules
If guidance appears to conflict, this document takes precedence.
The Status Lifecycle & Canonical Rules document defines when content transitions into canonical residence within Echo KB.
Summary
- Authority is intentional, not implicit
- Roles define decisions, not tools
- Canonical content is protected by design
- Contributors are invited, not burdened
This model exists to enable collaboration without confusion or risk.