Where the package stands
Every number here is counted from the record of events. Select a number or an item code to see the documents behind it.
Items by stage
Who has the ball
No movement for more than days
Records that do not add up
All items
Select an item to read its full chain, from first submittal to delivery, with the source of each step.
| Code | Item | Area | Stage | Ball with | Days idle |
|---|
Floor plan
Each area takes the status of its worst item. Choose who has the ball to see where they are holding the job.
- A record does not add up
- An item has stopped moving
- Moving normally
- Everything delivered
Inbox
An email never changes the record by itself. The system reads each message and drafts the update it implies, with the sentence it rests on. A person accepts, rejects or discards it. Here the drafts are written in advance, so the model runs without a mailbox or a language model.
Sources
Another party's register is a claim, not a fact. When it runs ahead of the record, there is no document behind it: a discrepancy opens and the claim is set aside. When it runs behind, it is simply out of date.
| Item | The register says | The record says | Last document | Verdict |
|---|
Two documents, two answers
Status report
Written from the record as it stands now. It only goes out if it passes the checks on the right.
The gate
| Milestone | Last report | Now |
|---|
Try to break it
The architect withdraws the approval of SUB-007 in a letter. Record it, then try to publish.