Skip to content

Model doctrinal development over time (Newman) #7

Description

@JohnRDOrazio

Context

John Henry Newman's theology of doctrinal development holds that doctrine is not static but unfolds organically over time. This has significant implications for how CMDDR models the relationship between documents across different historical periods.

Problem

The current table presents document types as timeless categories. Newman argues that doctrine develops historically, and a data model that cannot distinguish between contradiction and development, or between clarification and change, is structurally misleading.

Proposed Enrichment

The CMDDR data model should consider tracking:

  • Historical states — how a teaching was formulated at different points in time
  • Developmental notes — annotations on how a teaching evolved
  • Criteria of authentic development — Newman's seven "notes" for distinguishing genuine development from corruption:
    1. Preservation of type
    2. Continuity of principles
    3. Power of assimilation
    4. Logical sequence
    5. Anticipation of its future
    6. Conservative action upon its past
    7. Chronic vigour

Additional fields to consider:

  • stage_of_development — implicit, emerging, explicitly defined, dogmatized
  • earlier_formulations — links to prior expressions of the same doctrine
  • degree_of_clarity — how precisely the doctrine has been articulated

Impact on the Table

The README table could include a note acknowledging that document types and their authority may be understood differently across historical periods. The data model itself should support temporal layering.

References

  • John Henry Newman, An Essay on the Development of Christian Doctrine (1845/1878)
  • Vatican II, Dei Verbum §8 on the growth of tradition

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions