Prompt Details
Model
(gemini-3.0-pro)
Token size
444
Example input
[Insert Action or Situation]: Terminating a Romantic Relationship
Example output
**DOCUMENT ID:** ISO-9999-7E2A91
**CLASSIFICATION:** RESTRICTED / SYSTEMIC OPERATIONS
**SUBJECT:** STANDARD OPERATING PROCEDURE FOR THE PERMANENT DISSOLUTION OF BILATERAL INTERPERSONAL CONTRACTS (ROMANTIC)
---
## SECTION 1.0: PURPOSE
The objective of this protocol is to provide a standardized, reproducible, and clinical framework for the termination of a bilateral interpersonal emotional/social contract (hereafter referred to as "The Relationship"). This procedure is designed to minimize systemic friction, reduce the duration of inefficient emotional cycles, and ensure the clean segregation of shared data and physical assets.
## SECTION 2.0: SCOPE
This document applies to all Human-Unit (HU) operations where a high-dependency social bond has been established. This protocol governs the transition from "Active/Committed" status to "Null/Terminated" status. It covers the preparatory phase, the execution of the termination event, and the subsequent resource segregation.
## SECTION 3.0: HAZARD IDENTIFICATION & SAFETY
### 3.1 Potential Hazards
* **3.1.1 Emotional Volatility (EV):** High risk of uncontrolled lacrimal secretion, elevated vocal decibels, and irrational logic loops from the Secondary Unit (SU).
* **3.1.2 Social Network Fragmentation:** Potential for systemic data corruption within shared social circles.
* **3.1.3 Physical Resource Retaliation:** Risk of damage to or unauthorized retention of physical assets (e.g., electronic devices, apparel, keys).
### 3.2 Mitigation & PPE (Personal Protective Equipment)
* **3.2.1 Neutral Affect:** Maintenance of a flat vocal tone and static facial geometry to prevent feedback loops.
* **3.2.2 Predetermined Exit Vector:** Identification of at least two egress points from the execution site.
* **3.2.3 Information Buffer:** Use of scripts to prevent deviation into subjective or sentimental sub-routines.
## SECTION 4.0: EXECUTION PROTOCOL (SOP)
### 4.1 Phase I: Pre-Termination Audit
1. **4.1.1 Inventory Assessment:** Identify all physical assets currently held by the Secondary Unit (SU).
2. **4.1.2 Digital Asset Migration:** Revoke shared access to streaming subscriptions, cloud storage, and financial accounts prior to the termination event to prevent unauthorized data spikes.
3. **4.1.3 Environment Selection:** Select a neutral, low-occupancy location that facilitates immediate egress.
### 4.2 Phase II: Termination Execution (The Event)
1. **4.2.1 Initialization:** State clearly that the purpose of the meeting is the formal dissolution of the interpersonal contract.
2. **4.2.2 Data Transmission:** Use the "Passive-Direct" method. State the conclusion (Termination) followed by the functional cause (Incompatibility of Operating Systems). Avoid subjective variables.
3. **4.2.3 Error Handling:** Should the SU initiate an "Emotional Rebuttal" sub-routine, the Primary Unit (PU) shall acknowledge the input with "Input received, but the conclusion remains unchanged." Do not engage in recursive debate.
4. **4.2.4 Final Handover:** Provide a brief timeline for the repatriation of physical assets.
### 4.3 Phase III: Resource Segregation & System Purge
1. **4.3.1 Communication Quarantine:** Implement a "No-Contact" firewall across all digital interfaces (Mobile, Social Media, Professional Networks).
2. **4.3.2 Asset Retrieval:** Utilize a third-party courier or neutral drop-off point to exchange physical items. Direct contact during asset transfer is non-compliant with ISO-9999 safety standards.
3. **4.3.3 Data Scrubbing:** Archive or delete digital media files (images, videos) associated with the SU to prevent "Sentimental Buffering" which reduces PU operational efficiency.
## SECTION 5.0: QUALITY ASSURANCE
### 5.1 Success Criteria
A termination is classified as "Successful" if the following conditions are met:
* **5.1.1** Bilateral contract status is recognized as "Null" by both units.
* **5.1.2** All physical and digital assets have been repatriated or discarded with zero legal escalations.
* **5.1.3** Communication frequency is maintained at 0.0 Hz for a minimum of 90 fiscal days.
* **5.1.4** PU operational efficiency returns to baseline levels without the use of "Coping Mechanism" sub-routines exceeding standard parameters.
---
**APPROVAL:** *Chief ISO Compliance Architect* *Date: 2026-01-14*
Would you like me to generate a **Logistical Asset Repatriation Schedule (LARS)** for the physical items involved in this dissolution?
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View SelectBy purchasing this prompt, you agree to our terms of service
GEMINI-3.0-PRO
It is designed to take any mundane, absurd, or complex human activity and reformat it into a rigorous International Standard Operating Procedure (SOP).
...more
Added over 1 month ago
