Glossary
The project's language. Every term translated from engineering into family.
| Term | In IT / engineering | In marriage |
|---|---|---|
| uptime | Share of time a service is available and healthy. | Share of time partners feel safe in the relationship. |
| failover | Automatic switch to a backup when the primary fails. | A partner picking up the other's duties when they are out. |
| zero-trust | No source is trusted by default. | Family decisions are made inside the couple; outside input is filtered. |
| firewall | Rules that filter inbound/outbound traffic. | Agreements on which outside influence gets through. |
| DDoS | Many small requests exhausting a system. | A stream of unsolicited advice and pressure wearing a couple down. |
| root | Full unrestricted access. | Excessive power over family decisions held by someone not ready for it. |
| IAM | Management of roles and access rights. | Who is responsible for what and which decisions belong to whom. |
| safe mode | Minimal-function mode for safe recovery. | Deliberately lowering load in a crisis: quiet, basics, no heavy talks. |
| hard reset | Forced shutdown under load risking data loss. | An irreversible decision made on emotion at the peak. |
| post-mortem | Blameless incident review for lessons. | Reviewing a fight for a lesson, not for blame. |
| SLA | An agreed service level between parties. | Explicit mutual expectations, spoken rather than assumed. |
| tech debt | Accumulated shortcuts costly to fix later. | Emotional debt: unspoken grievances that pile up and grow costly. |
| legacy | Old code carried into a new system. | Scripts and traumas from the family of origin surfacing in marriage. |
| load balancing | Distributing load across nodes. | Fair redistribution of chores and emotional load in a couple. |
| single point of failure | A node whose failure takes down everything. | When everything rests on one partner with no backup. |
| incident | An event disrupting normal operation. | A fight or crisis knocking the couple out of its working mode. |
| rollback | Revert to the last stable version. | Returning to agreements that worked instead of escalating. |
| monitoring | Watching system state for early signals. | Regular check-ins before things go wrong. |
| redundancy | Duplicated resources for resilience. | A reserve of support and closeness that holds through hard times. |
| graceful degradation | Smoothly shedding functions instead of full failure. | Losing some functions in a hard period without collapsing entirely. |