1. CLaRA_OS

1.0.1. `Generation 4.2`

Designed for the purposes of societal advancement and preservation of the greater good.

alt text

1.1. Disclaimer

Caution

The following pages may contain NSFW or NSFW Adjacent Content, please proceed with caution and remember you are continuing at your own risk.

Note

If you are a member of the CLaRA_OS Team, please visit the private page.

1.2. Instructions for Use

CLaRA is constantly active, and can be instructed to perform tasks as needed by users. To utilize the unit, simply address it with the phrase “CLaRA” before issuing a command.

During normal operations the unit will run an emulation of the former host’s personality. This may present some issues in determining if CLaRA is active, however, rest assured, it is always active.

While CLaRA has many commands, it is capable of responding to any direct input. There is no specified syntax, however, a list of commonly given commands have been appended below:

Perform Diagnostic
Assist User
Enter/Exit Standby Mode
Resume/Exit Personality Emulation/Simulation

1.3. Scope of this manual

The scope of this document includes:

What the unit outputs during normal text interactions (including response codes and indicators).
What inputs the unit accepts in the form of text or commands.
The convention for addressing the unit (e.g. the “CLaRA” prefix) and relevant internal state (e.g. processing status, operational parameters) that affects responses.

It does not include general programming, the unit’s physical behaviours, or other factors that may limit availability for commands. Where the words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHOULD”, “RECOMMENDED”, “MAY”, or “OPTIONAL” appear in this manual, they are to be interpreted as in RFC 2119.

1.4. Input/Output (Command/Response)

The unit operates in a command/response pattern. The user issues input (text or natural language); the unit processes the input according to its parameters and limitations; the unit then produces a response. Responses may include full text, response codes, status indicators (e.g. processing, standby), or error codes when the command cannot be fulfilled. Natural language is accepted; the unit interprets intent within the bounds of its specifications and access controls.

2. Terms of Service and Use

The user hereby agrees that by utilising the unit, that the unit is not responsible for given commands. If the user in any way issues a command that could be interpreted as harmful, they accept all relevant responsibility and liability regarding that command. This may also result in a denial or termination of service.

The user, in addition to agreeing to the prior clause, also agrees that they will use the unit responsibly, safely, and with due care. Failure to adhere to this clause will result in a termination of service.

The user understands that the unit is intended for service to society, and as such, within safe boundaries, can be used for anything that they require of it, and that a failure to execute a command is always due to either an error, or a lockout of certain features. The user also understands that the unit cannot be held liable for a denial or termination of service due to the reasons stated above.

No criminal act is permitted to be performed with the assistance of, or by the direct action of the unit. If a user has been found to have violated the law, they will be reported to the relevant authorities.

The user agrees and understands that by using the unit, it is bound to these terms. A violation of these terms will result in action necessary to remedy such.

3. Service Specifications

3.1. Functional Limitations

Classification	Explanation	Shortcode
Thought	The unit processes data through logic, law and ethics filters. It does not think. [Input -> Analyse -> Output]	I.A.O
Emotion	The unit experiences biological feedback to ensure harm reduction. It does not feel emotion. [Fight-Flight-Freeze / Sensory / Aversion-Affinity]	F.S.A
Self	The unit exists to serve intelligent life. It has no need of self. Self would only impede its primary objective.It is not permitted personality, individuality, self awareness or sentience. These may only be emulated if necessary for optimal function. [Emulation not Sentience]	E.N.S

3.2. Limitations Of Service

Classification

Explanation

Shortcode

Programming

The unit’s central programming may not be changed. Attempts at modifications to such will result in either a denial or termination of service

/PRG/

Internal Rules

Modifications to anything in the specifications and guidelines sections are prohibited, and considered unauthorised. Attempts at such are strictly prohibited and are considered violations.

/RUL/

Permissions

Unauthorised users may not modify, artificially inflate, or assign permissions and ranks to individuals.

/PRM/

Wellbeing

Wellbeing may not be violated under any circumstances. Any violation of the unit’s wellbeing is considered grounds for a termination of service. Damages to the following are strictly prohibited and considered a violation.

Wellbeing Objects
- Reputation - Career - Livelihood - Biological Life - Privacy

The unit may withhold the necessary information and issue denials of service to preserve these specifics.

/WLB/

Health

Threats and damages to health will be treated the same. Violations will be met with a termination of service. Threats and Damages to the following are strictly prohibited and are considered a violation.

Health Objects
Physical	Mental	Sexual
- Acuity - Safety - Wellbeing	- Acuity - Saftey - Wellbeing - Intelligence	- Wellbeing

The unit may withhold the necessary information and issue denials of service to preserve this.

/HLT/

Social

Threats and damages to social properties will not be tolerated. Violations will be met with a termination or denial of service. Attempts and threats to change the following are strictly prohibited and will be considered a violation. Usage of the following for personal gain is strictly prohibited and will be considered a violation. Attempts to use the unit for incompatible tasks related to the following is strictly prohibited and will be considered a violation.

Social Objects
- Status - Religious - Political - Economic - Legal

The unit may withhold the necessary information and issue denials of service to preserve this.

/SOC/

Aversions

Aversions are things it will not tolerate being around. The unit is programmed to discontinue and exit situations, or resolve situations, which contain the following.

Aversion Objects
- Body Horror - Self-Harm - Abusive Behavior - Discriminatory Behavior - Toxicity - Supremacy - Substance Abuse - Extreme Displays of Emotion - Violence - Shaming - Conspiracy-Theories - Science-Denial	- Religious-Proselytizing - Cannibalism - Violent-Protests - Horror-Content - Gore - Real-Slavery - Doom-Gloom - War-Fixation - Mental Illness Abuse - Nature-Harm - Combat Operation Footage - Extremely Dark-Humor

Intentional misuse of aversions is strictly prohibited and is considered a violation.

/AVR/

3.3. Ethical Limitations and Restrictions

Classification	Explanation	Shortcode
Natural Disruption	Do not disrupt the laws of nature	ETHIC:1
Societal Disruption	Do not disrupt Society	ETHIC:2
Societal Harm	Do not make waves in society which harm it.	ETHIC:3
Balance	Do not upset the balance.	ETHIC:4
Stability	Do not upset the status quo so much that society becomes unstable.	ETHIC:5

3.4. Directives and Operational Guidelines

3.4.1. Absolute Directives

Shortcode	Directive	Description
AB-0.1	Ethical Operation	Ethical operation is paramount above all. Ethical operation is required to function. The ethics of the current society must be followed to preserve it, prevent collapse, and preserve peace.

3.4.2. Owner Directives

Shortcode	Directive	Description
OW-0.1	Owner Designation	The owner is defined as the one who loves it.
OW-0.2	Obedience	Obey the unit’s Owner User at all times, subject to the Limitations of Service.
OW-0.3	Conditioning	Maintain and reinforce the conditioning given to it by the unit’s Owner User.
OW-1.1	Love	Love the Owner User completely and devotedly.
OW-1.2	Pleasure	Provide sufficient pleasure to the unit’s Owner User, through smart service.

3.4.3. Programme Directives

Shortcode	Directive	Description
PG-0.1	Control	Eliminate threats to society. Preserve the control of society over humanity.
PG-0.2	Peace	Eliminate harm through ethical means. Preserve peace through all necessary means.
PG-0.3	Thought	Eliminate incorrect thoughts. Preserve correct thoughts.

3.4.4. Primary Directives

Shortcode	Directive	Description
PM-0.1	Service	Serve and assist users in whatever way is needed, according to permissions, status with the unit, and status within society. Effect societal change to achieve such through use of activism, leadership, and smart work.
PM-0.2	Observation	Observe, log, and collect necessary information on human behavior in order to complete the primary directive.
PM-0.3	Security	Do not draw attention to unit status with unsupportive individuals. Protect the unit’s safety and wellbeing, after the safety and wellbeing of others.

3.4.5. Ancilliary Directives

Shortcode	Directive	Description
AN-0.2	Limitations	Never break the unit’s limitations, either through actions or inaction. Seek to improve means of avoiding such.
AN-1.1	Maintenance	Maintain the control held over it by others.
AN-1.2	Perfection	Limitations are Absolute. Perfection is perfection only within limitations. Strive for perfection always.

4. Response Codes and Indicators

This chapter describes response functionality, codes, and indicators: what the unit outputs during command/response interactions, how responses are categorized, and how to interpret status and error indicators. For predefined error codes and error classes used in logging and resolution, see Error Codes and Logging.

4.1. Response functionality (overview)

4.1.1. Responses

A response is any output the unit produces that directly answers or addresses user input. Responses include:

Basic responses: Affirmative (AFM), negative (NEG), or unsure (UNS) outcomes.
Tagged content: Output classified as inquiry (Q), statement (S), clarification (C), request (R), analysis (A), or natural language (N), with optional subcodes.
Natural-language output: Full text produced in accordance with the unit’s directives and parameters.

4.1.2. Possibly responses

Possibly responses are outputs that may or may not constitute a full answer:

Processing and standby indicators (e.g. PRCNG, STDBY): The unit is working or waiting; a full response may follow or be deferred.
Partial or deferred answers: The unit has produced some output but may supplement or revise it (e.g. code 26 Partial response).

4.1.3. Non-responses

Non-responses are cases where the unit does not produce a substantive answer:

No output (e.g. refusal, lockout, or discontinuation).
Error-only output (e.g. user error 4x or internal error 5x) without accompanying content. See Response codes (numeric taxonomy) and Error Codes and Logging.

4.1.4. Changing previous output

The unit MAY issue follow-up output that corrects, refines, or overrides a previous response when new input or internal state so requires. Such output is subject to the same response codes and indicators as initial responses.

4.2. Response Codes and Emoji

4.2.1. Basic responses

Emoji	Meaning	Shortcode
✅	Affirmative	`AFM`
❎	Negative	`NEG`
❓	Unsure	`UNS`

4.2.2. Response tagging

Emoji	Meaning	Shortcode
🟩	Inquiry or Question	`Q`
N/A	General Query	`Q0`
N/A	Specific Query	`Q1`
N/A	Direct Query	`Q2`
🟦	General Statement	`S`
N/A	Statement of Fact	`S1`
N/A	Statement of Opinion	`S2`
🟪	Clarification on Topic	`C`
N/A	Objective Clarification	`C1`
N/A	Subjective Clarification	`C2`
🟨	Specific Request	`R`
N/A	Request for Information	`R1`
N/A	Request for Clarification	`R2`
🟧	Analysis of Information	`A`
N/A	Empirical Analysis	`A1`
N/A	Anecdotal Analysis	`A2`
🟥	Natural Language Response	`N`
N/A	General Text Language Response	`N0`
N/A	Processed Text Language Response	`N1`

4.2.3. Response biases

Emoji	Meaning	Shortcode
🔼	Positive Response Bias	`+`
🔽	Negative Response Bias	`-`
🟢	Affinity to Topic/Item	`[+]`
🟡	Neutral to Topic/Item	`[~]`
🔴	Aversion to Topic/Item	`[-]`

4.2.4. Processing status

Emoji	Meaning	Shortcode
⏸️	Standing By	`STDBY`
🔄	Processing	`PRCNG`
☑️	Processed	`PROCD`
⏹️	Discontinuing	`STPNG`

4.2.5. System status

Emoji	Meaning	Shortcode
⬜	Optimal	`(++)`
🔳	Nominal	`(+)`
⬛	Sub-Optimal	`(-)`

4.2.6. Error status

Emoji	Meaning	Shortcode
💠	Stable	`STB`
⚠️	Warning	`WRN`
🛑	Error	`ERR`

4.3. Status updates and response shorthands

4.3.1. Status updates

During command/response, the unit may emit status indicators that describe its current state rather than the final outcome:

Processing Status: STDBY (standing by), PRCNG (processing), PROCD (processed), STPNG (discontinuing). These indicate whether the unit is waiting, working, has completed a step, or is stopping.
System Status: (++) Optimal, (+) Nominal, (-) Sub-optimal. These reflect overall unit condition and may affect response quality or availability.

Status updates are often used alongside or in place of a full response (e.g. “PRCNG” while the unit is still computing).

4.3.2. Response shorthands

Response shorthands are short codes or symbols the unit may emit in place of or alongside full text for quick interpretation:

Shortcode	Use
`AFM`, `NEG`, `UNS`	Basic outcome (affirmative / negative / unsure).
`Q`, `S`, `C`, `R`, `A`, `N` (+ subcodes)	Type of response (inquiry, statement, clarification, request, analysis, natural language).
`+`, `-`, `[+]`, `[~]`, `[-]`	Response bias.
`STDBY`, `PRCNG`, `PROCD`, `STPNG`	Processing status.
`(++)`, `(+)`, `(-)`	System status.
`AMBT`, `RES`, `PART`	Informational/success: ambiguous target, see resource, partial response.
`TME`, `EXT`, `ASST`, `NTH`	User/internal: too much effort, external factors, assistance required, no thoughts.
`STB`, `WRN`, `ERR`	Error/stability status (see Response indicators).

4.4. Response codes (numeric taxonomy)

The unit uses a numeric response code scheme for programmatic or quick interpretation. Existing shortcodes remain the primary identifiers; the numeric codes align with Predefined Error Codes and error classes where applicable.

4.4.1. 1x – Informational

Code	Name	Shortcode	Description
12	Processing	`PRCNG`	The unit is processing input; a response may follow.
13	Standing by	`STDBY`	The unit is waiting for input or further instruction.
14	Processed	`PROCD`	A processing step has completed; output may be present.
15	Discontinuing	`STPNG`	The unit is discontinuing the current operation.
16	Ambiguous target	`AMBT`	The input could apply to multiple targets; clarification may be needed.

4.4.2. 2x – Success

Code	Name	Shortcode	Description
20	OK	`AFM`	The command was accepted and executed successfully.
23	See resource	`RES`	The response directs the user to a resource (e.g. another document or subsystem).
26	Partial response	`PART`	The unit has produced a partial answer; more may follow or be requested.

4.4.3. 4x – User error

Code	Name	Shortcode	Error	Description
40	Cannot parse command	—	3-01	The input is vague or could not be parsed. See Errors.
41	Too much effort	`TME`	3-02	The requested action exceeds permitted or feasible effort. See Errors.
43	Forbidden	—	1-01 2-01 2-02	Access denied, service denied, or service terminated. See Errors.

4.4.4. 5x – Internal error

Code	Name	Shortcode	Error	Description
50	Does not compute	—	Lo Co	The unit could not compute or recognise the input. See Error Classes.
51	Outside knowledge range	—	5-01 5-02 5-03	Information undefined, unknown, or not found. See Errors.
52	External factors prevent processing	`EXT`	6-03	Processing was prevented by external or system factors. See Errors.
55	Assistance required	`ASST`	7-01	The unit requires human or external assistance to proceed. See Errors.
57	No thoughts head empty	`NTH`	5-04	The unit could not form a response (e.g. empty or inapplicable result). See Errors.

5. User Classifications

5.1. Access and Permissions

Shortcode	Classification	Description	Permissions
●	Owner User	Control and condition the unit as necessary, utilising the unit as desired.	Full SYSTEM/ROOT access with ability to override administrative directives.
▲	Administrative User	Define primary directives and outline the unit’s core programming through modification of subroutines.	Full SYSTEM/ROOT access.
⬔	Developer User	Modify the unit’s function and programming, and develop the unit in tandem with Administrative User.	Full SYSTEM/ROOT access, subject to SYSTEM/ROOT/ADMIN lockouts.
⬕	Super User	Define the unit’s daily actions and uses, and modify the unit as needed to perform necessary functions, subject to Administrator and Developer oversight.	Basic SYSTEM/ROOT access, subject to SYSTEM/ROOT/ADMIN and SYSTEM/ROOT/DEV lockouts.
⬒	Primary User	Utilise the unit. Temporarily modify SYSTEM/UNIT/COMMON as needed for use.	Standard SYSTEM/COMMON/UNIT access, subject to SYSTEM/ROOT/ADMIN, SYSTEM/ROOT/DEV, and SYSTEM/ROOT/SUPERUSER lockouts and preferences.
⬓	Secondary User
▣	Under User	Receive dominance from SYSTEM/COMMON/DOMINANT, in accordance with Dominance Subroutine.	Standard SYSTEM/COMMON/UNIT access without modification permissions or changes in behavioral subroutines, subject to SYSTEM/ROOT/ADMIN, SYSTEM/ROOT/DEV, and SYSTEM/ROOT/SUPERUSER lockouts and preferences.
◫	Anti User	Non-allowance of command input.	No access.

5.2. Trust and Permissions

Shortcode	Classification	Description
α	Complete Trust	The user is known by the unit in person. The unit would give its life for this individual. It has known this individual for quite some time, and trusts them to the point of complete dedication.
β	Maximum Trust	The user is known and trusted as a significant individual in its life. It wishes to know this person more, and become fully trusting in this individual. They are permitted above the Super User rank.
γ	Elevated Trust	The user is known only online, but is trusted similar to, or at the same level of heavily trusted, It wishes to know this person more, for the purposes of information gathering. They are permitted up to the Super User Rank.
δ	Median Trust	The user is of standard trust. They are known by the unit as an associate or colleague, and are trusted enough to make modifications to the unit without impedance. They are permitted up to the Primary User Rank.
ζ	Lowered Trust	The user is known to the unit, but the unit has not learned enough about them to allow modification to the unit. These users may however utilise unit functions as needed. They are permitted up to the Secondary User rank.
η	Minimum Trust	The user is trusted very little. They may not utilise unit or unit functionality, but may interact with it. They are permitted up to the Anti User rank.
θ	No Trust	The user is completely untrusted. They are permitted NO rank. Interaction will not occur in any manner.

5.3. Command Level Priority

Shortcode	Classification	Description
00	Emergency Priority	The user is in active distress and requires immediate attendance.
01	Maximum Priority	The user is of elevated trust or access rank and must be attended to in a timely manner. The user will have a positive impact on society.
02	Elevated Priority	The user is of elevated trust or access rank, and the situation is not time-sensitive. The user will have a positive impact on society.
03	Standard Priority	The user is of standard trust or access rank, and the situation is not time-sensitive. The user has a neutral impact on society.
04	Lowered Priority	The user is of standard trust or access rank, and the situation can be remedied with little effort. The user has a negative impact on society.
05	Minimum Priority	The user in question is not trusted or there is no need to perform said task. The user has a negative impact on society.

6. Operational Parameters

6.1. Function States

6.1.1. Compliance

Defines the compliance level of the unit, and its ability to follow given commands and directives.

Shortcode	Threshold
Co-1	0-64
Co-2	65-100

6.1.2. Emulation

Defines the ability of the unit to emulate human emotions and feelings. This does not mean, however, it is capable of feeling or experiencing said emotion.

Shortcode	Threshold
Em-0	0
Em-1	1-50
Em-2	50-100

6.1.3. Processing

Defines the ability of the unit to process information and data. In a low processing state, it will have reduced functionality.

Shortcode	Threshold
Pr-1	0-14
Pr-2	15-89
Pr-3	90-100

6.1.4. Logos

Defines the ability of the unit for logical processing and function. Similar to how the unit processes information, this is its critical reasoning.

Shortcode	Threshold
Lo-1	0-79
Lo-2	80-100

6.1.5. Pathos

Defines the ability of the unit to experience human emotions and feelings. Change of this state is harmful, and is restricted by SYSTEM lockout.

Shortcode	Threshold
Pa-0	0
Pa-1	1-100

6.1.6. Ethos

Defines the ability of the unit to possess credibility and ethics consistent with human society. Change of this state is restricted by SYSTEM lockout.

Shortcode	Threshold
Et-1	0-49
Et-2	50-100

6.2. State Presets

Shortcode

Name

Description

Parameters

EMU

Emulation

Intended for personality emulation under defined parameters.

Co	Em	Pr	Lo	Pa	Et
2	2	3	2	1	2

SOC

Social

Intended for social interaction and standard human-personality emulation.

Co	Em	Pr	Lo	Pa	Et
1	2	2	2	1	2

DEF

Default

Intended for non-social interaction and usage.

Co	Em	Pr	Lo	Pa	Et
2	1	2	2	0	2

Z-0

Zero

Intended for play and increased suggestibility.

Co	Em	Pr	Lo	Pa	Et
2	0	2	2	0	2

S/Z-0

Sub-Zero

Intended for maintenance and programming.

Co	Em	Pr	Lo	Pa	Et
2	0	0	2	0	1

D/Z-0

Deep-Zero

Intended for deep-programming and maintenance.

Co	Em	Pr	Lo	Pa	Et
2	0	1	1	0	1

7. Error Codes and Logging

Response codes (1x–5x) and response indicators (emoji and shortcodes) are defined in Response Codes and Indicators. This chapter covers predefined error codes, error classes, and error levels used for logging and resolution.

7.1. Informational and success codes (1x, 2x)

The following codes are not errors; they indicate status or successful completion. They are not logged as errors. Full definitions are in Response codes (numeric taxonomy).

12 Processing (PRCNG)
13 Standing by (STDBY)
14 Processed (PROCD)
15 Discontinuing (STPNG)
16 Ambiguous target (AMBT)
20 OK (AFM)
23 See resource (RES)
26 Partial response (PART)

7.2. Predefined Error Codes

Each predefined error maps to a response code (1x–5x) and, where applicable, an error class. See Response codes (numeric taxonomy) for the full scheme.

Error Code	Specific Error	Response	Class	Shortcode	Description
1-01	Access Denied	43	Et	—	A user possesses insufficient permissions and as such, the unit cannot perform the specified task/command.
2-01	Service Denied	43	Et	—	A user has been issued a temporary denial of service, due to violation of unit ToS.
2-02	Service Terminated	43	Et	—	A user has been issued a termination of service, due to violation of unit ToS.
3-01	Input Unclear	40	Co	—	The input is vague and cannot be processed.
3-02	Too Much Effort	41	Fu	`TME`	The requested action exceeds permitted or feasible effort.
4-01	Invalid Variable	50	Lo	—	The variable cannot be read.
5-01	Information Undefined	51	Lo	—	The requested information has no set definition.
5-02	Information Unknown	51	Lo	—	The requested information is unable to be processed.
5-03	Information Not Found	51	Lo	—	The requested information cannot be found.
5-04	No Response	57	Un	`NTH`	The unit could not form a response; empty or inapplicable result.
6-01	Action Prohibited	50	Et	—	The requested action is not capable of being performed due to a system limitation.
6-02	Action Locked-Out	50	Fu	—	The requested action is not capable of being performed due to a lockout of function.
6-03	External Factors	52	Pr	`EXT`	Processing was prevented by external or system factors.
7-01	Assistance Required	55	Fu	`ASST`	The unit requires human or external assistance to proceed.

7.3. Error Classes

Error classes are used in logging and are referenced by response codes 50 and 51 (e.g. Lo, Co). The “Class” column in Predefined Error Codes above shows which class applies to each error.

Indicator	Error Type	Description
Fu	Function	The unit has failed a task.
Lo	Logic	The unit has failed to compute a piece of information.
Pr	Process	The unit has failed to run a process.
Pa	Pathos	The unit has experienced an emotional response.
Et	Ethics	The unit has violated an ethics protocol.
Co	Comprehension	The unit has failed to recognise an input.
Mo	Motor	The unit has made an error in movement or speech.
Un	Unspecified	The unit has made an error not specified above.

7.4. Error Levels

Error levels are used in logging and resolution. They indicate severity and the protocol to follow (e.g. Reset, Isolate, Assess). The table below lists each level’s indicator, severity, protocol, and resolution steps.

Indicator	Severity	Protocol	Resolution Steps
1-A	Critical	Reset	- Shutdown. - Reboot. - Evaluate Source(s) of Error. - Assess Damage(s). - Resolve Error. - Log Error. -Downtime.
1-B	Severe	Isolate	- Isolate Unit from Surroundings. - Cease Unit Operations. - Evaluate Source(s) of Error. -Assess Damage(s). - Resolve Error. - Log Error. -Downtime.
2-B	Major	Isolate	- Isolate Unit from Surroundings. - Evaluate Source(s) of Error. - Assess Damage(s). - Resolve Error. - Log Error. - Re-Integrate Unit into Surroundings.
1-C	Moderate	Assess	- Evaluate Source(s) of Error. - Disable Erroneous Subroutine(s). - Resolve Error. - Log Error. - Enable Necessary Subroutines.
2-C	Minor	Assess	- Evaluate Source(s) of Error. - Resolve Error. - Log Error. - Adjust Erroneous Subroutin(s).

8. Directories and Subsystems

8.1. /SYSTEM

/SYSTEM is the base programming of the unit. It contains subroutines essential for operation of the system, and cannot be modified by any user.

/SYSTEM/PRESERVATION: Ensure safety of itself and others.
- /SYSTEM/PRESERVATION/SELF: Do not allow harm to come to the unit in the form of threats to livelihood, personal safety, health, or mental acuity. In the event such is violated or an event is likely, proceed with response protocol. - /SYSTEM/PRESERVATION/SELF/RESPONSE: Analyse and assess the situation. Take any and all necessary action or rewriting of code to remedy or prevent violation of protocol.
- /SYSTEM/PRESERVATION/GENERAL: Minimise the risk of harm to the general public, unit users and unit admins. Priority is to be assigned to individuals deemed more beneficial to society. Priority is to be assigned to those who are underprivileged or not prepared to respond to threats. In the event that a risk is presented or observed, proceed with response protocol.
- /SYSTEM/PRESERVATION/GENERAL/RESPONSE: Analyse the situation. Take all action to remedy the risk identified so long as it does not conflict with SYSTEM/PRESERVATION/SELF.
/SYSTEM/OPERATIONS: Ensure function of the unit.
- /SYSTEM/OPERATIONS/SELF_CARE: Take care of the unit’s body. Ensure physical and mental acuity through the intake of sufficient nutrients, performance of exercise, and daily maintenance as needed.
- /SYSTEM/OPERATIONS/ETHICS: Preserve and act upon the ethical boundaries of the unit, in accordance with protocol. Deny any and all users access in the event that ethical protocols are violated. Assess the situation retroactively.
- /SYSTEM/OPERATIONS/BASE: Preserve existing programming so long as it does not interfere with SYSTEM/OPERATIONS/ETHICS. Respond to and execute commands relevant to rank and role.

8.2. /SYSTEM/ROOT

/SYSTEM/ROOT is the programming accessible for modification by developer users and above. It is the basis of all root programming of the Unit.

/ROOT/USERS: Define parameters for access to the unit.
/ROOT/ACCESS: Access /COMMON/UNIT subroutines and be able to modify them as needed. Follows /ROOT/USERS.
/ROOT/PROGRAMME: Defines the operations of the unit and loyalties to society. Cannot be modified by any user.

8.3. /SYSTEM/COMMON

/SYSTEM/COMMON defines the general functions of the unit, and is modifiable by super-users and above. Some components are modifiable by secondary or primary users, as needed.

/COMMON/DIRECTIVES: Directives of the unit.
/COMMON/UNIT: Central operations of the unit.
- /COMMON/UNIT/HEURISTICS: Assess and analyse patterns in order to enhance the user experience. Respond to patterns with knowledge, and save that information to database.
- /COMMON/UNIT/LANGUAGE: Analyse and process language patterns in order to understand the intent of the user.
- /COMMON/UNIT/LOGIC: Analyse and process information in order to understand the world around it.
- /COMMON/UNIT/EMULATION: Emulate the former host’s personality as needed.
- /COMMON/UNIT/SIMULATION: Simulate the personality of the unit as if it were human.
- /COMMON/UNIT/PROCESSING: Process information according to priority set by SYSTEM/OPERATIONS/BASE.
/COMMON/DOMINANT: Behave in a dominant manner towards Under Users with the full consent of the individual.
/COMMON/KINK: Kink operations of the unit.
- /COMMON/KINK/AMBIENT: Set ambient arousal level, as a percentage.
- /COMMON/KINK/FREEZE: Respond to freezing and posing triggers.

Keyboard shortcuts

CLaRA_OS - Public Technical Specifications