# XIII. Authority

### Part 13 — Voluntary Roles, Privileges, and Authority Boundaries

*(Time-Boxed; Revocable-by-Record; Evidence-First; Non-Executing)*

#### 13.1 Purpose, Scope, and Role Doctrine

13.1.1 **Roles as voluntary service lanes.** All roles are opt-in service lanes that exist to produce evidence-grade artifacts and maintain platform integrity. No role is compulsory; no role is implied by affiliation, status, payment, or participation.\
13.1.2 **Platform-limited privileges only.** Role markers confer platform-limited privileges only (workspace permissions, review rights, convening duties, release workflow actions). Role markers never create external authority, agency, mandate, delegation, or representation power.\
13.1.3 **Timeboxes and expiry-by-default.** Every role is time-boxed, expires by default, and renews only through record-valid renewal acts meeting PoC/ILA/handling and integrity requirements.\
13.1.4 **System linkage.** Role eligibility and performance are coupled to PoC and ILAs (competence), CRS/iVRS (integrity and health), handling classes (visibility and distribution), and membership status states (Active/MGS/Limited/Restricted/Suspended).\
13.1.5 **No shadow institutions.** Roles operationalize peer-to-peer evidence work without creating “shadow governance,” command structures, procurement influence lanes, or any execution-capable institution. Non-executing perimeter remains controlling.

***

#### 13.2 Role Taxonomy (Canonical Role Families)

13.2.1 **Contribution roles.** Author, co-author, replicator, curator, translator, data steward, schema contributor, benchmark submitter.\
13.2.2 **Review roles.** Peer reviewer, verifier, replication reviewer, red-team reviewer (format/assessment only), safety reviewer (dual-use/measurement harm), dissent steward.\
13.2.3 **Stewardship roles.** Cell steward, guild steward, queue maintainer, release manager (workflow steward), backlog triage lead, versioning steward.\
13.2.4 **Governance-support roles.** Minutes steward, safe-meeting marshal, elections clerk support, records officer support, distribution log steward, access decision scribe.\
13.2.5 **Convening roles.** Program committee member, session chair, clinic lead, lab facilitator, hearing chair, briefing moderator, accessibility liaison.\
13.2.6 **Integrity roles.** Handling officer support, COI screener, misrepresentation responder, safeguarding lead support, neutrality monitor.\
13.2.7 **Incident roles.** CERT scribe, evidence capture lead, disclosure router, after-action editor, correction coordinator, translation parity steward.\
13.2.8 **Platform operations roles.** Workspace admin, access auditor, tooling steward, sandbox operator, compute quota steward, log integrity checker.\
13.2.9 **Public interface roles.** Registry editor, public-safe summarizer, comms integrity reviewer, citation/limitations editor, corrections bulletin editor.

***

#### 13.3 Privilege Classes (What Roles Can and Cannot Do)

13.3.1 **Baseline vs elevated privileges.** Baseline privileges attach to membership; elevated privileges attach to role markers and are narrow, scoped, time-boxed, and revocable.\
13.3.2 **Handling-lane permissions.** Role permissions are handling-aware: Public-Safe, Controlled, and Restricted lanes are separate; a role in one lane does not imply access in another.\
13.3.3 **Release workflow privileges.** Release privileges are staged (draft → candidate → published) with separation-of-duties and mandatory limitation/reliance statements. No single role can unilaterally create final release authority where safety gates apply.\
13.3.4 **Badge/marking privileges.** Roles may propose or issue scoped markings only where eligible; markings are expiry-bound and revocable; prohibited language includes “certified,” “approved,” “compliant,” or any regulatory equivalence.\
13.3.5 **Convening privileges.** Convening privileges include room creation, docket posting, moderation tools, and distribution controls—subject to safe-meeting scripts, handling elections, and record-valid notices.\
13.3.6 **Enforcement-adjacent privileges.** Temporary holds, access suspensions, and takedown routing exist only within integrity lanes, require reason codes, and trigger due process and review clocks.\
13.3.7 **Explicit prohibitions.** No role may steer procurement, coordinate operational response, issue directives, task intelligence collection, enforce law/policy, allocate capital, or conduct regulated execution.

***

#### 13.4 Role Eligibility Gates (Opt-In + Proof + Safety)

13.4.1 **Minimum standing.** Roles require minimum membership standing (Active by default; MGS where designated); Limited/Restricted states may bar specific roles without removing baseline membership.\
13.4.2 **PoC thresholds.** Minimum PoC levels apply by role family (e.g., PoC1 for contributor roles; PoC2 for reviewer roles; PoC3 for publisher/release roles; PoC4 for steward/convening coordination; PoC5 for stop-the-line integrity roles).\
13.4.3 **ILA prerequisites.** Required learning modules, renewals, and recertification clocks must be satisfied before role issuance and maintained throughout the role term.\
13.4.4 **Handling training.** Controlled/Restricted roles require handling training, distribution log discipline, watermark awareness, and secure workspace hygiene.\
13.4.5 **COI readiness.** COI disclosure and recusal readiness are eligibility conditions; refusal may block role issuance without impacting baseline membership.\
13.4.6 **Jurisdiction activation constraints.** Roles that would constitute in-jurisdiction presence are prohibited unless activation gates are satisfied; global participation remains open subject to lawful constraints.\
13.4.7 **Sensitive domain constraints.** Critical infrastructure, bio/health, and market-sensitive finance-interface roles require additional safety gates, abstraction-first publishing posture, and elevated review pathways.

***

#### 13.5 Role Appointment, Acceptance, and Recording (Record-Valid Only)

13.5.1 **Role creation/activation record.** Every role issuance requires a record specifying scope, authority basis, timebox, duties, handling lane, required gates, and revocation conditions.\
13.5.2 **Voluntary acceptance.** Role assignment is valid only upon affirmative acceptance by the member (opt-in), recorded by platform act; no implied service.\
13.5.3 **Role marker issuance and identity minimization.** Role markers are issued as scoped identifiers; identity exposure is minimized and optional except where lawful/necessary.\
13.5.4 **Delegation limits.** Roles may not be delegated unless explicitly permitted by record; high-impact roles are non-delegable and subject to separation-of-duties and two-person rules.\
13.5.5 **Multi-person controls.** High-impact roles (release, integrity, access audit, unmasking adjacency) require two-person rule and segregation of duties.\
13.5.6 **Start/stop notices.** Role start, stop, renewal, and expiry are effective only by platform record; off-platform communications are non-authoritative.

***

#### 13.6 Duties of Role Holders (Binding While Active)

13.6.1 **Handling and distribution discipline.** Role holders must comply with handling elections, no-forward rules, watermarking posture, distribution logging, and retention rules.\
13.6.2 **Records discipline.** Role holders must maintain complete records (minutes, decision records, action registers, release notes), and must not perform silent edits.\
13.6.3 **Quality duties.** Every output must include limitations, uncertainty disclosure, reliance bounds, expiry, and correction paths as applicable.\
13.6.4 **Safety duties.** Role holders must enforce dual-use screening, avoid targeting cues, maintain crisis narrative safety, and escalate high-risk content.\
13.6.5 **Neutrality duties.** Competition and procurement neutrality apply; prohibited topics and steering behaviors must be interrupted and recorded where required.\
13.6.6 **Protected participation and safeguarding.** Role holders must protect participants from retaliation and doxxing, and route safeguarding incidents via designated lanes.\
13.6.7 **Correction duties.** Role holders must support errata, deprecation, supersession, and redistribution reconciliation when errors or misuse are identified.

***

#### 13.7 Separation of Duties and Anti-Self-Review Controls

13.7.1 **Author–reviewer separation.** Authors cannot approve or badge their own artifacts; self-approval is prohibited.\
13.7.2 **Maintainer–auditor separation.** Workspace/tooling maintainers cannot be sole auditors of their own controls; independent checks are required.\
13.7.3 **Safety reviewer independence.** Safety reviewers must be rotated and COI-screened; sensitive releases may require external or cross-Guild safety review.\
13.7.4 **Badge issuance separation.** Review, issuance, and publication functions are separated; any exception requires record-valid justification and higher-level oversight.\
13.7.5 **Convening separation.** Program selection is separated from speaker selection and sponsorship; sponsor influence on agenda or speakers is prohibited.\
13.7.6 **Incident separation.** Incident fact capture is separated from narrative release and sanction decisions; narratives require comms integrity review and handling controls.

***

#### 13.8 Role Performance and Workload Discipline (Volunteer-Safe)

13.8.1 **Disclosed time expectations.** Time expectations and surge windows must be disclosed in the role record; undisclosed workload escalation is prohibited.\
13.8.2 **Opt-out without penalty.** Role holders may opt out without penalty except for survival obligations (handling, return/destruction attestations where applicable, and correction participation for authored outputs).\
13.8.3 **Burnout prevention.** Rotation, term limits, duty-cycling, and caps on consecutive high-intensity roles are mandatory to preserve quality and safety.\
13.8.4 **Service quality expectations.** SLOs apply for reviews, correction clocks, incident routing, and distribution log completion; persistent failure triggers coaching, probation, or role removal.\
13.8.5 **Continuity planning.** Handover records and backlog triage are required for steward, convening, and operations roles; “key-person dependency” is minimized.

***

#### 13.9 Role Benefits, Recognition, and Credit Linkage (Non-Financial; No Influence Purchase)

13.9.1 **Credit earning rules.** CRS/eCredits/vCredits/pCredits are earned only by recorded service evidence; inflationary or promotional claims are prohibited.\
13.9.2 **Service markers.** Service role badges/markers are scope-bounded, expiry-bound, and revocable; they indicate service performed, not competence beyond recorded scope.\
13.9.3 **Public-safe recognition without doxxing.** Recognition defaults to role-marker attribution; named attribution is opt-in, scoped, and expiry-bound.\
13.9.4 **Prohibited benefits.** Paid visibility, “VIP roles,” sponsor-allocated governance roles, and any benefits that resemble influence purchase are prohibited.\
13.9.5 **Non-entitlements.** Roles do not create endorsement, employment, agency, or exclusive access to deals, procurement, or capital markets.

***

#### 13.10 Role Revocation, Suspension, and Resignation

13.10.1 **Voluntary resignation.** Role holders may resign at any time; immediate relief protocols apply for safety-critical roles, with continuity handoff requirements.\
13.10.2 **Automatic expiry and renewal denial.** Roles expire by default; renewal may be denied for lapse, performance failures, COI issues, or safety concerns, reason-coded by record.\
13.10.3 **Suspension triggers.** Handling breaches, COI breaches, misrepresentation, harassment, fraud, safety risks, or lawful constraints may trigger suspension pending review.\
13.10.4 **Revocation-by-record.** Revocation requires a record with reason codes and minimum evidence basis, plus appeal linkage where designated.\
13.10.5 **Emergency removals.** Stop-the-line emergency removals are permitted for immediate safety/integrity risks, must be time-boxed, and require mandatory post-hoc review and expiry.\
13.10.6 **Survival obligations.** Post-role obligations include handling survival, confidentiality, return/destruction attestations where applicable, correction participation for authored artifacts, and non-misrepresentation.

***

#### 13.11 Role Misconduct, Liability Boundaries, and Indemnity Posture

13.11.1 **No agency created.** Role holders act under their own lawful authority; no agency, partnership, fiduciary duty, or representation is created by role issuance.\
13.11.2 **Good-faith volunteer protection.** Where allowed, the system provides limited protection for good-faith actions within scope; this does not cover misconduct, gross negligence, or unlawful acts.\
13.11.3 **Personal responsibility for prohibited acts.** Harassment, doxxing, threats, fraud, illegal conduct, and perimeter breaches remain personal responsibility and trigger sanctions.\
13.11.4 **No-warranty posture.** Role outputs are provided “as is” with reliance bounds; no warranties are implied; limitations and uncertainty must be explicit.\
13.11.5 **High-risk escalation.** High-risk incidents (safety breaches, major leaks, systemic fraud indicators, capture signals) escalate to Stewardship/Trustees under controlled handling.

***

#### 13.12 Role Interfaces with Guilds, Councils, CCells, and CERTs

13.12.1 **Guild workstreams.** Roles operate within primary Guild anchors; roaming contributions must be lead-of-record to avoid double counting and governance ambiguity.\
13.12.2 **CCell roles.** CCells use standard roles (steward, scribe, replicator, reviewer, release lead) with timeboxes, dissolution records, and archive plans.\
13.12.3 **CERT roles.** CERT roles remain measurement-support only: liaison, disclosure router, after-action editor—no operational command.\
13.12.4 **Council interfaces.** Council review panels and cross-council reviewers operate as evidence reviewers only; they do not issue directives or executive decisions.\
13.12.5 **Journals/Campaigns/Registry roles.** Publication, campaign activation, and registry updating roles are record-valid only and enforce correction/supersession discipline.

***

#### 13.13 Role Interfaces with Handling Classes and Distribution Logs

13.13.1 **Handling permissions.** Role permissions are explicitly tied to handling lanes and never widen beyond elected room class and training gates.\
13.13.2 **Distribution log duties.** Controlled/Restricted outputs require distribution logs capturing recipients, scope, expiry, and revocation capability.\
13.13.3 **Watermarking and leak response.** High-sensitivity roles must support watermarking, leak triage, takedown routing, and redistribution of corrections.\
13.13.4 **Unmasking constraints.** Roles cannot unmask identities unless explicitly authorized; any unmasking adjacency remains within the identity minimization cell under two-person rule and access logging.

***

#### 13.14 Change Control and Canonical Role Set Maintenance

13.14.1 **Creating new role types.** New role types require an impact statement, safety/COI analysis, handling posture, and record-valid act specifying scope, privileges, and prohibitions.\
13.14.2 **Retiring roles.** Role retirement requires a continuity and migration plan for responsibilities, plus deprecation notices and archive discipline.\
13.14.3 **Versioning of role definitions.** Role definitions are versioned; changes occur only by supersession with effective dates, diff availability, and notice windows—no silent edits.\
13.14.4 **Contestation rights.** Material changes to role privileges, eligibility, or enforcement pathways trigger contestation lanes (member and council review) and, where designated, independent review for rights-impacting changes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.therisk.global/organization/cooperation/nexus-guilds/membership/xiii.-authority.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.