Re-charter Workshop¶
Reset workshop — instantiates Objective Boundary Governance
A convened event that, when additions have outgrown the original charter, decides whether to prune, defer, or formally replace the objective with a new baseline.
The Re-charter Workshop is an episodic, convened event triggered when accumulated additions have changed the objective beyond its original envelope — the point where treating creep as continuity is no longer honest. Its defining trait is that it legitimizes a new baseline. Rather than policing additions one at a time, it steps all the way back and decides, with authority, whether to prune back toward the old charter, defer the extras, add capacity, or openly write a new charter. It is the archetype's designated off-ramp: the mechanism that makes a changed objective an explicit, authorized choice instead of an accident everyone drifted into.
Example¶
An open-source database project was chartered as "a lightweight embedded store." Over two years it accreted a query language, then a network server, then optional replication — each a reasonable response to real user demand. When a contributor proposes clustering support, a maintainer realizes the project can no longer honestly call itself "lightweight" or "embedded," and convenes a re-charter workshop: a summit of core maintainers with the authority to redefine the project.
They run the re-charter gate explicitly. Is clustering still inside "lightweight embedded store"? No — and neither were the last three big additions. The group decides to formally re-charter the project as "a distributed database," writing a new baseline that the next two years of additions will be judged against. The "stay-embedded" faction's concerns aren't discarded; they are parked into a documented, still-supported minimal-build option. The workshop's value is that the objective is legible again, and the change was chosen rather than suffered.
How it works¶
- Triggered by a gate condition — a threshold crossing (from an audit or dashboard) convenes the workshop; it is not a standing meeting.
- Convenes stakeholders with authority — the people who can actually redefine the objective, so the outcome is binding.
- Reviews the accumulated additions against the old charter — the whole trajectory, not the latest request, is on the table.
- Chooses among a fixed menu — prune back, defer, add capacity, or re-charter; "keep drifting silently" is explicitly not on it.
- If re-chartering, writes the new baseline — a fresh reference state that becomes the next charter, with the old one archived, not erased.
- Parks what it defers — additions it chooses not to admit or discard go to the parking lot with a revisit trigger.
Tuning parameters¶
- Trigger threshold — how much drift convenes a workshop. Too high and creep locks in first; too low and the org re-charters constantly.
- Convening authority — who can call it and who must attend; without real authority the new baseline won't bind.
- Option bias — whether the menu leans toward pruning or toward re-chartering. A re-charter-friendly bias adapts fast but can launder creep.
- Frequency cap — a floor between workshops, so re-chartering doesn't itself become a way to dodge discipline.
- Ratification path — how the new baseline is approved and communicated so it actually replaces the old reference.
When it helps, and when it misleads¶
Its strength is that it makes objective change legitimate and explicit. The archetype insists that a changed objective is not a failure if it is authorized, costed, and governed — and the workshop is where that authorization happens. It is the honest alternative to pretending the expanded objective was the plan all along.
Its failure modes are opposite. Convened too rarely, it arrives after the creep has already hardened into the unexamined baseline. Captured by whoever wants the expansion, it becomes a rubber stamp — re-chartering used to launder creep as a fresh mandate without any pruning. Both are forms of escalation of commitment[n1]: the pull to keep pouring resources into an expanded course because backing out feels like loss. The guarding discipline is to keep real pruning and deferral on the menu every time, require the workshop to state explicitly what the objective now excludes, and treat "re-charter to everything we've drifted into" as a red flag rather than a resolution.
How it implements the components¶
re_charter_gate— the workshop is the gate: the event where accumulated additions stop being ordinary changes and force a prune / defer / re-charter decision.charter_baseline— when it re-charters, it writes the new baseline that becomes the next reference state.deferred_objective_parking_lot— it parks the additions it chooses to defer rather than admit or discard.
It does not implement sub_objective_admission_rule — per-addition admission belongs to the Objective Change-Control Board — nor objective_dilution_signal (the Objective Drift Dashboard) or objective_boundary_ledger (the Sub-objective Decision Record). The Objective Charter writes the original baseline once at founding; the workshop convenes to replace an outgrown baseline with a new one.
Related¶
- Instantiates: Objective Boundary Governance — the workshop is the re-charter gate that legitimizes a changed objective instead of letting creep become the silent baseline.
- Consumes: Mission-Creep Audit supplies the verdict that triggers the workshop; Objective Charter supplies the old baseline it replaces.
- Sibling mechanisms: Objective Charter · Sub-objective Decision Record · Objective Change-Control Board · Objective Drift Dashboard · Mission-Creep Audit · Opportunity-Cost Review · Plus/Minus Boundary Review · Deferred Objectives Backlog
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Re-charter Workshop operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it a convened event that, when additions have outgrown the original charter, decides whether to prune, defer, or formally replace the objective with a new baseline.
Independent corroboration: The frozen evidence defines Re-charter Workshop as 'A convened event that, when additions have outgrown the original charter, decides whether to prune, defer, or formally replace the objective with a new baseline', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Communication, Facilitation & Learning — Re-charter Workshop includes features of a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Formal charter resets descend from organizational governance and project-management practice.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Independent reviewer agreement; high confidence.
Notes¶
[n1] Escalation of commitment, studied by Barry Staw, is the tendency to invest further in a failing or expanded course of action to justify prior investment rather than on the merits of continuing. A re-charter workshop is the deliberate off-ramp against it — a scheduled moment to reconsider the whole trajectory — which is why keeping pruning genuinely on the menu is essential. ↩