Successor Charter¶
Charter document — instantiates Second-System Complexity Restraint
The founding document that fixes what the successor must preserve, what it may improve this cycle, its protected invariants and escape path, and who holds the authority to change any of it.
Every other restraint mechanism needs a fixed point to defend against — a written statement of what "this successor" is. Successor Charter is that founding document. It records four things: the core contract (what value the successor must preserve from the predecessor and the limited improvements authorized for this cycle), the stakeholder expectation contract (what the successor is not doing now and what that means for each group), the protected invariants including a rollback path, and — decisively — the decision authority, naming who may amend the charter. Its defining role is to be the constitution: the durable, authoritative anchor the sibling mechanisms all point back to. It does not itself score, gate, schedule, or measure; it declares the boundaries and the amendment rule those active mechanisms then enforce.
Example¶
A city transit agency is launching the successor to its fare-payment system, moving from magnetic-stripe cards to a tap-to-pay platform. Before any design, the program writes a Successor Charter. The core contract states what must be preserved: every rider who can pay today must still be able to pay — including cash-reliant and unbanked riders — and the transition must not orphan the existing card base. The authorized improvements for this cycle are named and bounded: contactless bank cards and a phone app, and nothing else this release. The expectation contract spells out, per stakeholder, what is deferred: the open-loop retail-payments ambition the finance office wants is explicitly not this cycle, and the charter says so in writing so it cannot be relitigated in every meeting.
The invariants section fixes the non-negotiables — fare accuracy, rider privacy, and a rollback path keeping the legacy card readers live through a full parallel-run so a failed cutover cannot strand commuters. Finally, the authority section names the steering group that alone may amend the charter, and by what process. When a vendor later proposes bundling a loyalty program "while we're modernizing anyway," the answer is not a debate but a document: outside the core contract, not authorized this cycle, and only the steering group can change that.
How it works¶
- State the core contract as preserve + bounded-improve. Name the validated value that must survive and the explicit, limited set of improvements this cycle authorizes — the bound is the point.
- Write the expectation contract per stakeholder. For each group, record what is deferred and what that means for them, converting silent omissions into acknowledged, agreed deferrals.
- Fix invariants, including an escape path. Enumerate the non-negotiables (continuity, safety, privacy) and require a rollback path, so ambition cannot later trade them away.
- Name the amendment authority. Specify who may change the charter and how; without this, the charter erodes silently as everyone assumes their addition is the reasonable exception.
Tuning parameters¶
- Improvement-scope breadth — how much the charter authorizes for this cycle. A narrow charter maximizes launchability but may under-serve a genuinely changed context; a broad one re-opens the door to overload.
- Invariant strictness — how absolute the protected invariants are. Hard invariants give the mechanisms firm ground but can block a legitimately necessary trade-off later.
- Amendment friction — how hard the charter is to change. High friction protects against creep but can ossify the successor against real new information; low friction invites the very drift the charter exists to stop.
- Expectation-contract explicitness — how concretely each stakeholder's deferral is spelled out. More explicitness prevents relitigation but requires harder up-front conversations.
When it helps, and when it misleads¶
Its strength is giving the whole intervention a stable referent: the parity gate derives its checklist from the charter's core contract, the admission rubric defers to its authorized scope, and every "while we're at it" can be answered by pointing rather than arguing. By naming decision authority, it also fixes the classic scope-creep vector where nobody owns the boundary — echoing the project-management insight that scope, time, and cost form an iron triangle in which quietly expanding one silently breaks the others.[n1]
Its failure mode is the charter that is written once, celebrated, and then ignored — a founding document nobody consults becomes decoration while decisions drift elsewhere. It can also ossify: an over-strict charter with high amendment friction can lock a successor into a scope that a genuine change in the world has made wrong. The classic misuse is amending it informally — letting additions slip in without going through the named authority — which hollows out the contract while preserving its appearance. The guarding discipline is to make the charter load-bearing (the sibling mechanisms must actually cite it) and to route every change through the named authority, so the document stays the real boundary and not a museum piece.
How it implements the components¶
successor_core_contract— the charter authors it: the explicit statement of preserved value plus the bounded improvements authorized this cycle, from which the parity gate later derives its checklist.stakeholder_expectation_contract— the per-stakeholder record of what is deferred and what that means, agreed up front so deferrals need not be re-argued.rollback_or_escape_path— fixed as a protected invariant the charter forbids ambition from trading away, ensuring the successor is never made irreversible.
It does not enforce parity before expansion at build time — that runtime precondition is the Parity-Then-Expansion Gate, which consumes this contract; and it does not stress-test failure or stock the overreach casebook, which is the negative_example_casebook work of Second-System Premortem.
Related¶
- Instantiates: Second-System Complexity Restraint — supplies the founding contract, invariants, and authority the rest of the intervention defends.
- Sibling mechanisms: Architecture Decision Record with Future-Option Cost · Complexity Budget Review · Constraint-Release Inventory · Feature Admission Rubric · Parity-Then-Expansion Gate · Postlaunch Ambition-Thaw Review · Rewrite Scope Firewall · Second-System Premortem · Staged Release Ladder
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Successor Charter operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it the founding document that fixes what the successor must preserve, what it may improve this cycle, its protected invariants and escape path, and who holds the authority to change any of it.
Independent corroboration: The frozen evidence defines Successor Charter as 'The founding document that fixes what the successor must preserve, what it may improve this cycle, its protected invariants and escape path, and who holds the authority to change any of it', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Organization, Role & Governance — Successor Charter includes features of an enduring role, team, authority, channel, or governance body that allocates responsibility, but its defining operation is a standing rule, threshold, contractual commitment, or policy constraint governing future conduct.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: A founding instrument specifying successor mandate, invariants, amendment authority, and escape clauses is constitutional design.
Related originating lineages:
- Organizational & Management Science — Institutional succession requires scoped change authority.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: the founding document that fixes what the successor must preserve, what it may improve this cycle, its protected invariants and escape path, and who holds the authority to change….
- Systems Thinking & Cybernetics — Protected invariants preserve identity through transition.
Review resolution: The blind reviewers agree that law_governance is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The charter is the one mechanism here that is a declaration rather than an activity — its power comes entirely from being cited. A charter no sibling mechanism references has failed regardless of how well it is written; its correctness is measured by how often the gate, rubric, firewall, and ladder actually point back to it to settle a live dispute.
[n1] The iron triangle (or triple constraint) of project management — scope, time, and cost are interlocked, so enlarging scope without moving the other two silently sacrifices quality or delivery. The charter's bounded core contract is the discipline that keeps the scope corner from expanding unnoticed. ↩