Proprietary & Illustrative Notice. This document is a publicly released framework reference for The Objective Ledger™ (TOL-OS). All named frameworks, formulas, and figures shown (including the Systemic Failure Extraction Cycle™, Anchor Tax™, and Convergence Protocol™) are original heuristic models, not validated scientific or statistical instruments. All numeric examples are illustrative sample placeholders for a blank worksheet template — they describe no real person, couple, or dispute. Nothing in this document scores, diagnoses, or renders a verdict on any individual; every metric evaluates a shared workload arrangement only, filled in voluntarily by both participants. This release is marked DRAFT — RESTRICTED pending final publication formatting and carries no legal, clinical, or evidentiary standing.
Section 01
The Five-Pillar Interdisciplinary Foundation
I
Forensic Bookkeeping
Double-entry visibility so invisible labor gets a line item both people can see.
II
Contract Theory
Named, revisable ownership via the RACI treaty — one Responsible, one Accountable, per task.
III
Polyvagal Science
Checking your own nervous-system state before negotiating a shared arrangement.
IV
Signal Theory
The RF Paradigm: retuning mismatched pace, register, and urgency before they squeal.
V
Deontological Ethics
Duty-based parity — tasks judged against agreed ownership, not shifting mood.
Section 02
The Systemic Failure Extraction Cycle™
A recurring structural pattern — not a description of any one person — showing how an unclaimed task compounds into resentment when ownership isn't named.
01Task goes unclaimed
→
02One partner absorbs it silently
→
03Absorption goes unbilled
→
04Anchor Tax™ accrues
→
05Next ask lands heavier
Step 05 feeds back into Step 01 for the next task, compounding over successive weeks.
Anchor Tax™ Breakdown
An illustrative model for the compounding cost of an unresolved task — not a measured constant. Treat the formula below as a discussion aid, not an audit result.
Time CostExtra minutes spent noticing, tracking, or re-explaining the gap each week.
Recall BurdenMental load of remembering what wasn't done, on top of what was.
Trust ErosionReduced confidence the task will be handled without a reminder next time.
Section 03
The Lemonade Stand Heuristic
Two people, one stand. Every hour that keeps the household running gets logged in the open, by both people, in the same units — not to keep score, but so nobody has to guess what the other one is carrying.
Full interactive version: spreadloveandacceptance.com — Chapter III / Tools
Section 04
Three Neutral Refusals — Tactical Scripts
Each follows the same shape: acknowledge → state actual capacity → offer a specific alternative.
Scenario
Script
Purpose
Asked to take on a task with no bandwidth left
“I hear that needs doing. I don't have the bandwidth for it today — can it wait until tomorrow, or is there someone else who could take it?”
Declines without denying the task matters
Asked to add a task on top of an already full day
“I can do that, but something else has to move if I do. Which one matters more this week?”
Surfaces trade-offs instead of silently overloading
Asked for an immediate commitment under time pressure
“I'm at capacity right now. I can commit to it by [specific time] if that works.”
Converts a vague ask into a concrete, keepable commitment
Section 05
The 30-Day Relational Statement
A mini-worksheet template. Log weekly hours for each column, then carry the Weekly Net into the Rolling Net. Figures below are illustrative sample data showing two possible outcomes of the same starting pattern — copy the blank structure for your own numbers.
Sample A — Resolved Pattern
Week
Col A hrs
Col B hrs
Weekly Net
Rolling Net
1
14
9
+5
+5
2
12
11
+1
+6
3
10
18
−8
−2
4
13
−28*
+41
+39
Net Rolling Balance: +39
*Week 4 reflects RACI reassignment mid-cycle — illustrative only
Sample B — Defaulted Pattern
Week
Col A hrs
Col B hrs
Weekly Net
Rolling Net
1
15
10
+5
+5
2
17
8
+9
+14
3
19
6
+13
+27
4
11
61*
−50
−23
Net Rolling Balance: −23 (Default)
*Week 4 reflects no RACI review held — illustrative only
Section 06
The Convergence Protocol™ — Bilateral Shield Summary
BILATERAL COMMITMENT
Both, or it doesn't function.
The Convergence Protocol only holds when both participants opt in equally — it isn't valid as a tool one partner uses to hold the other accountable alone. It is a summary of the shared commitments underlying every tool in this framework:
Both hours go in the same ledger, visible to both people
Every recurring task carries one named owner, reviewed weekly
Either person may use a neutral refusal without penalty
State is checked before negotiation, not used to end it
The statement is closed and re-opened together, on a shared cadence