Cross-Domain
Cross-Domain

The Residue Is Where the Power Is

Cross-Domain

The Residue Is Where the Power Is

Three brothers want a turn with their god. One servant has absorbed every task so completely that nobody can get near — not the brothers, and, the text says pointedly, not even the wife.
developing·spark··Aug 18, 2026

The Residue Is Where the Power Is

Three brothers want a turn with their god. One servant has absorbed every task so completely that nobody can get near — not the brothers, and, the text says pointedly, not even the wife.

So they build an instrument. A written roster of every service from waking to bed, allocated by preference, signed by Rāma, stamped with the royal seal, copies distributed. His name is not on it. That is the whole design.

Rāma reads it, notices the omission, works out exactly what it is for, and signs.

Then somebody adds, generously, that any service not on the list is still available — and Hanumān says: snapping the fingers when the Lord yawns is not on this roster.

He gets that signed and sealed too, at the same rank as the document written against him. And because there is no telling when a god might yawn, he now walks backward in front of Rāma with his fingers cocked, and eats left-handed to keep his right hand free.

The roster produced more of what it was built to reduce.


Here is the part worth keeping. Any enumeration prices what it lists and, by construction, creates an unpriced remainder. That is not a flaw in a particular schema — it is what enumeration is. And the remainder is where the leverage sits, because nobody negotiated over it.

The corpus's own XP economy has the same shape: eight qualitative measures declared primary, advancement gated entirely on what can be counted. Whoever finds the practice it forgot to count will win it, and on the scoreboard will appear to be doing nothing.

The second half is sharper and I have not seen it stated anywhere. Not all residue is equal. The item that matters is the one whose trigger cannot be scheduled — because availability at an unknown moment requires availability at every moment. A large allocated responsibility is bounded by its allocation. A small unschedulable one is unbounded.

So in any division of labour: the person holding the on-call scrap holds the calendar. Everyone else holds a slot.

And the defensive reading is the useful one. If someone cheerfully takes the trivial always-on item and leaves you the substantial scheduled ones, look again at what their item actually requires of them. They may have taken the only piece that cannot be covered, cannot be shared, and cannot be gone on leave from.

Which the Carit presents as the summit of devotion, and which — stripped of the god — is a job description nobody should accept.

Where This Could Go

  • A short piece on enumeration and its remainder, built on the roster and the XP economy together. The devotional example does the work the corporate one cannot, because nobody reads it defensively.
  • The unschedulable-trigger rule as a negotiation heuristic: in any scope discussion, price the random-trigger item higher than its size suggests.
  • And the honest counterweight: this is a technique for capturing a role, and the people it was used against had a legitimate grievance that the story never answers.

Connected Concepts

domainCross-Domain
developing
complexity
createdAug 18, 2026