Layer 4 — Structure (Domains)
0. Introduction
0.1 Purpose of the Domain Framework
The Domain Framework defines the systematic methodology by which institutional righteousness is structured, organized, and operationalized across various domains of human activity. While the Role Framework (4A) defines who acts righteously, the Domain Framework (4B) defines where righteousness is institutionalized — the systems, structures, and operational environments that enable and sustain righteous conduct.
A Domain is a distinct sphere of human activity, characterized by:
- Specific functions and purposes
- Unique risks and ethical challenges
- Specialized systems and processes
- Particular stakeholder relationships
0.2 Relationship to the 25 Core Institutional Systems
All Domains are built upon and must express the 25 Core Institutional Systems derived from the Institutional Righteousness Systems Map. These 25 systems represent the foundational infrastructure that every righteous institution must possess, regardless of its domain.
| Category | Core Systems |
|---|---|
| Governance & Ethical Direction | Board Oversight, Ethics Committees, Succession Planning |
| Transparency & Information Integrity | Disclosure Mechanisms, Whistleblower Protection, Records Management |
| Justice & Corrective Architecture | Bias Detection, Inclusion Systems, Structured Corrective Action |
| Ethical Risk & Procurement Control | Vendor Due Diligence, Duty Segregation, Authorization Governance |
| Culture, Safety & Motivation | Psychological Safety, Intrinsic Motivation Systems |
| Accountability, Compliance & Audit | Audit Independence, Compliance Management |
These 25 systems apply to all institutions universally. They are the baseline of institutional righteousness.
0.3 Relationship to Domain Extended Factors (B.3)
While the 25 Core Institutional Systems apply to all domains, certain domains require additional systems beyond the core set. These are defined as Domain Extended Factors in RSS 37004‑B.3.
| 25 Core Systems | Domain Extended Factors | |
|---|---|---|
| Applicability | All institutions | Specific domains only |
| Nature | Universal baseline | Domain-specific additions |
| Example | Whistleblower Protection | Anti-Doping System (Sports) |
| Example | Records Management | Patient Safety System (Healthcare) |
0.4 Relationship to the Seven‑Layer Architecture
This framework sits within Layer 4 (Structure) as the institutional counterpart to the Role Framework:
- Layer 3 (Alignment) ensures institutional alignment with righteous principles.
- This Framework (B.1) defines how domains are structured.
- RSS 37004‑B.2 (Domain Catalog) lists all recognized domains.
- RSS 37004‑B.3 (Domain Extended Factors) adds domain-specific systems.
- RSS 37004‑B.4.x (Domain Modules) provides comprehensive definitions for each domain.
1. Scope
This standard applies to:
- All institutions operating within the RSS ecosystem.
- The definition, documentation, and understanding of institutional domains.
- The identification of domain-specific risks, responsibilities, and system requirements.
- The development of domain-specific governance, compliance, and accountability frameworks.
- The assessment of institutional righteousness within specific domains.
2. Normative References
The following standards are indispensable for the application of this document:
- RSS 37001:2026 — Fundamentals Standard
- RSS 37002:2026 — Foundation Standard
- RSS 37003:2026 — Alignment Standard
- RSS 37004:2026 — Structure Standard
- RSS 37004‑A.1:2026 — Role Expression Framework
- RSS 37004‑B.2:2026 — Domain Catalog
- RSS 37004‑B.3:2026 — Domain Extended Factors
3. Terms and Definitions
For the purposes of this document, the following terms apply:
3.1 Domain — A distinct sphere of human activity, characterized by specific functions, risks, ethical challenges, and stakeholder relationships, requiring specialized institutional systems and structures.
3.2 Core Institutional System — One of the 25 foundational systems that every righteous institution must possess, regardless of domain.
3.3 Domain Extended Factor — A system or structure required only in specific domains, beyond the 25 Core Institutional Systems.
3.4 Domain Module — A comprehensive definition of a specific domain, including domain description, system mapping, extended factors, and conformance requirements.
3.5 Domain Mapping — The systematic process of associating each of the 25 Core Institutional Systems to the specific functions and risks of a given domain.
3.6 Domain Risk Profile — The unique set of ethical, operational, and compliance risks inherent to a specific domain.
4. Structure of This Standard
This standard contains four normative components:
- RSS 37004‑B.1.1 — Domain Architecture
- RSS 37004‑B.1.2 — Core System Mapping
- RSS 37004‑B.1.3 — Domain Risk Classification
- RSS 37004‑B.1.4 — Domain-Role Integration
5. RSS 37004‑B.1.1 — Domain Architecture
This section defines the mandatory architecture for structuring any institutional domain.
5.1 Domain Definition Requirements
Every domain shall be defined by:
- Domain Name and Description — Clear identification of the sphere of activity.
- Primary Functions — The core purposes and activities of the domain.
- Key Stakeholders — All parties affected by or involved in the domain.
- Risk Profile — The unique risks to righteousness in this domain.
- Regulatory/Professional Context — Relevant laws, standards, and ethical codes.
5.2 Domain Categorization
Domains shall be categorized according to their primary function:
| Category | Description | Examples |
|---|---|---|
| Public Service | Serving the public interest | Government, Judiciary, Law Enforcement |
| Health & Welfare | Protecting health and well-being | Healthcare, Insurance, Nonprofit |
| Education | Developing knowledge and character | Education, Training |
| Commerce | Producing and distributing goods/services | Finance, Corporate, Retail |
| Infrastructure | Building and maintaining systems | Transportation, Construction, Energy |
| Information | Producing and transmitting information | Media, Technology |
| Primary Production | Extracting and producing raw resources | Agriculture, Environment, Manufacturing |
| Leisure & Culture | Enriching human experience | Sports, Hospitality, Arts |
5.3 Domain System Architecture
Every domain shall be supported by systems that cover all six categories from the Institutional Righteousness Systems Map:
| System Category | Domain Application |
|---|---|
| Governance & Ethical Direction | How the domain ensures ethical oversight |
| Transparency & Information Integrity | How the domain ensures truth and disclosure |
| Justice & Corrective Architecture | How the domain ensures fairness and correction |
| Ethical Risk & Procurement Control | How the domain manages ethical risks |
| Culture, Safety & Motivation | How the domain fosters righteous culture |
| Accountability, Compliance & Audit | How the domain ensures verification |
6. RSS 37004‑B.1.2 — Core System Mapping
This section defines how the 25 Core Institutional Systems are mapped to each domain.
6.1 Comprehensive System Inventory
Every domain definition shall begin with a complete inventory of all 25 Core Institutional Systems. No system shall be omitted, though the implementation and emphasis of each system may vary by domain.
6.2 System Categorization by Domain Relevance
For each domain, systems shall be categorized into one of three tiers:
| Tier | Description |
|---|---|
| Primary Systems | Directly critical to the core functions of the domain. Failure constitutes fundamental institutional failure. |
| Secondary Systems | Support the primary functions and are relevant to overall institutional righteousness. |
| Contextual Systems | Always required but may be implemented with lower complexity depending on domain scale and risk. |
6.3 Domain-System Association Matrix
For every domain, the entity defining the domain shall identify which of the 25 systems are activated by the domain’s specific functions, risks, and stakeholder relationships.
7. RSS 37004‑B.1.3 — Domain Risk Classification
This section defines how domain-specific risks are identified and classified.
7.1 Risk Identification
Every domain shall identify its unique risks to righteousness, including:
| Risk Type | Description | Examples |
|---|---|---|
| Ethical Risks | Risks of moral failure | Corruption, fraud, abuse of power |
| Operational Risks | Risks of system failure | Safety failures, service failures |
| Relational Risks | Risks of relational harm | Exploitation, discrimination, neglect |
| Reputational Risks | Risks of trust erosion | Loss of public confidence, scandal |
| Regulatory Risks | Risks of legal violation | Non-compliance, liability |
7.2 Risk Severity Classification
Risks shall be classified by:
- Likelihood: Probability of occurrence
- Impact: Severity of consequences
- Detectability: Ease of detection
7.3 Risk Mitigation Requirements
For each identified risk, the domain definition shall specify:
- Which Core Systems address this risk
- Which Domain Extended Factors (if any) are required
- What controls and safeguards are necessary
8. RSS 37004‑B.1.4 — Domain-Role Integration
This section defines how Domains (4B) and Roles (4A) integrate.
8.1 Domain-Role Matrix
Every domain shall identify the roles (from 4A) that operate within it:
| Role Type | Domain Application |
|---|---|
| Universal Roles | All apply within every domain (Citizen, Employee, Supervisor, etc.) |
| Domain-Specific Roles | Defined in A.3 for each domain (Police Officer, Doctor, Teacher, etc.) |
8.2 Person-Institution Alignment
Institutional righteousness requires alignment between:
- Individual expression of the 30 Core People Factors (4A)
- Institutional expression of the 25 Core Systems + Domain Extended Factors (4B)
8.3 Mutual Accountability
Domains and Roles shall be accountable to each other:
- Domains provide the systems that enable righteous role performance.
- Roles provide the human agency that activates domain systems.
9. Conformance Requirements
To conform to RSS 37004‑B.1, an entity shall:
- Define its domain according to the Domain Architecture (Section 5).
- Map all 25 Core Institutional Systems to its domain (Section 6).
- Classify domain-specific risks and identify mitigation measures (Section 7).
- Integrate domain systems with applicable roles (Section 8).
- Document all domain definitions, mappings, and risk classifications.
- Review and update domain definitions regularly to maintain relevance.
10. Relationship to Other Layers and Standards
- RSS 37004‑A.1 (Role Expression Framework) defines the methodology for individual role expression.
- RSS 37004‑B.2 (Domain Catalog) lists all recognized domains.
- RSS 37004‑B.3 (Domain Extended Factors) adds domain-specific systems beyond the 25 core systems.
- RSS 37004‑B.4.x (Domain Modules) provides comprehensive definitions for each domain.
- Layer 5 (Process) will define operational processes for domains.
- Layer 6 (Assurance) will verify domain-level righteousness.
- Layer 7 (Restoration) will address domain-level failures.
End of RSS 37004‑B.1:2026