Role Charter¶
Founding governance document — instantiates Role Expectation Architecture
Constitutes a role or governing body as a legitimate office — fixing its remit and decision authority, the path by which it answers for its actions, and how it is properly filled and vacated.
A Role Charter is the constitutional instrument that brings an office into being and makes its exercise of power legitimate. Where a position description says what the job does, the charter says by what authority it acts, to whom it answers, and how a person comes to hold or lose it. Its defining move is to couple authority with legitimacy: the role may decide certain things precisely because a recognized source ratified that it could, and that same source can call it to account or remove its holder. This is what distinguishes it from a delegation letter — the charter defines the office's standing remit generically, for whoever holds the seat, rather than granting a bounded slice of authority to one named person.
Example¶
An open-source project has outgrown its informal habits: when a serious vulnerability is reported, nobody knows who may embargo it, who may cut an emergency release without the usual review, or who speaks for the project on the public advisory. The maintainers write a Security Response Team charter. Remit and authority: the SRT may hold a report under embargo and ship an out-of-band security release without a full council vote. Accountability: it must publish a post-incident write-up to the steering council within roughly two weeks of disclosure. Appointment and exit: members are nominated by core maintainers, serve fixed terms, and may be removed by a council vote.
The next time a critical CVE lands, the team acts fast and within bounds — its power to move without the usual process is real, recognized, and answerable, rather than something an individual improvised and might later be accused of usurping.
How it works¶
- State the remit and its ceiling. Fix what the office may decide on its own authority and where that authority stops and must escalate.
- Name the accountability path. Specify to whom the role answers and what review it periodically undergoes.
- Set appointment, legitimacy, and exit. Define how the seat is filled, for how long, and how a holder is removed — the source from which the office draws its legitimacy.
- Ratify at a legitimate source. Have the charter approved by a body entitled to confer the authority, so the role's power is recognized rather than self-declared.
Tuning parameters¶
- Authority ceiling — how much the office may decide alone before it must escalate. A higher ceiling makes it decisive but concentrates risk.
- Accountability tightness — how often and how deeply the role is reviewed. Tighter is safer and slower and adds overhead; looser trusts more and catches drift late.
- Term and removability — long secure terms versus short or at-will ones. Security buys independence; easy removal buys responsiveness and resistance to capture.
- Ratification breadth — how widely the charter must be approved. Broader ratification confers more legitimacy but makes the charter harder to amend later.
- Amendment rule — how the charter itself may be changed. Rigid amendment stabilizes the office; easy amendment lets it adapt but weakens the constraint.
When it helps, and when it misleads¶
Its strength is that it makes power legitimate, bounded, and answerable in one instrument. It forecloses the two failures of ungoverned roles — self-appointed authority nobody sanctioned, and "who decided that, and on whose say-so?" — by attaching every grant of power to a source that can also withdraw it.
Its failure modes track the gap between paper and practice. A charter drifts when the office's real behaviour outgrows its written remit, so the document describes a role that no longer exists; too tight a charter starves the office of the discretion it needs and induces paralysis. The signature drift is mission creep — the remit quietly expands past what was chartered, one reasonable exception at a time.[1] And the classic misuse is to write or amend a charter to entrench a sitting incumbent, or to manufacture after-the-fact legitimacy for a decision already taken. The discipline that keeps it honest is periodic re-ratification against actual practice, and wiring the accountability path to real review rather than a nominal reporting line.
How it implements the components¶
This document fills the constitutional slice of the archetype — the authority, accountability, and legitimacy of the office — and leaves the day-to-day to other mechanisms:
authority_and_permission_scope— fixes, at the level of the office rather than the person, what the role may decide and where its authority stops.accountability_and_review_path— names to whom the office answers and the review it undergoes, so its power is not unaccountable.appointment_legitimacy_and_exit_rule— sets how the seat is legitimately filled, its term, and how a holder is removed: the source of the office's legitimacy.
It defines the office's standing authority, but does not grant that authority to a named individual (that is the Delegation Letter or Authority Envelope), enumerate the day-to-day duties (Position Description or Office Mandate), or map how the role interfaces with its neighbours (RACI or Decision Participation Matrix).
Related¶
- Instantiates: Role Expectation Architecture — it constitutes the office as a legitimate, bounded, answerable authority.
- Sibling mechanisms: Delegation Letter or Authority Envelope · Position Description or Office Mandate · RACI or Decision Participation Matrix · Role Review Retrospective · Conflict-of-Interest Disclosure
Notes¶
The charter defines authority for the office; a delegation letter hands a person a bounded slice of it. The two are complementary and layered: a delegation draws its legitimacy from the charter that established the office in the first place, which is why a delegation without a governing charter behind it is authority no one actually sanctioned. Keep the charter as the standing constitution and let delegations instantiate it — do not use one-off delegations to quietly expand what the office was chartered to do.
References¶
[1] Mission creep (or scope creep) — the gradual expansion of an office's remit beyond its original mandate through an accumulation of individually reasonable extensions. A charter's fixed remit and periodic re-ratification are the standard guards, which is why the accountability and amendment dials matter as much as the grant of authority itself. ↩