His Rejected Luna Returns

When The Plan Breaks

Caelan opened the blank response column on the repair schedule and pulled the first cure-sensitive milestones onto a separate screen.

The distinction they needed was simple enough to say and hard enough to operate.

A schedule could move without failing.

A cure obligation could not.

He started with an example already on the board.

The drainage crew at marker twelve had lost ninety minutes when the material truck arrived late. The physical repair still had enough time to finish before the reserved inspection window.

No escalation.

The crew could resequence work inside its assignment and keep moving.

The second example was different.

A contractor working farther north reported an equipment fault that could push both the repair and the only available verification slot past the governing milestone.

Caelan marked the item threatened.

The schedule automatically opened a joint-review record beside it.

Seren joined from the field channel.

“Keep the original milestone visible.”

Adrian added a second time field for revised operational timing rather than allowing anyone to overwrite the cure date.

The distinction solved one of Caelan’s biggest concerns with schedule management.

Field teams could adapt without making the legal record disappear beneath their edits.

He wrote the escalation trigger beside every cure-sensitive row.

If required physical work, evidence, or joint verification was likely to miss its governing milestone, the item entered threatened status before the failure occurred.

The joint review could then add resources, resequence work, change inspection timing, or ask legal to interpret the cure language.

It could not move the legal deadline by editing a calendar cell.

The equipment-fault item became the first live test.

Silvercrest operations found a replacement unit at a noncritical interior road project. Moving it would delay that work by half a day but would not create a safety problem.

Caelan approved the transfer.

A flatbed left Crestfall twenty minutes later.

The contractor crew remained on site rather than standing down.

Seren’s verification team had another conflict.

Its original inspection slot would expire before the replacement machine reached the section.

Blackridge had one verifier available later that evening, but using that slot meant shifting a non-cure inspection elsewhere.

Seren made the move on her own schedule.

The cure milestone stayed where it was.

The replacement equipment reached the contractor before the revised field start time.

Adrian attached the transfer order, updated inspection slot, and unchanged cure date to the threatened-item record.

The schedule had just absorbed a real disruption without inventing a new authority or hiding the delay.

Caelan turned to the next weak point.

Completion status.

Silvercrest’s internal work-order system could close a task as soon as a supervisor accepted the crew’s report. That was useful for payroll and maintenance administration. It was not enough to decide whether a cure-sensitive item had satisfied the joint standard.

The cut-slope reinforcement provided a live test.

The Silvercrest supervisor reported the anchor replacement complete and closed the internal work order.

Blackridge’s verifier reached the site ten minutes later.

One fastening point remained outside tolerance.

Under the old administrative process, the supervisor could have left the work order closed and added a follow-up note.

Caelan reopened the item for cure purposes while leaving the payroll record intact.

The crew stayed at the slope and corrected the fastening point.

Adrian added the failed verification to the cure history.

When the second inspection passed, the item earned cure credit.

The sequence created a useful separation.

Silvercrest could manage its own internal records however its administration required.

Cure credit came only after the evidence and verification step defined in the binding schedule.

Caelan did not need to repeat that rule at every row after the first live example proved it.

He made the system enforce it instead.

A completed internal work order could no longer automatically change the cure field.

Only the joint verification record could do that.

The operations staff updated the schedule logic.

Seren checked the change from the field.

“Good. Now test a failed inspection after the legal milestone.”

Adrian built the case.

If physical work finished before the milestone but required verification occurred after it, the item did not receive automatic cure credit merely because the crew had finished on time. The schedule had to preserve enough verification capacity to complete the required step inside the governing period unless the operative legal language said otherwise.

That turned inspection availability into a resource rather than an afterthought.

Caelan added it to the next chapter’s audit list.

By evening, the response column no longer contained vague instructions like escalate or monitor.

Each cure-sensitive row showed what ordinary operations could change, what event created threatened status, who entered the joint review, how the original milestone remained visible, and what proof moved the item into cure credit.

The equipment-fault item stayed threatened until its revised work passed inspection.

The cut-slope item had returned to cured status after the second check.

The convoy was still staged.

The repair schedule was no longer fragile because one plan had to happen exactly as written.

It had rules for surviving when the field refused to cooperate.

Caelan sent the schedule into final resource audit.

The next question was whether Silvercrest had actually committed enough people, material, equipment, and inspection capacity to make those rules useful.