Part I. The Scream of the Prefrontal Cortex: A Field of Burning Dominoes

Chapter 1. Morning at Plant 3, a Strange Resonance

The entrance to Plant 3 was always filled with a strange resonance.

Each time the 160-ton toggle injection molding machine pushed the mold with the high-pressure scrape of cylinders, the double glass of the control room trembled faintly. At 8 a.m., exactly as the shift changed, the production manager took a sip of coffee and stared at the monitors.

On the dual monitors over his desk, unfinished work blinked in disorder: a reminder from headquarters about the first-half cost-reduction report, a defect report about cracks in outsourced machined parts from the night shift, and an alert from IT that warehouse system inventory did not match the physical count.

Out of habit, he opened a memo pad and began writing whatever had to be done that day. Under the mechanical heading "To Do List," more than ten tasks poured out almost instantly.

• Replace the broken part on Line 3 and attend the test run
• Prepare a meeting to pressure the subcontractor and secure alternatives
• Draft the first-half cost-reduction performance report
• Verify consistency between warehouse physical count and ERP inventory data
• Summarize reasons for field utilization delay and send them to headquarters

He believed he was a veteran of this manufacturing floor. For more than a decade he had learned injection molding and mold technology from the bottom up, and whenever an incident occurred he had thrown his body into the line to save production. When a process went wrong, he knew by instinct which valve to close and which parameter to adjust.

But for the last several months, what visited him on the way home was not achievement. It was extreme fatigue and a hollow feeling he could not name. He had run around the field all day, breathless, unable to sit comfortably for even ten minutes. Yet when he asked himself near the end of the day, "What did I complete today?", his mind went blank. He had put out many fires, but the trajectory of time he should have protected seemed to have evaporated.

Chapter 2. Dominoes on Fire Together

His day was like dominoes on fire together.

When one chip fell and passed the flame, every plan and time grid arranged behind it burned down in sequence. When the materials team's inventory mismatch alarm rang, he ran to the floor. When the subcontractor called about cracked parts, he shouted. When he returned to his desk to write the headquarters cost-reduction report, the plant manager's intercom rang.

"Production manager, where is the headquarters report? The planning director says that if the data is not sent by this morning, this utilization evaluation will carry a penalty."

The plant manager's heavy voice poured out through the thin vibration plate of the intercom speaker. The production manager looked reflexively back at the memo pad. Beside "write cost-reduction report," there was no mark. The wall clock already pointed to 11:40.

All morning he had not played for a single moment. At 9, a report came that the Line 3 compression cylinder was slipping, so he put on work clothes and ran to the floor to work with engineers. At 10:30, he brought in the subcontractor's president and shouted about the cracked parts. But the report file, the core objective of the morning, had not even been opened on the desktop. Intention existed, but execution evidence did not.

"Should I do this first, or that first?"

His prefrontal cortex was constantly discharged by decision fatigue inside the flood of tasks. The research finding that execution probability falls as choices increase was not a foreign theory. He had not rested for a moment, but he had completed nothing. The ten-plus items in the morning To Do List were not a symbol of control. They were a cruel gallows that paralyzed his prefrontal cortex.

Neuroscientifically, his prefrontal cortex was suffering severe decision fatigue every morning. The prefrontal cortex handles planning and decision-making. But the moment more than ten untimed tasks are densely listed, the brain begins asking unconscious questions without end. In that endless priority weighing, prefrontal energy is depleted before real work even starts. The paradox of choice was happening inside his brain in real time.

Chapter 3. The Split Grid, the Fragmented Human

That night, with only the minimum night-shift crew left and the machines finally quiet, the production manager stayed alone in the office.

He opened the daily timeline screen of ExaTimebox+, which he had kept buried in a monitor drawer. The screen held honest traces of execution, every moment of the day left as ten-minute Cells.

The visual reality of his day was brutal.

Line 3 attendance, 20 minutes. Subcontractor call, 20 minutes. Report file review, 10 minutes. No task filled more than three consecutive Cells, or 30 minutes. Whenever he sat down to start something essential and was about to enter the orbit of focus, a field alarm rang or someone else's urgent request stole his cognitive resources.

His "time" had been cut into 10-minute and 20-minute fragments and scattered everywhere.

He clicked the behavior analysis report tab in the lower right. The vague fatigue he had felt became sharp statistical indicators on the monitor.

[Behavior Analysis Diagnostic Result]
- Average observed episode duration over one week: 1.4 Cells (14 minutes)
- Fragmentation Index: 0.78 (Risk)
- Start-up Barrier for unstarted intentions: High
- Tomorrow schedule overload probability: 88.4%

The indicators spoke coldly. He had not been lazy. He had been trying to do too much, overdriving cognitive resources at every moment.

When a human begins an action, the brain consumes enormous transition energy. It is like the heavy electrical load required to bring a stopped machine up to target RPM. The brain is also a slave to the Zeigarnik effect, constantly raising unfinished work into awareness. The ten-plus unfinished tasks in the memo pad were consuming his brain energy in real time.

He had spent the whole day repeatedly accelerating and braking dozens of tiny 14-minute behavioral episodes. The reason his fingers trembled at quitting time was not physical labor. It was severe cognitive overheating caused by this fragmented transition process.

On the drive home, his hands often shook lightly on the steering wheel. There was no evidence that he had lived diligently. Only the miserable sensation remained: a consumed part, fragmented to the soul while mechanically reacting to the world's stimuli. Unfinished tasks occupied working memory like fog.

Chapter 4. Parkinson's Law and the Trap of Planning Fallacy

The production manager stepped out of the control room and lit a cigarette.

In the darkness, the production line was a rigorously controlled closed system. The resin weight entering the hopper, the controlled temperature of the heating cylinder, and the WIP quantity flowing between processes were managed under calculated physical constraints.

But beyond the cigarette smoke, his own resource called "time" was entirely different. It was a fully open system into which external incidents and other people's cognitive interference rushed in without a filter.

He suddenly understood why he always exerted superhuman force only at the deadline, and why everything always took longer than planned.

"Work expands to fill the time available for its completion."

It was Parkinson's Law. A report due in a week somehow takes exactly a week to finish. Without an artificial boundary, work stretches and loosens without end.

In planning, he had also fallen into the planning fallacy: assuming that everything would go perfectly. Field equipment failure and subcontractor calls were excluded from the calculation; only the best-case scenario without interference was used as the default. Like the experiments at the University of Waterloo, humans carry a cognitive bug that predicts from ideal conditions. Cognitive bias and system ignorance had combined into a predictable failure.

Looking at the monitor light reflected in the control-room glass, he realized:

"I manage process utilization by the second. Why have I never measured the actual capacity of my own behavior?"

Part II. The Compass in Fog: Accepting a Bayesian Prior

Chapter 5. 1 a.m., Awakening in the Control Room

The glass of Plant 3's control room still reflected the reddish night guide lights. At 1 a.m., the production manager crushed out the cigarette and walked inside. The emergency calls and disorderly noise that had pressed on him all day had subsided into an almost unnatural stillness.

He looked at an old printed Elon Musk article taped beside the monitor. It described how a person commanding Tesla's Gigafactory and SpaceX's Falcon launch pad at the same time controlled terrifying density and complexity within the same physical limit of 24 hours.

"He did not obey a timetable. He controlled the gap between plan and execution."

That autumn, desperate not to live like this anymore, the production manager turned on the Bayesian activity management engine in ExaTimebox+ and began to face his broken trajectory.

The first thing he saw was his severe planning fallacy. He too had ignored the "average daily reality" of field incidents and delayed meetings, believing with excessive optimism that a three-hour report could be finished in one hour.

The Bayesian engine shattered that cognitive arrogance. Whenever he pushed 7 or 8 tasks into the tomorrow-prep screen, the engine sent a cold warning: overload probability 90%, based on his historical actual record data.

He decided to accept the great principle of Bayesian thinking.

He abandoned the fantasy of building a perfect timetable from a zero state with no data. Instead, he honestly placed his subjective experience and poor past execution records into a vessel called the Prior. That was all. From that humble admission, everything began to change.

Chapter 6. Breaking the Illusion of the Timetable

Until then, he had misunderstood the "ten-minute grid" as a timetable.

He had tried to fill it with fixed plans: what to do from this time to that time, and what to do next. Each time a field variable erupted, the whole plan collapsed like dominoes.

The ten-minute Cell grid on the screen was not a set of tight gears to be fitted together. It was only the minimum digital grid, a tracking filter, for honestly marking the traces of what he actually did in the uncertain sea of tomorrow.

The essence was not writing a timetable. It was controlling the plan-execution activity process to prevent cognitive overload and close selected priorities.

He moved the mouse and poured the tangled tasks in his head into Brain Dump. Like discharging electricity onto paper, he stopped the brain from holding unfinished tasks and consuming energy. He deliberately cut the chain of the Zeigarnik effect.

Chapter 7. Four Rings Built on Real Limits

The production manager entered the tomorrow-prep screen.

He boldly stopped his old habit of mechanically registering ten-plus tasks because every visible issue felt as if the plant would collapse if not handled tomorrow.

After pouring the clutter of his mind into Brain Dump, he accepted the physical constraint that even Elon Musk could not finish everything in one day. Then he compressed the core intentions that had to be completed when the plant opened the next morning into only four items and put them onto the Today To Do list.

[Priority 1] Finalize first-half cost-reduction performance report (submit to HQ planning)
[Priority 2] Final confirmation of Line 3 injection molding feed-guide replacement test
[Priority 3] Alternative-material meeting for subcontractor crack defect response
[Priority 4] First causal analysis of warehouse ERP inventory mismatch

When he limited the list to four and ranked it, the posterior predictive simulation engine on the right dropped the overload probability from a dangerous 88.4% to a stable green 31.2%.

Based on the accumulation of his actual execution Cells and behavioral inertia, the four Rings fit within the execution capacity that his brain could control tomorrow without collapsing. The numbers were telling him: when he admitted his limits, completion became possible inside those limits.

"Do not make a timetable. Keep the order."

He finally understood the destination of timeboxing. It did not matter whether a subcontractor called at 9 or a field alarm rang at 10. With no rigid timetable, the plan could not be broken. When the interruption was resolved and he sat down again, he only had to remember that the next target was Priority 1. Abandon the desire to multitask. Leave execution evidence until one Ring is completely Closed. That was all.

Part III. The Bayesian Chain: Recursive Estimation and Calibration

Chapter 8. The Ten-Minute Grid, the Minimum Unit of Measurement

The real change began when his view of the ten-minute Cell grid changed.

It was not a pressure timetable trying to control every minute and second. It was a measurement grid for comparing expected behavior with actual elapsed time and calibrating the cognitive error of the brain.

He sat down to execute the first Ring, "write the cost-reduction report," and pressed the timer start button. Whenever external stimuli broke in, he honestly marked the ending and starting points on the timeline grid.

[Estimated time: 60 minutes] -> ■■■■■■ (6 ten-minute Cells assigned)
[Actual observation: 110 minutes] -> ■■■ (30 minutes executed, then interrupted)
                                  ... ■■■■■■■ (70 minutes of focus, then closed)

At first, the gap between expectation and actual time made him feel self-blame. But the system's core architecture, recursive Bayesian estimation, began to operate, and the situation changed.

The many logs of past failures and meeting delays were compressed into posterior state and sufficient statistics inside the system. Some remained as simple alpha/beta balance; others remained as more complex states of duration, capacity, fragmentation, and TX density. Each time he compared "estimated time" with "actual time" and accumulated evidence, the posterior distribution calibrated his brain mechanism more honestly.

Chapter 9. Brain Calibration: The Compass Made by Data

As the Bayesian chain repeated from Prior to Likelihood to Posterior, the precision with which his brain predicted time began to calibrate rapidly.

How much energy he needed for each category of work, how many minutes of Start-up Barrier existed after an incident before he could return to the original task: these were no longer subjective impressions. They became a precise data compass.

The compass was not just numbers. It was an objective and honest map of himself. Not how fast, but how predictable. Not how much, but how completely closed. That distinction was the essence of productivity, and the Bayesian engine was making the essence legible in numbers.

The calculation ExaTimebox+ runs day by day is simple. When the user confirms the core To Do set on the tomorrow-prep screen, the system runs 10,000 Monte Carlo samples from posterior parameter distributions built from historical data, then derives overload probability.

Load^m = Σ_i Z^m_i × D^m_i,e    (where Capacity^m ~ NB(r_cap, q_cap))

P_overload = (1/M) Σ_m I(Load^m > Capacity^m)

Ten thousand virtual tomorrows are simulated, and the system calculates how many exceed the production manager's actual execution capacity. Numbers do not lie. And those numbers were protecting him: from greed, and from himself.

Part IV. Closure of the Ring: Clear Pieces, Regained Control

Chapter 10. 6 p.m. the Next Day

At 6 p.m. the next day, when the bell announced the shift change at Plant 3, the production manager returned to the monitor and opened the Today Result summary.

His timeline was still not a perfect straight line. The traces of ten-minute Cells broken by urgent field calls remained. There was an unexpected detour in the afternoon because of a material mismatch issue.

But there was a huge difference from the fragmented days of the past.

[Priority 1: Cost-reduction report] ■■■■■■■■■■■ (110 min closed) -> [Status: CLOSED]
[Priority 2: Line 3 test run]       ■■■■         ( 40 min closed) -> [Status: CLOSED]
[Priority 3: Subcontractor meeting] ■■■          ( 30 min closed) -> [Status: CLOSED]
[Priority 4: Inventory cause]       -            (not started)    -> [Status: OPEN -> choose again tomorrow]

It was not a fragmented day where he was swept from one issue to another and completed nothing.

Even amid incidents, he returned to his desk and finished the Priority 1 report. Then he closed Ring 2 and Ring 3 in order. He did not mechanically react to external stimuli and wander around. Even if the field alarm briefly pulled him away from the grid, when the situation was resolved and he sat again, his prefrontal cortex did not waste energy asking, "What should I do next?" The boundary of Priority 1 was clear.

Priority 4 was untouched, and that was fine. It belonged to tomorrow morning's judgment, where he would look at statistical context and choose again. The Bayesian engine did not erase that fact or decide for him. It simply left a clear difference between the unstarted Open Ring and the Rings closed today, so that he could decide again in the morning.

Chapter 11. Daily Review: The Miracle of 130 Minutes

The daily review panel in the lower right displayed a subjective score of 5.

The total execution time was only 130 minutes, less than usual, but the cognitive fatigue was astonishingly light. The sense of release and clarity in the brain was beyond comparison.

This was the paradox. He felt lighter than when he did more. He completed more than when he worked longer. Not pouring endlessly, but closing what was chosen completely. That was the real grammar of productivity.

The fog of unfinished work that had eaten into his brain was gone. The prefrontal cortex maintained deep focus and alertness, radiating the vitality of living intelligence. He could concentrate deeply without decision fatigue, and after concentration came real rest.

Part V. Metamorphosis: From Ghost of Time to Architect

Chapter 12. Two Months Later at Plant 3

Two months later, the production manager in the control room of Plant 3 had become a completely different person.

The old version of him had mechanically reacted to the world's stimuli and been dragged around after losing control. Now he was an architect who structurally designed time and behavior. He separated reactive time, such as sudden meetings, email checks, and field alarms, from autonomous deep-focus time.

When he opened the tomorrow-prep screen, his prefrontal cortex no longer felt decision fatigue. The Bayesian posterior predictive simulation engine first showed tomorrow's overload signal based on his calibrated data pattern, and he adjusted the number and size of Rings himself while looking at that signal. He did not overreach. He intentionally arranged rest and focus with the feeling of walking with himself.

The result was an explosive blooming of productivity.

Once a Ring was chosen, it was closed that day despite incidents. The headquarters cost-reduction report was sent three days before the deadline with perfect consistency. Plant utilization renewed its all-time high inside his refined behavioral-management prediction range.

Chapter 13. The True Architect of Time

The production manager was no longer a ghost of the field, dragged by the merciless speed of the conveyor belt.

He had become a true architect of time, honestly accepting physical constraints and placing the most certain evidence of execution inside limited resources. It was not a matter of superhuman willpower. It was a system problem. A measurement problem. And a problem of honesty toward oneself.

Bayesian timeboxing returned three things to him.

First, the sense of closure. Every evening, when his chosen Rings changed to CLOSED, dopamine flowed through his prefrontal cortex. Closure was addictive. A healthy addiction.

Second, a predictable self. He learned how long each kind of work took and under what conditions focus broke. It was a map of himself, and the map became more precise each day.

Third, real rest. Unfinished tasks no longer ate into his brain after work. When a Ring was CLOSED, the brain recognized it as release. As that release accumulated, the density of life changed.

Chapter 14. The Red Sunset

At 6 p.m., when the factory bell rang, the production manager put on his coat with a light smile.

His hands no longer trembled from fatigue.

This was the deep calm and fullness that comes to a person who has trained the inner system through Bayesian timeboxing and regained control over the day. It was not merely satisfaction with results. It was existential fullness from the fact that the day had flowed as he had designed it, and that he had completed the choices he made despite uncertainty.

Beyond the control-room glass, the magnificent red sunset shone as if blessing the great journey of an architect who had escaped from being a ghost dragged by time and learned to govern his own life.

And it was not only the production manager's story.

Epilogue: Where Is Your Plant 3?

At this moment, somewhere, someone lives like the production manager.

A developer staring at a monitor until dawn without completing anything. A startup founder whose Ring for the work they truly want to do carries unfinished from night to night between meetings and reports. A student moving between cram school and self-study without ever digging deeply into the most important thing. A working parent feeling that their time belongs completely to no one, between childcare and work.

Their factories are in different places. But the structure of what happens inside those factories is astonishingly similar.

Burning dominoes. Fragmented grids. Debris of Rings that were never closed.

ExaTimebox+ is an answer to this structural problem.

It does not ask you to make a denser timetable. It does not ask you to work harder. It asks you to measure your real execution capacity honestly and close the most essential Rings one by one within that capacity. The Bayesian engine shows the point where ambition turns into overload before it happens. Ten thousand virtual tomorrows protect you.

Your day can be designed by you.

Each time you close one Ring, you become a little more of an architect.

Appendix: Core Mathematical Specification of B-TEEM v2.0

For external academic and system-architecture review, this narrative includes the mathematical specification of B-TEEM (Bayesian Time-Behavior Evidence Emission Model) v2.0, the plan-execution control mechanism behind the story.

A.1 Pre-execution latent importance state space ($V^{pre}$)

To prevent same-day execution results from leaking into pre-execution importance judgment, the model uses only morning intention features.

$\eta_{u,d,i} = \rho_u \eta_{u,d-1,i} + (x^{pre}_{u,d,i})^T \omega_u + \epsilon^{V}_{u,d,i}$

$\epsilon^{V}_{u,d,i} \sim \text{Normal}(0, \sigma^2_V), \quad \rho_u \sim \text{Beta}(a_\rho, b_\rho)$

$V^{pre}_{u,d,i} = \frac{1}{1 + \exp(-\eta_{u,d,i})}$

A.2 Plackett-Luce rank-observation likelihood

Likelihood for the rank array $r = (i_1, i_2, \dots, i_n)$ decided by UI drag and drop:

$P(i_1 \succ i_2 \succ \dots \succ i_n \mid \eta_{u,d}) = \prod_{k=1}^{n} \frac{\exp(\eta_{u,d,i_k})}{\sum_{j=k}^{n} \exp(\eta_{u,d,j})}$

A.3 Separation of Start and Continuation transitions

$Z_{u,d,i} \sim \text{Bernoulli}(p^{start}_{u,d,i})$

$\text{logit}(p^{start}_{u,d,i}) = \alpha^{start}_{u,c_i} + \beta^{start}_V V^{pre}_{u,d,i} + \beta^{start}_r \text{rank\_signal}_{u,d,i} - \beta^{start}_c \text{carry\_count}_{u,d,i}$

$G_{u,d,i} \sim \text{Bernoulli}(p^{cont}_{u,d,i})$

$\text{logit}(p^{cont}_{u,d,i}) = \alpha^{cont}_{u,c_i} + \beta^{cont}_V V^{pre}_{u,d,i} + \beta^{cont}_f \text{recent\_fragmentation}_{u,i}$

A.4 Zero-Truncated Negative Binomial episode generation

$P(D_{u,d,i,e} = y \mid y \ge 1, r_{u,c}, q_{u,c}) = \frac{\Gamma(y + r_{u,c})}{\Gamma(y+1)\Gamma(r_{u,c})} \frac{q_{u,c}^{r_{u,c}} (1-q_{u,c})^y}{1 - q_{u,c}^{r_{u,c}}}$

$\text{Frag}_{u,d,i} = \frac{K_{u,d,i}}{Y_{u,d,i}}$

A.5 Posterior predictive simulation (M = 10,000)

$\text{Load}^{(m)} = \sum_{i \in \mathcal{T}_{u,d+1}} Z_{u,d+1,i}^{(m)} \times D_{u,d+1,i,e}^{(m)}, \quad \text{Capacity}^{(m)} \sim \text{NB}(r^{cap}_u, q^{cap}_u)$

$P\_\text{overload} = \frac{1}{M} \sum_{m=1}^{M} \mathbf{1}\!\left(\text{Load}^{(m)} > \text{Capacity}^{(m)}\right)$

These equations were running quietly behind the production manager's monitor every night. And they are still running now.