# Tracking URL: https://mechanisticmindset.com/wiki/tracking Tags: system-architecture, practical-application, probability-distributions, observer-stance # Tracking #system-architecture #practical-application #probability-distributions #observer-stance ## What Tracking Really Is “I've been going to the gym regularly” and “I went 18 of the last 30 days” are different kinds of information. The first is an impression. The second is a record you can compare with another month or with the conditions under which you went. Tracking can be understood as measuring the behavior a system produces. In this framing, the day's action is an output, and repeated observations reveal the probability distribution behind it. The question changes from “What did I choose?” to “What did the current arrangement produce today, and how is that pattern changing?” A log can still help you remember individual events. Its further value is to show what your routines, environment, energy, and competing activities produce together. A thermometer records a temperature without treating it as the weather's decision. Similarly, tracking records behavior so that its underlying distribution becomes visible. ## Each Day as a Sample Before this shift, tracking seemed like a way to remember many conscious choices. The new framing treats each instance as a sample of how often the behavior happens under the current conditions. It has you observe what the system produces instead of judging each day's output as a separate choice. ### From Microstates to Macrostates Suppose the first three entries are gym, gym, no gym. Read as choices, they become two successes and one failure in a moral record. Read as samples, all three contribute to the same question: what distribution is the current arrangement producing? The individual entries are microstates. Their pattern across days reveals the macrostate and how it changes over time. A skipped day remains useful because it is part of the output being measured. ### The Architecture Determines The Distribution In Week 1, attendance is 1–2 of 7 days. Activation cost is high, competing scripts remain available, and no routine has been cached. In Week 18, attendance is 6–7 days. The 30x30 routine is installed, the activation cost is low, and a bridge sequence and Julius forcing function support the transition. The change is in those conditions rather than daily willpower or discipline. Gym has become the highest-probability behavior from the relevant state. > > This reframe emerged from Will's 30x30 gym tracking experience. > ## Why You Cannot Trust Your Model Subjective experience often gives an unreliable account of patterns across time. The problem is not that today's experience is absent, but that it does not supply an accurate aggregate of the preceding days. ### 1. Memory Cannot Aggregate Samples Into Distributions Will found that memory failed to recall frequencies over 30 days, detect gradual shifts, combine dozens of observations, and distinguish a pattern from noise. “I've been going to gym regularly” felt like about seven days in ten, while the log showed 18/30, or 0.6. “I worked most days this month” felt like about six days in ten; the record showed 6/30, or 0.2—a threefold difference. Memory favors recent events, confirms existing beliefs, and varies with mood. In both of Will's cases the estimate ran above the record, a little for the gym and threefold for work. A record is how to find out whether your own estimates do the same. ### 2. How Often You Act Is Not Visible on Any One Day State machines, activation costs, cached routines, and competing scripts generate the distribution, but the distribution cannot be inspected directly. On a given day, you can observe only gym=1 or gym=0 and the feeling that you do or do not want to go. That feeling seems like the source of the decision. In this account, it is the experience of the distribution's output on this occasion. After 30 observations, you can infer a rate from the count: “26 gym days of 30 this month.” You can then install a bridge and measure again, to see whether the next month's count is higher. Behavior supplies the visible evidence about a hidden system. ### 3. The Subjective Experience of "Choosing" Obscures The System The useful model is how often the gym happens given the current state, the architecture, the energy level and the competing scripts. Deliberation is real as an experience; the model treats the felt choice as one more output of those conditions. The observer and the system are the same physical entity. “Observer” names the consciousness that experiences deliberation and sees outputs. “System” names the states, costs, and routines that produce the distribution. The separation allows the observer to investigate the conditions instead of treating itself as the direct source of each output. ## Tracking as Measurement Instrument Like `console.log()` during debugging, tracking exposes state that would otherwise remain hidden. A series of records does more than show individual values: it makes the distribution and its changes available for comparison. ### Recording Temperature vs Measuring Climate A record used only as a reminder looks like this: ``` "Today was 72°F. Let me write that down so I remember." Focus: What was the specific value today? Purpose: Memory of individual instances ``` The same record used to understand a changing system looks like this: ``` "Today's reading: 72°F. Current 30-day average: 68°F, up from 62°F last month." Focus: What distribution am I observing? How is it changing? Purpose: Understanding the system that generates temperatures ``` Writing down the number is unchanged. What changes is the question the accumulated numbers answer. ### What Tracking Actually Does Without records, “I feel like I'm not making progress” and “I think I'm getting worse” combine recent memories with the present mood. A log can instead show 18 workdays this month versus 12 last month, a rise from four days in ten to six in ten. It can show wake-time variance falling from ±45 minutes in Week 1 to ±12 in Week 3, or sleep quality correlating 0.87 with the previous day's exercise. “What does the log show?” is a constant-time lookup of a record rather than a reconstruction from memory. It gives reality a veto over the story. “Am I disciplined?” has no observable answer; “How many times did the predetermined sequence execute in the last 30 days?” does. ## What You're Actually Measuring The useful measurements are the conditions you can change and the outputs they produce. Recording everything adds work without necessarily helping you decide what to alter. ### Architectural Variables (What Changes How Often) Temporal inputs include wake time, meal timing, work start, and bedtime. Environmental inputs include phone location, gym-bag placement, and workspace setup. Energy-related inputs include sleep quality, exercise timing, and medication compliance. State-related inputs include morning rituals, launch sequences, and context switches. Tracking these alongside behavior reveals which conditions change how often the desired behavior happens. In a 30-day sleep/work comparison, work happened on three days in four when sleep quality was above 8, and on one day in four when it was below 6. The architectural conclusion was that sleep constrained the work distribution. ### Behavioral Outputs (What the Arrangement Produces) Outputs can be binary, such as gym attendance, a work session, or meditation. They can be continuous measures such as sleep hours, work hours, or energy on a 1–10 scale; discrete counts such as tasks, meals, and interruptions; or quality assessments such as sleep quality on a 1–10 scale, focus, and mood. Gym attendance was tracked for 21 weeks. The recorded windows were: Weeks 1–7 show 9/49 days, about 0.18; Weeks 8–14 show 32/49, or 0.65; Weeks 15–21 show 46/49, or 0.94. With the 30x30 routine installed, the share of days rose from 0.18 to 0.94. ### The Correlation Game Thirty-plus days of inputs and outputs let you compare exercise timing with good sleep, meal composition with afternoon productivity, wake-time consistency with work output, and bedtime screen use with next-day focus. The purpose is N=1 empirical debugging, not a population study. You are looking for conditions that shift your own behavior in the desired direction. ### Starting Point: Your First Tracking System During the first week, a whiteboard or simple spreadsheet can hold 1–2 inputs—sleep time and wake time—and 1–2 outputs—gym attendance and whether a work session happened. The initial task is to make daily logging routine; analysis comes later. After 30 consistent days, there is enough data to start looking for correlations and designing interventions. ## Practical Implementation ### The Whiteboard Method A digital record must be opened, queried, and analyzed, creating [activation costs](/wiki/activation-energy) for both logging and review. A wall-mounted whiteboard is encountered passively, perhaps 20 times a day. Marking an X takes almost no effort, and the accumulating pattern remains visible without opening anything. ``` DECEMBER 2024 Gym: X X _ X X X _ X X X X X X _ X X [13/16] Work: X X X _ X X X X _ X X X X X X _ [13/16] No AM: X X X X X X X X X X X X X X X X [16/16] ``` On December 16, you see the gym on 13 of 16 days, work on 13 of 16, and no morning food on all 16. The gym gap on day 14 raises a question; the work gap on day 9 suggests checking for a gym correlation. The no-morning-food row indicates perfect adherence and a working intervention. Repeated exposure makes those patterns salient without a separate analysis session. ### Granularity: Resolution for Distribution Measurement “Productive today: yes/no” is too coarse to distinguish a two-hour workday from an eight-hour one. Recording “9:14 AM - opened editor, 9:17 AM - wrote 47 words...” creates so much overhead and noise that the system becomes unsustainable. Binary entries suit execution habits. Scales of 1–10 suit subjective quality, energy, and mood. Duration measurements such as 6.5 hours preserve the amount of work. Counts such as 3 workouts or 1500 words reveal rates. The useful resolution shows the distribution's shape without making the act of recording it too expensive. ### Thirty Days of Samples [Signal boosting](/wiki/signal-boosting) describes how accumulated samples come to separate a pattern from noise, and the practice is to collect thirty days of them before drawing conclusions. Five samples are insufficient; apparent patterns that early may be random fluctuations. Days 1–7 establish a high-variance baseline. Days 8–14 may reveal an initial rough estimate. Days 15–21 make the pattern clearer and the estimate firmer. Days 22–30 allow intervention-related shifts to be identified. After 30 days there is a baseline for comparison, and a strong correlation or a large intervention effect stands out from the day-to-day noise. As in A/B testing, the sample size must support distinguishing a changed distribution from noise. ### Tracking as Distribution-Awareness Device Tracking also changes what it measures. Going to the gym and marking an X is a small reward, and it makes going tomorrow more likely. Seeing a gap after skipping is aversive and also raises the next day's chances through the desire to close it. A visible streak reinforces itself, so continuing a streak is far more likely than starting fresh. The anticipated X increases the [expected value](/wiki/expected-value) of going by adding immediate visual feedback. This is an intervention, not a defect in the measurement. The purpose is to produce a favorable distribution, not to observe behavior untouched by the act of recording it. ## Connection to Probability Distributions ### Tracking Reveals Distribution Shifts Over Time An individual day supplies a sample; the pattern across days reveals the distribution. The comparison with probability stops at stability. A coin's chance of heads stays put, while the rate a stretch of tracking reveals belongs to the arrangement in place during it, and it moves when that arrangement changes. Will's gym record shows the following progression: | Time Period | Samples | Frequency | Architecture State | |-------------|---------|-----------|-------------------| | Week 1 | 7 days | 1/7 = 0.14 | High activation cost, no cache, competing scripts | | Week 5 | 7 days | 5/7 = 0.71 | Cost decreasing, cache forming, fewer competitions | | Week 10 | 7 days | 6/7 = 0.86 | Low cost, strong cache, gym is default | | Week 16 | 7 days | 7/7 = 1.00 | Barely any cost; almost no deliberation | Attendance moved from 1 of 7 days to 7 of 7 as repetition lowered activation cost, a routine became cached, and competing scripts disappeared. Each day contributed evidence about the configuration in place at that time. ### Tracking Makes Distribution Changes Observable “Gym feels easier” becomes a quantified change from 1/7 in Week 1 to 7/7 in Week 16, or +0.86. That comparison provides a way to evaluate an intervention. If the count does not rise, the change is not working and another point of intervention is needed. If it rises, the change is effective and can be continued while watching for a plateau. ### Each Action Changes the Odds of the Next [Probability space bending](/wiki/probability-space-bending) explains why consecutive observations are not independent. An action changes the probability of later actions: ``` Clean eating streak (5 days): Day 1-5: All clean meals tracked Day 6: A clean meal is likely (streak momentum) Tracked outcome: Clean meal (sampled while the streak holds) Break pattern (1 cheat meal): Day 6: Cheat meal tracked Day 7: A clean meal is less likely (momentum lost, cascade activated) Tracked outcome: Another cheat (sampled after the break) ``` Momentum, cascades, identity priming, and depletion connect one sample to the next. Tracking exposes these [probability dynamics](/wiki/probability-space-bending), including the need for an intervention when one break begins a downward sequence. ## The Observer vs The System The distinction connects tracking to [superconsciousness](/wiki/superconsciousness): the observer needs measurements to investigate the system whose states it experiences. ### The Observer's Part and the System's Part The observer experiences “Should I go to gym?”, records gym=1, marks the whiteboard, infers a rate of 26 days in 30, and chooses an intervention. The system occupies a tired or energized state, executes morning_routine → gym or couch → phone → doom_scroll, and produces the next sample. A new bridge changes the conditions from which it generates that sample. In this framing, consciousness cannot directly force the output. It can observe, infer the state, modify the arrangement, and measure again. Installing a bridge, removing a phone, or adding Julius as a forcing function changes the system rather than treating the observer as a direct input source. This is why the model suggests “just try harder” often fails. ### Tracking as The Measurement Interface The observer cannot directly read how often the gym happens, activation cost, competing-script strength, or cache-compilation status. It has behavior and subjective states such as feeling resistant or energized. Thirty days of outputs bridge that gap. They support an inferred distribution, comparisons with changed conditions, and a check on whether an intervention shifted the rate as expected. This treats behavior as a scientific black box: its inside is hidden, but inputs can be modified and output changes measured. ### From Participant to Observer The participant waits for motivation, feels unwilling, and postpones until tomorrow. The observer instead names the measured rate of 26 gym days in 30, judges how hard starting has been, installs a bridge intended to raise the rate, and specifies how to check the result. Tracking enables this [kernel-mode](/wiki/superconsciousness) stance. Without measurement, the participant experiences states without the visibility needed for meta-awareness. With it, the same person can compare patterns and adjust their conditions. ## Common Failure Modes ### Over-Engineering A custom dashboard with 40 daily variables demands too much logging and too many distributions to estimate. The system collapses after 2 weeks without useful data. Beginning with 3–5 critical variables keeps the workload sustainable; additions need to justify their continued cost. ### Under-Utilizing A log that is never reviewed accumulates samples without producing an inference. Treating the act of logging as sufficient accountability misses its use as an instrument. A weekly 10-minute review asks which distributions and correlations are visible and which change might shift them. ### Precision Theater Three decimal places do not improve a decision that only requires distinguishing work on six days in ten from work on three. A duration of 7.342 hours is precise without necessarily being more useful or accurate. The resolution needs to support the intervention; a binary entry often suffices. ### Moralizing Samples Treating an unwanted outcome as a character judgment creates guilt, then missing entries precisely when behavior deviates. Those deviations are often the most useful evidence. Gym=0 three days in a row shows a lower rate and a configuration worth examining. It is data to retain, not a reason to stop recording. ## Integration with Other Frameworks ### Tracking + [Superconsciousness](/wiki/superconsciousness) Superconsciousness supplies the observer/operator stance; tracking supplies its measurements. “I feel like I'm not making progress” becomes “Work on 6 days of 30 this month, up from almost none last month.” A low rate then directs attention toward activation cost and competing routines. INSPECT_STATE has a concrete answer: “How often am I going to the gym?” can return 26 of 30 from the whiteboard. ### Tracking + [Probability Space Bending](/wiki/probability-space-bending) A visible streak and its continuation reveal the relation between today's sample and tomorrow's distribution: ``` Streak visible on whiteboard: X X X X X _ Visual pattern shows: - 5 consecutive gym days (high streak momentum) - 1 break (gap visible) - The next day now uncertain (will momentum restore or cascade activate?) Next day outcome: X X X X X _ X → Momentum restored (going is likely again) OR X X X X X _ _ → Cascade activated (going is now less likely) The tracking makes probability dynamics VISIBLE. ``` A five-day streak makes continuing likely, and one break makes it noticeably less so. The point is that the pattern itself changes the distribution being sampled. ### Tracking + [State Machines](/wiki/state-machines) A state machine assigns a distribution to the states that can follow the present one. Recording the starting state reveals these conditional differences: ``` State: "Home from work, energized" Tracked outcomes over 30 evenings in this state: 24x gym, 6x couch → gym on 24 of 30, about 0.8 State: "Home from work, depleted" Tracked outcomes over 30 evenings in this state: 5x gym, 25x couch → gym on 5 of 30, about 0.17 Architectural insight: Energy state dominates how often the gym happens. Intervention: Protect energy through day (prevent depletion state). ``` Instead of “sometimes I go,” the comparison is 24 of 30 in state A and 5 of 30 in state B. Preserving the energized state becomes the intervention suggested by that difference. ### Tracking + [30x30 Pattern](/wiki/30x30-pattern) The 30x30 pattern describes a month of daily repetition over which starting is expected to get easier. Tracking shows its installation curve: | Rep Range | Tracked attendance | Notes | |-----------|--------------------|-------| | Reps 1-5 | 0.2 (1/5) | High resistance, forcing required | | Reps 6-10 | 0.6 (3/5) | Resistance decreasing | | Reps 11-15 | 0.8 (4/5) | Starting to feel routine | | Reps 16-20 | 0.9 (9/10) | Approaching automatic | | Reps 21-30 | 1.0 (10/10) | Fully automatic | The shift from 1 in 5 to 10 in 10 over 30 repetitions shows the installation directly, in place of the general impression that the activity feels easier. ### Tracking + [Expected Value](/wiki/expected-value) Motivation rises with the size of the reward and the chance of success, and falls with the effort and the time until the reward arrives. Tracking improves the estimate of the chance of success. Enthusiasm can make it feel like nine in ten when it is three in ten; anxiety can make it feel like two in ten when it is seven in ten. A record of 3 completions among 10 similar projects supplies an estimate of about 0.3. For projects with daily tracking and Julius as a forcing function, 7/8 supplies about 0.88. Conditioning the estimate on the actual arrangement improves expected-value judgments and resource allocation. ### Tracking + [Prevention Architecture](/wiki/prevention-architecture) Tracking identifies a behavior whose access conditions can be removed and then checks whether removal worked: ``` Tracked over 30 days each: Phone accessible: doom scrolling on 22 of 30 days (high) Phone locked away: doom scrolling on 2 of 30 days (negligible) Architectural intervention: Phone off by default, locked in drawer. Result: doom scrolling on 2 of 30 days, without any resistance cost. Tracked validation: 28/30 days no doom scrolling (vs 8/30 before intervention). ``` The before/after record shows the unwanted behavior falling close to zero without the ongoing cost of resistance. ### Tracking + [The Braindump](/wiki/the-braindump) Tracking supplies quantities such as work on 6 days in 10 and sleep_quality = 7.5. A braindump supplies context: “felt resistant because unclear next step.” If work falls from 6 days in 10 to 3 and all the entries mention “unclear what to build,” the numbers identify the change while the notes identify ambiguity and working-memory overload as the mechanism. Defining the next action follows from that diagnosis. ### Tracking + [Working Memory](/wiki/working-memory) Working memory holds roughly 4 to 7 items. Gym frequency, work hours, sleep quality, meal timing, and energy patterns across a month exceed that capacity. A whiteboard, spreadsheet, or journal holds the state externally, leaving memory free to compare it. You can then see that gym attendance and sleep quality both fell during a week and ask about their relationship. Tracking turns the problem of remembering 30 days into the perceptual problem of comparing visible marks. ## Examples in Practice ### Will's Gym Installation (30x30 Pattern) Will recorded daily attendance as yes or no. Week 1, Days 1–7, produced 1/7, or 0.14. Activation cost was high, no routine was cached, and many alternatives competed. His description was “Hardest days of my life,” with each day feeling like a separate moral battle requiring force. Week 5, Days 29–35, produced 5/7, or 0.71. The cost had fallen, the routine was forming, and fewer alternatives competed: “Still conscious effort but getting easier.” By Week 16, Days 106–112, attendance was 7/7, or 1.00, and going took almost no thought: “I just went, barely thought about it.” The record made the installation visible as a shift from 0.14 to 1.00 through repeated changes to the system. In the observer framing, the individual days were samples rather than choices, and the pattern validated the intervention. ### Debugging Sleep Correlation The 30-day sleep record included bedtime, wake time, sleep quality on a 1–10 scale, previous-day exercise, and screen use after 8 PM. It produced these comparisons: ``` Exercise days (n=18): Average sleep quality = 7.8 No exercise days (n=12): Average sleep quality = 5.5 Difference: +2.3 sleep quality on exercise days Late screen time (n=10): Average sleep quality = 5.2 No late screen (n=20): Average sleep quality = 7.6 Difference: -2.4 sleep quality on late-screen days ``` The interventions were to prioritize exercise, aiming at the 2.3-point difference, and remove late screens, aiming to avoid the 2.4-point drop. The personal data supports the result for this system without relying on a population statement that exercise helps sleep. Continued measurement supplied the before/after comparison: ``` Month 1 (before intervention): sleep quality 7 or above on about a third of nights Month 2 (with exercise + no screens): sleep quality 7 or above on about four nights in five The share of good nights more than doubled through architectural changes ``` ### Work Output Tracking Ninety days of work-session and duration records showed: ``` Days 1-90 (Oct-Dec): work on 6/90 days = 0.067 Current rate ≈ 7% of days Architectural state: 3-month dormancy (detraining), no forcing function, ambiguous goals, competing scripts active ``` The measured output followed three months of dormancy, absent forcing, ambiguous goals, and active competing routines. Four interventions were planned: a daily 2-hour Julius sync, morning mantra plus OBS reactivation, externalization in Linear to reduce working-memory load, and concrete task definitions to reduce ambiguity. The expected change was work rising from about 7% of days to 60–80% over 30 days. This was a prediction to validate, not a result already obtained. Continued records would show whether the changes were sufficient or another intervention was needed. ## Reality Check: Observable Questions Require Tracking [Question theory](/wiki/question-theory) requires a measurement device for an observable question. “Am I making progress?” invites a story shaped by mood. “How many more days did I work this month than last?” can return a record: 12 days in Month 1, 18 in Month 2, six more. “Am I disciplined?” has no corresponding instrument. “How many gym days in the last 30?” can return 26 from the log. Tracking makes that empirical question answerable and allows the observer to work from records rather than a narrative about character. ## Related Concepts - [Signal Boosting](/wiki/signal-boosting) — how accumulated samples separate a pattern from noise - [Experience Extraction](/wiki/experience-extraction) — quantitative records within the extraction process - [Superconsciousness](/wiki/superconsciousness) — the observer stance - [Probability Space Bending](/wiki/probability-space-bending) — one action changing later probabilities - [State Machines](/wiki/state-machines) — conditional next-state distributions - [30x30 Pattern](/wiki/30x30-pattern) — observing the activation-cost curve - [Expected Value](/wiki/expected-value) — estimates based on recorded outcomes - [Prevention Architecture](/wiki/prevention-architecture) — checking changes to access and triggers - [The Braindump](/wiki/the-braindump) — qualitative context for the numbers - [Working Memory](/wiki/working-memory) — externalizing more than can be held mentally - [Journaling](/wiki/journaling) — explanations accompanying quantitative patterns - [Question Theory](/wiki/question-theory) — matching questions to measurements - [Error Signal](/wiki/error-signal) — a declared target supplies the comparison that makes a measurement a signal ## Key Principle Tracking makes the system's outputs visible over time. The observer uses those samples to infer a distribution, changes the conditions producing it, and measures the next set of outputs. Recording both the conditions and the behavior makes that cycle possible; treating unwanted samples as useful evidence keeps it working when the system needs attention most.