[PROTOCOL]: Routing Family Conflict via the DNR Standard
> SYSTEM LOG INITIALIZED
> SUBJECT: INTERPERSONAL ROUTING AND CONFLICT RESOLUTION
> DEMOGRAPHIC FOCUS: 8–11 YEARS
Most modern parenting advice fails because it is entirely abstract. We tell our children to "be good" or "communicate better," but we rarely provide them with the mechanical routing instructions to actually execute those commands.
In systems engineering, ambiguity causes errors. If a protocol is not clearly defined, the system cannot process the request.
When an 8- to 11-year-old is experiencing an emotional meltdown, they do not need abstract philosophy. They need a rigid, predictable framework they can use to navigate the conflict. In the Mettamaker ecosystem, that framework is the DNR Protocol.
The DNR Standard: Decent, Nice, and Reasonable
DNR is the mechanical protocol executed within our offline hardware. It is a strictly secular, mechanical standard for interpersonal communication and problem-solving within a household.
Before an emotional spike can be processed and routed, it must pass through these three validation checks:
> Decent: Is the baseline behavior acceptable? Decency is the minimum viable product of human interaction. It means no physical harm, no name-calling, and basic respect for the environment. If the behavior is not decent, the system throws an immediate error and routing stops until decency is restored.
> Nice: Is there positive intent? Niceness is the UX (User Experience) of the interaction. It requires executing the communication with positive bandwidth and a collaborative tone. You can deliver a hard truth, but the delivery mechanism must remain nice.
> Reasonable: Does the proposed solution obey logical constraints? A request for unlimited screen time or staying up until midnight is not structurally sound. Reasonableness requires the child to look at the physical realities of a situation and propose a solution that respects the parameters of the household.
Offline Execution
You cannot effectively teach a communication protocol during an active emotional spike.
The foundation of this system is introduced when things are calm, primarily through our base documentation, Spark’s Big Debug. The 32-page manual gives children a visual and narrative understanding of how to "befriend a glitch" and establishes the core moral: Build Kind Systems.
But when a conflict inevitably happens, philosophy isn't enough. The child needs mechanical execution. That is when they transition to the Terminal Pad and the Quick Start Card. As they use the dot-grid wireframe to physically map an active glitch or capture a System Snapshot, they are required to filter their proposed solution or positive transmission through the rigid DNR checks.
By forcing the data offline and running it through a rigid, mechanical framework, we remove the ambiguity of family conflict. The DNR standard gives 8- to 11-year-olds the exact syntax they need to navigate their own friction and build baseline resilience.
> END OF LOG