[ SYSTEM_DOCUMENTATION ] Processor Selection & Default Bias

SYSTEM LOG INITIALIZED
SUBJECT: PROCESSOR SELECTION & DEFAULT ROUTING BIAS
TARGET DEMOGRAPHIC: ALL NODES

The Mettamaker architecture runs on four primary processors: Spark, Patch, Amp, and Gyro. These are the hardware translations of the four Brahma Viharas (the "Four Faces of Love").

But having four processors introduces a new system vulnerability: Default Routing Bias.

When system load is high, human hardware instinctively routes data through its most familiar pathway. Some of us default to Patch, constantly trying to fix and heal, even when someone just wants to celebrate. Others default to Gyro, detaching into cold neutrality when a child actually needs active comfort.

To run an optimized family network, you must recognize your default bias and manually deploy the correct processor for the current system state. Here is the IF/THEN execution guide for processor selection.

1. SPARK (Metta / Goodwill)

The Function: The Baseline Generator.
The Trigger: IF the system is neutral or mildly positive, THEN deploy Spark.

Spark is your daily operating standard. It does not require a crisis or a celebration to activate. It is the active, unconditioned generation of friendliness. You use Spark to warm up the network before a heavy load is applied.

[+] Deployment Example: It is 7:00 AM. Your 11-year-old is quietly eating breakfast. There is no active friction. Instead of ignoring the neutral state, you deploy Spark: "May you have a solid day today." You are building emotional bandwidth while the system is calm.

2. PATCH (Karuna / Compassion)

The Function: The Emergency Hotfix.
The Trigger: IF the system detects active suffering or friction, THEN deploy Patch.

Patch is specific, targeted relief. It is the processor that activates when you encounter a corrupted sector. It requires you to acknowledge the pain without being absorbed into the error loop yourself.

[+] Deployment Example: Your 8-year-old is experiencing an active cognitive overload because a transition between activities failed. They are crying and shutting down. You do not use Spark (too vague) or Amp (mismatched). You deploy Patch: "May you find relief from this frustration. I am here." You are routing support directly to the crash.

3. AMP (Mudita / Appreciative Joy)

The Function: The Signal Booster.
The Trigger: IF another node achieves success or experiences joy, THEN deploy Amp.

Amp is the most underutilized processor in the network. Human hardware is wired for a negativity bias, meaning we often feel a subtle jealousy glitch when someone else wins. Amp overrides that glitch, allowing you to source joy from another person's success.

[+] Deployment Example: Your partner secures a massive win at work, or your child finally masters a complex physical skill. Instead of just saying "good job" (which is passive), you deploy Amp: "May your success continue to grow." You are actively linking your system's joy to their telemetry.

4. GYRO (Upekkha / Equanimity)

The Function: The Heavy Anchor.
The Trigger: IF the environment is chaotic and completely out of your control, THEN deploy Gyro.

Gyro is the ultimate defense mechanism against network collapse. Sometimes, Patch fails. You cannot fix the suffering. A massive tantrum is happening, or a flight is canceled, and no amount of active empathy is going to change the physical reality. Gyro is the protocol of radical acceptance.

[+] Deployment Example: A meltdown is occurring in a public space, and all attempts to debug the crash have failed. If you use Patch, you will drain your own battery trying to fix the unfixable. Instead, you deploy Gyro: "Things are exactly as they are right now, and I will remain stable." You hold the line, waiting for the analog speed of the physical world to bleed off the excess energy.

Review the Mechanics of Metta to see the foundational code behind these processors.

// END OF LOG