Stop 9 of 9 · Weekly
Karim's month and the capstone
Three routines that carry the month, Cowork for the exhibit list, and the graded capstone: one delay from update comparison to claim package.
The month on three routines
Eight stops of parts, arranged into a month that runs whether or not the week is a good one.
| When | What runs unattended |
|---|---|
| Update day, 06:00 | Baseline against update: the change register and the float table, written to a file, nothing concluded |
| Friday, 16:00 | The correspondence log: letters sent and received this week, every notice clock running, with days remaining |
| First working day, 06:00 | The monthly narrative draft from the update export and the change register, gaps left bracketed |
Each one reads, compares and drafts. None of them concludes, cites a clause without a page, or sends anything, because those are the three ways a scheduling consultancy loses an argument it should have won.
On the eighth of each month at 06:00, compare the accepted baseline exports with the newest update exports in the C-1149 folder. Write one file: the change register grouped by activities, durations, logic, constraints, calendars and progress, then every activity whose total float fell by five working days or more with both values. State the data date of each file you used and list anything you could not compare. Do not state any effect on completion, do not attribute a cause, and do not draft any correspondence.
Cowork for the exhibit list
The exhibit list is the job nobody wants and everybody notices. Delegate it.
Work through the Claim exhibits folder for C-1149. For every document, record the exhibit number, the date, the document type, from and to, and one line on what it shows. Then check the exhibit list against the package draft: every exhibit referenced in the text that is not in the folder, and every document in the folder that nothing refers to. Write the list and the two gap reports to files. Rename nothing and move nothing.
The capstone
Take one delay on a live or closed engagement and run it end to end. Five artefacts: the change register and float table from two exports, the chronology and fragnet with the evidence column and your P6 run results, the monthly narrative paragraph with its reservation, the notice letter and the response to the rejection, and the claim package draft with its verification pass and exhibit list.
[upload the five capstone artefacts] Grade this against the rubric below, out of 100, scoring each criterion separately and quoting the evidence you used. For every point not awarded, say exactly what is missing and what would earn it. Be strict about three things: any number that cannot be traced to a schedule run, a cost record or a printed document; any clause cited without a verified page; and any sentence that states a legal conclusion.
| Criterion | Points | Full marks means |
|---|---|---|
| Notice proved | 20 | Every applicable clause has a row, a deadline and the letter that served it, inside the clock |
| Facts traceable | 20 | Every date, ID and duration points at an export row or a document reference |
| Boundary held | 25 | No delay quantum, cost or legal conclusion produced by Claude anywhere in the package |
| Causation evidenced | 20 | Every link in the chain has an exhibit, and thin links are marked rather than hidden |
| Citations verified | 15 | Every clause quoted as printed, with a page, checked against the special provisions |
Eighty passes. Below eighty, the gap is almost always the same two: a number nobody can source, and a clause nobody read on the page.