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. |