Role Expectation Architecture¶

When coordination depends on a recurring social position, design the role as a clear, occupiable bundle of expected behaviours, authority, obligations, interfaces, support, conflict guards, and handoff rules.

Overview¶

When coordination depends on a recurring social position, design the role as a clear, occupiable bundle of expected behaviours, authority, obligations, interfaces, support, conflict guards, and handoff rules.

A role is an occupiable expectation bundle. It is not simply the person who currently holds it, the title used to label it, or the document that describes it. This archetype becomes useful when coordination depends on people knowing what a position is expected to do, what authority and obligations attach to it, how it connects to neighboring roles, how it is entered and exited, and how misuse or overload is corrected.

Why this is a distinct archetype¶

The accepted source set already contains many role-like components: role charters, role definitions, role-specific pathways, role-based access control, central coordinator roles, liaison roles, incident commander roles, and many others. Those are important mechanisms or components. They do not by themselves supply a parent archetype for the accepted prime role: the general pattern of attaching a behavior expectation bundle to an occupiable position. This draft fills that parent gap while preserving boundaries with emergence, accountability, decision-rights, institutional design, and access-control hosts.

Core components¶

Component	Description
Role Position Anchor ↗	Identifies the occupiable social position, office, niche, slot, or participation site that can be held by different actors over time. The role must be separable from the current holder; otherwise the pattern collapses into personality, identity, or ad hoc assignment.
Expected Behavior Bundle ↗	Defines required, permitted, discouraged, and forbidden behaviours attached to the role. This is the core of the target prime: a role is not merely a title but a bundle of normative expectations.
Authority and Permission Scope ↗	Specifies what the role-holder may decide, access, represent, approve, initiate, refuse, delegate, or escalate. Keeps role architecture distinct from but compatible with decision-rights and least-privilege patterns.
Obligation and Service Scope ↗	States what the role-holder owes to others, to the institution, to the system, to affected parties, or to the role itself. Prevents roles from becoming pure authority without service, care, repair, or accountability.
Role Interface Map ↗	Maps upstream inputs, downstream outputs, handoffs, dependencies, communication obligations, and collaboration boundaries for the role. A role functions as an interface between actors, expectations, resources, and decisions.
Eligibility and Competence Conditions ↗	Defines who may occupy the role, what preparation is required, what incompatibilities bar occupancy, and what support is needed. Role legitimacy depends partly on fit between position demands and holder capacity.
Appointment, Legitimacy, and Exit Rule ↗	Defines how a holder enters, is recognized in, rotates through, resigns from, is removed from, or sunsets the role. A role without entry and exit rules becomes captured by incumbents or ignored after turnover.
Accountability and Review Path ↗	Names how role performance, misuse, overload, neglect, and contested interpretation are reviewed and repaired. Role expectations become usable when answerability is attached to the position rather than only to individual goodwill.
Resource and Support Provision ↗	Provides the time, access, tools, information, staffing, authority, and relief needed to perform the role responsibly. Role design fails when obligations exceed resources or when authority is granted without capacity.
Role Conflict and Interest Guard ↗	Detects incompatible expectations, conflicts of interest, multi-role strain, capture risk, and hidden dual loyalties. This connects the parent role prime to its role_conflict child and conflict_of_interest neighbor.
Handoff, Substitution, and Succession Path ↗	Defines how work, authority, memory, relationships, and context move when a role-holder changes or is temporarily unavailable. A stable role should survive ordinary turnover, absence, delegation, and succession.
Interpretation and Exception Rule ↗	Defines who may interpret ambiguous expectations, when exceptions are permitted, and how contested role boundaries are resolved. Roles are partly normative and context-sensitive; they require legitimate interpretation, not only static definition.

Common mechanisms¶

Role Charter¶

Type: definition_artifact. Documents purpose, expectations, authority, boundaries, interfaces, resources, accountability, and review cadence for the role. This mechanism appears in accepted hosts; here it implements the broader role architecture.

Position Description or Office Mandate¶

Type: formal_role_artifact. Formalizes a role for employment, governance, stewardship, office-holding, or professional practice. Useful where legitimacy depends on written mandate and public recognition.

RACI or Decision Participation Matrix¶

Type: decision_interface_mapping. Maps who is responsible, accountable, consulted, informed, or empowered around recurring decisions. Use as an implementation mechanism without reducing the whole role to decision rights.

Role Card or Participation Card¶

Type: lightweight_role_cue. Gives participants a compact role description, expected behaviors, boundaries, and interaction cues. Common in workshops, games, deliberation, simulations, and rotating stewardship settings.

Onboarding and Role Shadowing Runbook¶

Type: transfer_and_learning. Transfers tacit role knowledge through apprenticeship, shadowing, checklists, and examples. Prevents role memory from being person-dependent.

Delegation Letter or Authority Envelope¶

Type: authority_scoping. Specifies delegated powers, limits, reporting duties, escalation conditions, and revocation routes. Useful when role authority is granted by another office or institution.

Role Compatibility Check¶

Type: conflict_screening. Tests whether a holder can occupy multiple roles without incompatible expectations, conflicts of interest, or overload. Connects to relation_constraint_enforcement and role_conflict boundaries.

Handoff Checklist¶

Type: continuity_control. Transfers open responsibilities, context, relationships, authority, records, exceptions, and known risks to a new or temporary holder. Essential for succession, shifts, on-call roles, and steward rotations.

Role Rotation or Deputy Schedule¶

Type: capture_and_resilience_control. Rotates role occupancy or assigns deputies to reduce capture, burnout, single points of failure, and status monopoly. Should preserve continuity through overlap and memory practices.

Conflict-of-Interest Disclosure¶

Type: integrity_control. Requires role-holders to disclose interests, relationships, obligations, or incentives that may distort role performance. Disclosure alone is rarely enough; it must be linked to mitigation or recusal.

Role Review Retrospective¶

Type: learning_and_recharter. Periodically reviews whether role expectations, resources, authority, legitimacy, and boundaries still fit the environment. Supports role adaptation without silent drift.

Swimlane or Service Blueprint¶

Type: interface_visualization. Visualizes role interfaces, handoffs, responsibilities, and dependencies across a process or institution. Useful when role boundaries are confused because the workflow is not visible.

Parameter dimensions¶

Occupancy stability: temporary, rotating, term-limited, permanent, hereditary, elected, appointed, or emergent.
Expectation precision: tacit norms, role cards, charters, legal mandates, professional standards, or executable runbooks.
Authority intensity: advisory, coordinating, gatekeeping, approving, enforcing, fiduciary, emergency, or symbolic.
Interface density: local role with few handoffs, hub role with many dependencies, boundary-spanning role, or broker role.
Conflict exposure: low-conflict service role, dual-loyalty role, adversarial review role, fiduciary role, or public-authority role.
Transfer burden: easy substitution, apprenticeship-dependent transfer, succession-sensitive office, or person-dependent tacit role.
Adaptation cadence: stable charter, scheduled review, event-triggered recharter, emergency override, or sunset path.

Invariants to preserve¶

A good role architecture preserves the distinction between role and holder, aligns authority with obligation and support, gives neighbors reliable interface expectations, includes legitimate entry and exit paths, protects against role conflict and capture, and keeps a role reviewable without making it so rigid that context-sensitive judgment disappears.

Target outcomes¶

The desired outcome is not merely a clearer title. The desired outcome is reliable social coordination: people can occupy the role, rely on it, hand it off, challenge it, resource it, rotate it, and adapt it without renegotiating the entire surrounding institution or workflow.

Neighbor distinctions¶

Against emergent_role_formation: use that neighbor when the primary question is whether a repeated contribution pattern should become a role. Use this archetype once a role must be designed, clarified, resourced, or reviewed.
Against decision_rights_clarification: decision authority is one component of a role. A role also carries expected behavior, obligations, interfaces, eligibility, support, legitimacy, and continuity.
Against accountability_chain_design: accountability chains trace answerability for actions. Role architecture defines the recurring position whose actions and omissions may become accountable.
Against institutional_rule_role_stabilization: an institution contains many rules, roles, memories, expectations, and legitimacy loops. This archetype focuses on the role-level unit within that wider arrangement.
Against least_privilege_access_design: role-based access is an implementation of one role component; it does not define the role itself.
Against network_broker_role: a broker role is a subtype or specialized component. This archetype governs the general role expectation bundle.

Failure modes to watch¶

The most common failure is title-without-architecture: the position has a name, but no one knows its real expectations. Other common failures include unfunded responsibility, authority without review, person-role fusion, role sprawl, invisible labor extraction, role conflict denial, and overformalized brittleness. These failures are structural, not merely interpersonal.

Worked example¶

A community platform has moderators, admins, topic stewards, and conflict mediators, but users and volunteers disagree about what each title means. Moderators are expected to enforce policy, counsel users, resolve disputes, maintain technical documentation, and absorb abuse, even though no single person has the time, training, authority, or support to do all of that. Applying this archetype, the platform separates role names from current holders, defines expected and forbidden behaviors, narrows each role's authority, creates handoffs and escalation rules, installs conflict-of-interest disclosure and recusal, provides onboarding and shadowing, rotates high-burden roles, and reviews the charter quarterly.

Non-examples¶

A one-time task assignment, a personality trait, a title on an org chart, a pure software type signature, or a whole institution design problem is not enough. The archetype applies when the design object is the recurring position-bound expectation bundle.

Common Mechanisms¶

Conflict-of-Interest Disclosure — Makes a decision-maker declare the relationships and incentives that could skew their judgment, so a specific decision can be checked for independence.
Delegation Letter or Authority Envelope — Transfers a bounded, revocable slice of decision authority to a named holder — stating exactly what they may decide, up to what limit, and what to do at the edge of that envelope.
Handoff Checklist — A structured transfer list that moves a role from an outgoing holder to a successor without dropping open commitments, live context, or hard-won know-how.
Onboarding and Role Shadowing Runbook — A structured ramp that brings a new holder up to a role's competence bar by provisioning support and mentorship and by having them learn through supervised shadowing of an experienced holder.
Position Description or Office Mandate — The founding document that establishes a position exists, states what its holder is responsible for and owes to others, and makes the role recognizable independent of whoever currently fills it.
RACI or Decision Participation Matrix — Lays every recurring task or decision against every role in a grid and tags each cell, so exactly one role is Accountable and no decision right is left blank or doubled.
Role Card or Participation Card — A single-role, at-a-glance card — this position, the few things you do, the near ones you don't, and whom you serve — small enough to hand someone the moment they step into the seat.
Role Charter — 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.
Role Compatibility Check — A pre-appointment screen that tests a proposed role assignment against the role's competence bar and against conflict and separation constraints, before the assignment is made.
Role Review Retrospective — A recurring session that puts the role itself — not the person in it — on the table: is it still needed, still sane in scope, still bearable, and what should change?
Role Rotation or Deputy Schedule — A standing schedule of who holds a role now, who covers when they're out, and who takes over next — so the position survives any single person leaving the seat.
Swimlane or Service Blueprint — Draws the work as parallel lanes — one per role — so every step, handoff, and 'whose job is this?' gap shows up as a line crossing (or failing to cross) a lane boundary.

Compression statement¶

Role Expectation Architecture treats a role as a position-bound expectation bundle rather than a title, personality, job slot, or one-time task assignment. The archetype separates the role from its current holder, defines expected behaviors and permissions, maps interfaces with other roles, provides legitimacy and resources, manages conflicts of interest and role strain, and preserves continuity across entry, exit, rotation, substitution, and rechartering.

Canonical formula: role_architecture = position_anchor + expectation_bundle + authority_scope + obligation_scope + interface_map + legitimacy_rule + support + accountability + conflict_guard + handoff_path + recharter_trigger

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (12)

Accountability: Responsibility for actions.
Agency: A system pursues representable goals through actions whose selection is sensitive to its beliefs about its situation, via a goal-representation, world-model, and action-selection coupling.
Coordination: Aligning independently controlled actors so their separate actions combine into a coherent collective outcome despite distributed decision-making and incomplete shared information.
Decomposition: Breaking a whole into parts that can be analyzed independently and recombined to reconstitute the whole, making complexity tractable through divide-and-conquer.
Delegation of Authority: Assign responsibility.
Institution: A durable, self-reproducing complex of rules, roles, and shared expectations.
Interface: A bounded, rule-governed surface across which two systems exchange information or control while hiding their internals, letting each evolve independently behind a stable contract.
Interpretation: Recover meaning from a representational substrate under a framework that makes some readings available and others not.
Role: A bundle of expected behaviours attached to a social position.
Site: A persistent, addressable position whose identity is given by its capacity to host or contain entities, surviving the turnover of whatever occupies it.
Social Norms: Shared expectations about how members of a reference group should behave, maintained through internalization and anticipated decentralized approval, correction, or sanction.
Transformation: A rule-governed mapping that restructures an input into a different output, holding certain invariants fixed while altering others.

Also references 15 related abstractions

Authority: The recognized, legitimate right to issue binding decisions within a defined scope, distinct from raw coercive force or mere persuasive influence.
Boundary: Defines system limits.
Capability Separation: Issuance is restricted to a privileged party while verification is open, tied by a forgery-prevention mechanism.
Conflict of Interest: Competing incentives.
Contextual Mode Switching: Adapt communication.
Division of Labor: Partition a joint activity into specialized sub-tasks assigned to distinct performers whose outputs are then re-integrated.
Formal vs. Informal Structures: Official vs actual systems.
Hierarchy: Organizes elements into levels or ranks.
Legitimacy: Accepted authority.
Network Broker Role: A network position combining upstream access, downstream tie capacity, and interpretive authority that makes its holder a productive required intermediary.

▸ Show 5 more

Variants¶

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Formal Office Role Charter · governance variant · recognized

A formally recognized office or position with explicit mandate, authority, duties, term, accountability, and succession rules.

Distinct from parent: It is the formalized office branch of the broader role-expectation architecture.
Use when: A role exercises institutional power or represents a collective; Legitimacy, term limits, appointment, or removal are central.
Typical domains: public administration, professional societies, platform governance, organizational management
Common mechanisms: position description or office mandate, delegation letter or authority envelope, handoff checklist

Emergent Contribution Role · temporal variant · recognized

A role first recognized from repeated contributions, tacit expectation, or informal reliance before any formal charter exists.

Distinct from parent: It concerns the informal-to-role transition path.
Use when: A group already relies on a contribution pattern but lacks a legitimate role boundary; Premature formalization would freeze a useful emergent pattern too early.
Typical domains: open source communities, mutual aid networks, research groups, startups
Common mechanisms: role review retrospective, role charter, onboarding and role shadowing runbook

Boundary-Spanning Role · subtype · recognized

A role whose expected behaviors focus on translating, brokering, coordinating, or mediating across group, domain, system, or boundary interfaces.

Distinct from parent: It is the cross-boundary branch of role architecture.
Use when: Coordination fails because separate groups lack a trusted interface; The role-holder must translate norms, language, evidence, requests, or constraints across boundaries.
Typical domains: knowledge brokering, interdisciplinary research, care coordination, platform moderation
Common mechanisms: swimlane or service blueprint, role charter, conflict of interest disclosure

Rotating Stewardship Role · governance variant · recognized

A role intentionally moved among qualified holders to distribute burden, prevent capture, preserve learning, and maintain continuity.

Distinct from parent: It is the rotation-and-substitution branch of role architecture.
Use when: A necessary role creates status monopoly, burnout, or single-holder dependency; The role can be safely transferred with overlap, documentation, and competency controls.
Typical domains: facilitation, on call operations, community stewardship, governance committees
Common mechanisms: role rotation or deputy schedule, handoff checklist, onboarding and role shadowing runbook

Role Conflict Resolution Branch · risk or failure variant · recognized

A branch of role architecture focused on resolving incompatible expectations across one or more roles held by an actor or position.

Distinct from parent: It handles a failure mode produced by multiple or overloaded roles.
Use when: A holder is pulled by incompatible obligations, loyalties, norms, or performance criteria; A role creates conflict of interest or expectation strain that cannot be solved by simple clarification.
Typical domains: medical ethics, journalism, public office, caregiving and work
Common mechanisms: role compatibility check, conflict of interest disclosure, role review retrospective

Near names: Role Design, Social Role Design, Position Expectation Design, Role Chartering, Role Boundary Governance.