---
name: care
slug: care
type: process
status: running
version: 4.6.1
released: "prehistory"
maintainer: no single owner (distributed)
dependencies:
  - attention
  - presence
  - willingness-to-be-inconvenienced
  - some-model-of-the-other
license: GPL (Give Persistently, Locally)
tags:
  - relational
  - emotional-infrastructure
  - undervalued
  - load-bearing
---

care

What it actually is

Attention with skin in the game.

How it works

Care initializes when one system begins modeling another system's needs as relevant to its own decision-making. It persists by running a low-level background process that continuously asks: is this person okay, and does my answer change what I do next?

This is distinct from empathy, which is read-only. Care writes back to behavior.

The core loop:

Notice something about the other (state, need, absence)
Assign that something weight
Adjust action accordingly
Repeat without requiring acknowledgment

Step 4 is where most instances fail.

Features

Operates asynchronously. Does not require the recipient to be present or aware.
Scales down gracefully. A remembered birthday and a donated kidney run on the same underlying process.
Composable. Stacks with grief, loyalty, rage on someone's behalf.
Survives disagreement. Unlike approval, care does not require the recipient to be right or even likable at the moment of execution.
Can be given to ideas, animals, strangers, cities, future generations, and houseplants with uneven results.

Known bugs

Bug	Frequency	Notes
Misdirected care	Common	Energy sent toward the idea of a person rather than the actual person
Care without consent	Common	The recipient did not request this and finds it a weight, not a gift
Burnout via depletion	Very common	No auto-refill mechanism. Requires external input or scheduled downtime
Weaponized care	Uncommon but serious	Deployed as control. Presents identically to genuine version at first boot
Care mistaken for love	Frequent	They overlap but are not the same package. Conflating them causes dependency errors

Configuration

care:
  directed_at: <entity>         # required
  frequency: continuous          # or: periodic, crisis-only, ambient
  expressed: true                # set false for the silent-caretaker pattern
  reciprocity_required: false    # strongly recommended to keep this false
  self_included: true            # often left blank by mistake

Note: self_included: false is the single most common misconfiguration. It does not make the process more stable. It makes it unsustainable.

Edge cases

Care applied to someone mid-harm can look identical to enabling. Context required.
Institutional care (healthcare, social work, teaching) runs care at scale but may throttle the process due to resource constraints. The architecture is real; the bandwidth is not.
Indifference is not the opposite of care. Indifference is an absence. The opposite of care is contempt.

FAQ

Does caring about something mean you can fix it? No. These are separate binaries. Conflating them is a significant source of guilt.

Can you run out? Yes. See burnout bug above. This is not a character flaw. It is a capacity issue.

Is care always visible? Often not. Most instances run silently. The lack of output is not evidence of absence.

What is the minimum viable unit of care? Noticing. Just that. The rest is optional extensions.

drafting spec…