Skip to content

RFCs

This directory records proposed changes to the scope, terminology, principles, patterns, and governance model of Because Drift Happens.

RFCs are useful when a change affects more than one document or introduces a new conceptual commitment.

When To Write An RFC

Use an RFC for:

  • New core terminology.
  • Changes to framework scope.
  • New architecture pattern categories.
  • Significant revisions to principles.
  • Changes to contribution or terminology policy.
  • Formal relationships to implementation repositories.

RFC Style

An RFC should be clear, bounded, and operationally grounded. It should describe the problem, proposed change, rationale, risks, and affected documents.

See 0001-framework-scope.md for the initial scope RFC.