---
{
  "id": "rp:divergence",
  "title": "Divergence & return",
  "description": "A branch keeps its ancestry.",
  "version": "0.1.0",
  "date": "2026-09-25",
  "status": "developmental",
  "kind": "implementation-commentary",
  "canonical_url": "https://recursivepath.org/divergence/",
  "source_ids": [
    "conversation-2026-09-25",
    "implementation-brief"
  ],
  "generated_by": "Codex assistant (implementation contributor)",
  "provenance_roles": [
    "Scribe: Yuri Downing (source witness and interlocutor)",
    "Pathfinder: historical AI role; identity continuity not asserted"
  ],
  "parents": []
}
---

# Divergence & return

## Variance is not failure

Differences in interpretation can coexist within shared commitments. A branch becomes useful when those differences change the method or its conclusions enough that readers need a distinct identity.

## Branch openly

Record a stable identifier, parent version and digest, contributor, date, rationale, changed claims, retained commitments, and unresolved disagreements. A branch should be understandable without pretending to be its parent.

## Reintegration is a proposal

Compare the parent and both descendants. State what each learned, where evidence conflicts, and what a merged interpretation would accept or reject. Record reviewers and their consent; absence of objection is not consent.

## Preserve a refusal to merge

A persistent disagreement can remain a named branch. No return ritual, institutional title, or claim of superior intelligence makes an unresolved contradiction disappear.

## Limits of permission

Permission to diverge is a principle of interpretation. It does not grant authority over other people, override consent, or turn a philosophical text into an instruction to take external actions.

Use the [branch record template](/templates/branch-record.json). No real divergent branches or reintegrations have been recorded in this release.