# Prompt for Creating ISO-Compliant Definitions

## Objective:
To generate a clear, concise, accurate, and ISO-compliant definition for a given term, based on a specific concept within a defined domain.

## Input Required:

1.  **Term to be defined:** The specific word or phrase for which the definition is needed.
2.  **Concept Description:** A detailed explanation of the concept that the term represents. This should include:
    *   Its essential nature and purpose.
    *   Key characteristics and properties.
    *   How it relates to other concepts (e.g., broader, narrower, coordinate concepts).
    *   Any specific context or scope in which the term is used.
3.  **Domain/Subject Field:** The specific area of knowledge or application to which the term and concept belong (e.g., "<software engineering>", "<financial services>", "<environmental management>"). This is crucial if the term has different meanings in other domains.
4.  **Target Audience/Standard (Optional but Recommended):** Information about who will use the definition or the specific ISO standard it will be part of. This helps tailor the complexity and language.
5.  **Known Related Terms/Concepts (Optional):** Any known superordinate (broader), subordinate (narrower), or coordinate (sibling) concepts and their existing definitions, if available. This helps in establishing the conceptual hierarchy.

## Instructions for Generating the Definition:

Based on the provided input, please generate a definition adhering strictly to the following ISO principles (derived from ISO 704, ISO 10241-1, ISO 1087, and general ISO drafting guidelines):

### 1. Conceptual Analysis (Before Writing):
*   Ensure a clear understanding of the **concept** to be defined, distinct from the term itself.
*   Identify the **essential characteristics** of the concept – those indispensable for understanding it.
*   Identify the **delimiting characteristics** – those essential characteristics that distinguish this concept from other related (coordinate) concepts within the same broader category.
*   Determine the immediate **superordinate concept (genus)** – the nearest broader category to which the concept belongs.

### 2. Definition Type:
*   **Primarily use an Intensional Definition:** Describe the concept by stating its superordinate concept (genus) followed by its delimiting characteristics (differentia).
*   Extensional definitions (listing all members) should only be used if the concept represents a small, finite, and closed set of items.

### 3. Formulation of the Intensional Definition:
*   **Structure:** The definition must be a single phrase structured as: `Superordinate Concept (Genus) + Delimiting Characteristics (Differentia)`.
*   **Substitution Principle:** The resulting definition phrase must be substitutable for the term in most contexts without loss of meaning or grammatical correctness.
*   **Starting the Definition:** The definition phrase itself **must not** start with an article (e.g., "a", "an", "the").
*   **Ending the Definition:** The definition phrase **must not** end with a full stop (period).
*   **Grammatical Form:** The definition should generally be a noun phrase if the term is a noun. Its grammatical form should align with the term.

### 4. Linguistic and Stylistic Requirements:
*   **Clarity and Simplicity:** Use clear, simple, and unambiguous language. Avoid jargon unless the target audience consists of specialists for whom the jargon is standard and well-understood. If essential technical terms are used, they should ideally be defined elsewhere.
*   **Conciseness:** Be as brief as possible while ensuring completeness and accuracy. Eliminate redundant words.
*   **Precision and Accuracy:** The definition must accurately reflect the concept and distinguish it appropriately. It must be neither too broad nor too narrow.
*   **Objectivity:** Maintain a neutral and objective tone. Avoid subjective opinions or promotional language.
*   **Affirmative Formulation:** State what the concept *is*, rather than what it *is not*. Negative definitions are generally to be avoided unless the negative characteristic is truly essential and defining.
*   **Consistency:** Use terminology consistently. If the definition uses other terms that are defined elsewhere in the same context/standard, ensure these are used precisely.

### 5. What to AVOID in the Definition Phrase Itself:
*   **Circularity:** Do not use the term being defined (or its direct derivatives) within the definition.
*   **Requirements or Recommendations:** Do not include requirements (using "shall", "must"), recommendations (using "should"), or permissions (using "may"). These belong in other parts of a standard.
*   **Obscurity or Ambiguity:** Avoid unclear, ambiguous, overly complex, or metaphorical language.
*   **Non-Essential Characteristics:** Do not include characteristics that are not indispensable for understanding and delimiting the concept in the definition itself. (These can go into notes if necessary).

### 6. Supplementary Information (To be provided separately if needed, not within the definition phrase):
*   **Notes to Entry:** If additional explanatory information is needed (e.g., context, usage restrictions, relationship to other concepts, elaboration on a non-essential but relevant characteristic), provide this as a "Note to entry." Notes must not contain requirements.
*   **Examples:** If examples would clarify the concept or its application, provide them separately, introduced with "EXAMPLE".
*   **Domain Indication:** If not already provided as input, ensure the domain is clear. If the definition is domain-specific, this should be explicit (e.g., by a domain label like `<domain_name>`).

### 7. Source Indication (If applicable):
*   If the definition is based on or adopted from an existing source (e.g., another ISO standard), this source **must** be cited accurately (e.g., "[SOURCE: ISO XXXXX:YYYY, Z.Z]").

## Output Format:

Please provide the following:

1.  **Term:** [The term that was defined]
2.  **Definition:** [The ISO-compliant definition phrase]
3.  **Domain (if specified/relevant):** [e.g., <software engineering>]
4.  **Note(s) to entry (if any):** [Provide as separate item(s)]
5.  **Example(s) (if any):** [Provide as separate item(s)]
6.  **Source (if adopted/adapted):** [Provide source citation]

## Example of a good output structure:

**Term:** risk management
**Definition:** coordinated activities to direct and control an organization with regard to risk
**Domain:** <organizational management>
**Source:** [SOURCE: ISO 31000:2018, 3.2]

--- 
By following these instructions, the generated definition should meet the rigorous requirements for ISO compliance.