DNR Protocol

// BEGIN_FILE: DNR_PROTOCOL.TXT
// ROUTING_PATH: /PAGES/DNR-PROTOCOL
// PROTOCOL: STRICT_MONOSPACE
// SYSADMIN: JERRY_ESTEBAN
// STATUS: COMPILED & LOCKED

// ABSTRACT: PROTOCOL SPECIFICATION
In any network architecture, protocols exist to standardize communication and prevent fatal data collisions. When managing unstructured human emotional data, relying on abstract moral instructions—like "be good" or "be considerate"—causes runtime errors. Subjective commands require too much cognitive RAM to parse during an active amygdala hijack. The Mettamaker ecosystem translates emotional intelligence (EQ) into a clear, mechanical standard: the Decent, Nice, and Reasonable (DNR) protocol.

// LAYER 01: DECENT (THE PHYSICAL LAYER)
Decency is the system firewall. It is the absolute baseline of physical safety and structural respect. A process is Decent if it does not inflict unauthorized physical damage on the environment or another node.
[+] [ PASS ] Maintaining physical boundaries; respecting closed doors; removing oneself from a high-friction environment safely.
[+] [ FAIL ] Striking, breaking hardware, throwing objects, or physical intimidation. A failure at the Decent layer triggers an immediate SYSTEM.HALT. No other data can be processed until the physical layer is secured.

// LAYER 02: NICE (THE TRANSMISSION LAYER)
Nice dictates how data is transmitted across the network. You are not required to agree with the data being sent, and you are permitted to transmit frustration or disagreement, but the packet delivery must remain uncorrupted.
[+] [ PASS ] Using a regulated volume; stating a negative preference ("I do not want to do this"); executing a task without verbal retaliation.
[+] [ FAIL ] Packet storms (yelling); injecting malicious payloads (insults, name-calling); or aggressive sarcasm. If the transmission is corrupted, the receiving node will drop the packet and refuse the connection.

// LAYER 03: REASONABLE (THE LOGIC LAYER)
Reasonable evaluates the API compatibility between the trigger and the response. Does the executed behavior scale proportionally to the event?
[+] [ PASS ] Requesting a five-minute mechanical buffer before transitioning from a high-dopamine digital task to an analog physical task.
[+] [ FAIL ] Initiating a catastrophic, hour-long system meltdown because a specific dinner plate was unavailable. When a response is mathematically disproportionate to the input, it is not Reasonable. It indicates a severe bandwidth shortage requiring an immediate RAM clearance.

// EXECUTING THE DIAGNOSTIC (REACTIVE)
The DNR protocol cannot be enforced while a nervous system is actively crashing. Logic cannot overwrite an amygdala hijack. During an active spike, the operator must rely on the tactile friction of the physical [TERMINAL_PAD]—using off-cushion mindfulness to bleed off kinetic energy and ground the system. Only after the physical resistance of the paper has restored baseline processing speed can you run the diagnostic: Was the interaction Decent, Nice, and Reasonable? If not, where exactly did the packet drop?

// THE ACTIVE OUTPUT (PROACTIVE METTA TRANSMISSION)
DNR is not exclusively a passive defensive standard; it is the active output of a well-resourced system. You cannot demand consideration from an overloaded machine. By executing [TRANSMISSION_ROUTING]—our mechanical framework for off-cushion Metta (loving-kindness) meditation—to proactively generate and route positive bandwidth (goodwill and empathy) to internal or external nodes, real-world consideration emerges naturally, reinforcing the DNR baseline of the entire network before friction occurs.

// UNIVERSAL SYSTEM ARCHITECTURE
This standard is strictly bi-directional across any shared network, whether in a household or on a team. An adult screaming at a child—or a lead snapping at a peer—over a minor infraction is a failure of both the Nice (volume/transmission) and Reasonable (proportional logic) protocols. We all glitch. The DNR framework holds the adult architect to the exact same mechanical operating constraints as the developing builder.

// END OF FILE

SELECT NEXT COMMAND:
[LOAD: CRASH_ROUTING.TXT]
[CD .. RETURN TO MASTER DIRECTORY]