FranOps

FranOps (Memory / Canon)

Protected institutional memory that outlives any individual.

FranOps guards the canon — mission, architecture commitments, and public promises. These are the things that must survive personnel changes. Changing canon is a deliberate, versioned act with a changelog entry and a steward's approval.

Source: coherence/canon/

---

Canon Files

File	Purpose
mission.md	Why this project exists
architecture.md	Core architectural commitments and boundaries
public-commitments.md	Promises made to users, partners, stakeholders
changelog.md	Every change to canon, with date, rationale, and DLR link

---

Rules

1. All canon changes require a changelog entry — CI will block if changelog.md isn't updated in the same PR
2. Canon changes should be reviewed by a Canon Steward — the designated owner of institutional memory
3. Canon is append-mostly — supersede, don't delete
4. When canon changes, check downstream — existing DLRs and assumptions may be affected; open DriftOps signals if needed

---

Canon Steward

The Canon Steward is responsible for:

• Reviewing PRs that touch coherence/canon/
• Ensuring changelog entries are complete
• Triggering drift signals when canon changes invalidate existing decisions

Assign a Canon Steward in your team's first Training session.

---

Public Commitments

Commitments are canon entries that face outward — promises to users, adopters, or partners. Breaking a commitment requires a DLR explaining why, a canon changelog entry, and notification to affected parties.

---

See Also

• ReOps — decisions that may change canon
• DriftOps — what happens when canon is contradicted
• Policy Gates — Gate 3: canon changelog enforcement