# XXIV. Registry ### Part 24 — Registry and Public Trust Surfaces *(Binding objective: the Registry is a **system-of-record**, not an authority engine. It must enable **trust-under-scrutiny** through record-valid states, correctionability, handling discipline, and doxxing-resistant visibility.)* #### 24.1 Purpose, Scope, and Public-Trust Doctrine 24.1.1 **Registry as system-of-record.** The Registry records membership states, roles, outputs, and integrity actions; it confers **no authority** and implies **no endorsement**.\ 24.1.2 **Public trust surfaces.** Publishable, contestable visibility surfaces that preserve privacy and safety while supporting legitimacy and auditability.\ 24.1.3 **Non-executing perimeter reaffirmed.** Registry entries never authorize operations, procurement, enforcement, dispatch, underwriting, custody, or settlement.\ 24.1.4 **Validity-by-record.** All Registry entries, changes, and disclosures are effective only when record-valid, time-stamped, and supersession-linked.\ 24.1.5 **Voluntary visibility baseline.** Default privacy; visibility is opt-in and scope-bounded except for minimal integrity/safety disclosures required by policy/law.\ 24.1.6 **Non-regression.** Handling, safety, and due-process protections cannot be weakened by visibility choices or “public profile” settings. *** #### 24.2 Registry Architecture and Layers 24.2.1 **Canonical registers.** Member Registry; Role Registry; Artifact Registry; Badge Registry; Sanctions & Restrictions Register; Corrections & Supersession Register.\ 24.2.2 **Layer separation.** Public-safe layer; Controlled layer; Restricted layer; each with independent access rules and disclosure minima.\ 24.2.3 **Identity minimization cell integration.** Identity mapping is separated; two-person unmasking rule; access-logged; lawful necessity standard.\ 24.2.4 **Namespace controls.** Reserved names, labels, and terms (“node,” “chapter,” “office,” “certified”) with anti-impersonation enforcement.\ 24.2.5 **Multi-jurisdiction posture.** Local law overlays, sanctions/export control filters, and visibility suppression in sensitive contexts.\ 24.2.6 **Continuity & resilience.** Backup/restore, integrity monitoring, tamper detection, incident response, and recovery drills for registry primitives. *** #### 24.3 Member Registry (States, Standing, and Routing) 24.3.1 **Membership status taxonomy.** Active; Observer; Limited; Restricted; Suspended; Removed; Alumni; Read-Only.\ 24.3.2 **Member-in-Good-Standing.** MGS criteria, renewal clocks, compliance gates, and lapse/grace rules (recorded with effective dates).\ 24.3.3 **Primary affiliation routing.** Single anchor for rotation pools and capture resistance; switching rules with rate limits and audit trail.\ 24.3.4 **Roaming entitlements.** Observe/contribute/review permissions by status + PoC + handling eligibility; downgrade propagation rules.\ 24.3.5 **Lapse/reactivation.** Re-attestation, PoC refresh, security reset, and effective-date reinstatement by record.\ 24.3.6 **Scholarship/waiver markers.** Non-prestige, non-influence markers; privacy-preserving display defaults.\ 24.3.7 **Non-agency / non-employment marker.** Always-on registry marker for all members; non-waivable; displayed in public-safe form where feasible. *** #### 24.4 Identity and Attribution Surfaces 24.4.1 **Role markers ≠ identity.** Role markers are the default visible unit; identity exposure is optional except where lawful/handling requires.\ 24.4.2 **Pseudonym defaults.** Pseudonymous participation supported; verified identity is an optional lane with separate consent and handling rules.\ 24.4.3 **Attribution consent model.** Opt-in, scope-bounded, purpose-bounded, expiry-bound; revocable-by-record with distribution reconciliation where feasible.\ 24.4.4 **Identity unmasking criteria.** Lawful necessity / safety necessity only; two-person rule; logged access; minimum disclosure principle.\ 24.4.5 **Doxxing protections.** Emergency concealment protocol; takedown + suppression; safe contact routing; incident linkage to Part 18/22.\ 24.4.6 **Public official participation safety.** Ethics-safe attribution patterns; mandate-safe labeling; travel/gift/honoraria neutrality safeguards.\ 24.4.7 **Media quoting protocol.** Permissioned quoting; misquote response; corrections linkage; no implied endorsement language. *** #### 24.5 Role Registry (Privileges, Scope, Expiry, Revocation) 24.5.1 **Role taxonomy.** Member roles; contributor; reviewer/verifier/red-team; steward/maintainer; editor; program committee; integrity roles; cell/CERT roles.\ 24.5.2 **Minimum role-marker fields.** Authority basis; scope; duties; handling permissions; PoC prerequisites; start/end; expiry; renewal; revocation path.\ 24.5.3 **Least privilege + time-boxing.** Role markers expire-by-default; renewal requires recorded eligibility checks and recusal readiness.\ 24.5.4 **Rotation + cooling-off.** Capture resistance schedules for sensitive roles (review, safety gate, program selection, registry editing).\ 24.5.5 **Revocation propagation.** Cross-Guild restrictions, controlled-lane access removal, and badge/release privileges suspended as applicable.\ 24.5.6 **Conflicts/incompatibilities.** No self-review; separation-of-duties; integrity roles incompatible with sponsor-adjacent selection decisions.\ 24.5.7 **Role appeals/reinstatement.** Due process linkages; remediation markers; probationary reinstatement options. *** #### 24.6 Badge and Marking System 24.6.1 **Purpose and strict limits.** Badges are non-regulatory quality signals; never “certification,” “approval,” “compliance,” “audit opinion.”\ 24.6.2 **Badge classes.** Guild-Reviewed; Lab-Validated; Dataset-Ready; Benchmark-Ready; Release-Ready; Operator-Safe Pattern; Safety-Screened; Interoperability-Mapped; Deprecated/Superseded.\ 24.6.3 **Scope statements.** Mandatory “reviewed / not reviewed” fields; handling lane; evidence basis links; limitations and reliance bounds.\ 24.6.4 **Expiry/renewal/deprecation.** Expiry-by-design; renewal criteria; revalidation triggers; stale badge display rules.\ 24.6.5 **Revocation triggers.** Fraud, misconduct, material error, unsafe misuse risk, misrepresentation; public-safe notice requirements.\ 24.6.6 **Prohibited language + misuse controls.** Automated scanning, takedown workflow, sanctions linkage for repeated abuse.\ 24.6.7 **Portability rules.** No laundering across Guilds; equivalent-or-stronger handling; revocation propagation.\ 24.6.8 **Dispute and contestation lanes.** Minority reports preserved; badge holds and safety escalations time-boxed. *** #### 24.7 Artifact Registry (Outputs, Provenance, Corrections, Reliance Bounds) 24.7.1 **Artifact taxonomy.** Methods; datasets; benchmarks; ontologies; Proof Packs/AEP patterns; review reports; drill after-actions; summaries.\ 24.7.2 **Minimum artifact metadata.** Provenance; lineage; scope; limitations; uncertainty; reliance bounds; handling class; expiry; correction path.\ 24.7.3 **Versioning discipline.** No silent edits; diffs; supersession chains; current-version resolution rules.\ 24.7.4 **Dependency/citation graphs.** Explicit upstream/downstream; circular reliance detection; dependency risk flags.\ 24.7.5 **Reproducibility markers.** Replayability evidence, environment notes, hashes, replication logs (where applicable).\ 24.7.6 **Controlled/restricted artifacts.** Distribution logs; watermarking; expiry; access-logged appendices; declassification-by-abstraction only.\ 24.7.7 **Withdrawal/retraction/unsafe removal.** Stop-the-line removal protocol; public-safe explanation; preservation of record trail. *** #### 24.8 Corrections, Errata, and Supersession Register 24.8.1 **Correction clocks.** Severity tiers and target clocks (<4h, <72h, <30d, quarterly) with escalation triggers.\ 24.8.2 **Errata records.** What changed; why; impact; scope; effective date; reliance update; distribution reconciliation references.\ 24.8.3 **Supersession chains.** Canonical chain objects; “current” pointer logic; immutability of prior releases.\ 24.8.4 **Recall propagation.** Recipient notifications and distribution-log reconciliation; best-effort compliance logging.\ 24.8.5 **Misquote/misrepresentation linkage.** Correction records connected to comms integrity responses and takedown actions.\ 24.8.6 **Dissent preservation.** Minority reports retained and linked across corrections/supersessions.\ 24.8.7 **Public-safe correction summaries.** Default publication with limitations and non-endorsement blocks. *** #### 24.9 Sanctions, Restrictions, and Misrepresentation Register 24.9.1 **Sanctions taxonomy.** Warning → Limited → Restricted → Suspension → Removal; emergency interim measures time-boxed.\ 24.9.2 **Due process linkage.** Notice, minimum evidence basis, reason codes, appeal routes, expiry/review dates.\ 24.9.3 **Disclosure layering.** Public-safe outcome summaries by default; controlled details minimized and access-logged.\ 24.9.4 **Misrepresentation classes.** Unauthorized node/chapter claims; badge misuse; implied endorsements; delegated authority claims; impersonation.\ 24.9.5 **Emergency restrictions.** Safety-driven holds; mandatory expiry; post-hoc review and ratification.\ 24.9.6 **Reinstatement markers.** Training/attestation completion, probation windows, restored privileges by record.\ 24.9.7 **Protected reporting integration.** Anti-retaliation protections, anonymized reporting options, and non-contact constraints where needed. *** #### 24.10 Local Node Listings and Activation Status 24.10.1 **No implied nodes.** Default global-only posture; no local presence implied by membership alone.\ 24.10.2 **Activation prerequisites.** State Council record + mandate evidence; Host Institution capacity checks where applicable.\ 24.10.3 **Mandatory labels.** Activated / Global-only / Paused / De-recognized with effective dates and expiry.\ 24.10.4 **Scope/expiry/limits disclosures.** Local listing includes scope of permitted activity, handling posture, and non-authority disclaimer.\ 24.10.5 **Mandate withdrawal effects.** Automatic pause; listing update; privilege downgrades; reversion-to-global-only rules.\ 24.10.6 **Sensitive jurisdiction suppression.** Visibility suppression rules; safety-first exceptions; lawful constraints. *** #### 24.11 Search, Discovery, and Public-Facing Presentation Rules 24.11.1 **Public-safe indexing.** No targeting cues; no operational details; no controlled summaries leaking restricted specifics.\ 24.11.2 **Accessibility + multilingual posture.** Low-bandwidth pages, screen-reader compliance, structured summaries, localization options.\ 24.11.3 **Neutrality and non-endorsement.** Standard disclaimers embedded in all listings; no vendor/product promotion.\ 24.11.4 **Speaker/presenter listings.** Permissioned attribution; expiry-bound; role-marker option; doxxing safeguards.\ 24.11.5 **Evidence-room and convening listings.** Handling-aware; “no deal room / no procurement” notice; entry gates by PoC/standing.\ 24.11.6 **External linking policy.** No implied partnerships; explicit “reference only” disclaimers; anti-brand-laundering controls. *** #### 24.12 Auditability, Integrity Controls, and Security for Registry Operations 24.12.1 **Access control + logs.** RBAC, least privilege, audit trails (read/write/export), anomaly detection.\ 24.12.2 **Watermarking + leak response.** Per-recipient watermarking for controlled exports; leak triage and recall hooks.\ 24.12.3 **Schema change control.** Governance-critical fields are change-controlled by record with notice, contestation, and rollback.\ 24.12.4 **Completeness audits.** Reconciliation checks between records, badges, roles, sanctions, and corrections; mismatch locks where applicable.\ 24.12.5 **Backup/restore testing.** Regular restore drills, integrity validation, and continuity runbooks.\ 24.12.6 **Independent integrity review triggers.** Systemic anomalies, repeated failures, or capture indicators prompt independent review. *** #### 24.13 Privacy, Data Protection, Retention, and Deletion Rights 24.13.1 **No PII by default.** Minimization enforcement; purpose limitation; structured redaction/de-identification options.\ 24.13.2 **Retention schedules.** By registry type and handling class; survival obligations preserved; legal holds supported.\ 24.13.3 **Deletion requests.** De-identification and suppression pathways within record-integrity constraints; role-marker continuity preserved.\ 24.13.4 **Youth/vulnerable safeguards.** Enhanced minimization; restrictive defaults; special handling rules if participation permitted.\ 24.13.5 **Cross-border constraints.** Lawful basis for transfers; sanctions/export control gating; geo-suppression where required.\ 24.13.6 **Incident disclosure posture.** Record-valid member notifications; layered public-safe statements; controlled annexes as needed. *** #### 24.14 Transparency Minima and Annual Registry Reports 24.14.1 **Annual public-safe transparency pack.** Counts, states, trends, corrections performance, dispute throughput, and integrity posture.\ 24.14.2 **Controlled integrity pack.** Access-logged audit extracts, anomaly summaries, and remediation closure evidence.\ 24.14.3 **Sponsor concentration indicators.** Public-safe summary metrics; no narrative purchase; influence caps compliance signals.\ 24.14.4 **Corrections + disputes metrics.** Correction clocks performance, appeal volumes, outcomes distribution, and systemic learnings.\ 24.14.5 **Improvement roadmap.** Planned registry enhancements issued by record with contestation windows and effective dates. --- # 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/xxiv.-registry.md?ask= ``` 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.