The work elsewhere
Work that happened somewhere else
22 items have been filed by somebody who did the work outside this platform. 18 became work units, 3 are waiting for a person to promote them, and 1 was refused. None of it is graded as observed, because observing it is exactly what the platform could not do.
The five ways work reaches this platform without being observed
Each channel issues an assurance grade, and the grade is a property of the channel rather than of the person using it.
The platform sees what the sender wrote. It did not see the work and cannot confirm it happened.
One address per function. The message body is stored verbatim and never summarized before it is filed.
A row in somebody’s workbook is a claim about work, not a record of it.
Each row becomes one unit. The uploader’s name travels with every row so the claim always has an author.
Chat carries the least structure of any channel here and the platform grades it accordingly.
Only messages that name a function and a subject are filed. Everything else is left alone rather than guessed at.
The fields are enforced, so the record is complete. It is still a statement by the submitter rather than an observation.
The only channel where the platform can refuse an incomplete submission rather than accept it and flag it.
Written from memory after the fact. This is the weakest grade the platform issues and it is kept separate for that reason.
Does not create a work unit automatically. Somebody has to promote it, and the promotion is recorded.
Everything filed
The words the submitter wrote are kept verbatim. Nothing here has been summarized before it was filed, because a summary of a claim is a second claim.
Rang the account manager at Delfland Packaging on Monday. They will hold the current price to the end of September if we confirm volumes this week. Nothing in the portal yet.
Eleven adjustments prepared outside the ledger and posted as one journal. Workbook attached with the line detail.
Two shipments held at Rotterdam. Cleared directly on the carrier portal, no record on our side.
Advised on the distributor termination clause. No matter opened because the question was answered in the meeting.
Handled outside the contact center. Customer accepted a partial credit. Written up from memory the following morning.
Emergency spare part bought on a card because the supplier would not wait for a purchase order.
Fourteen runs recorded in the research notebook, which is not connected. Summary rows uploaded here so the work is at least counted.
Agreed to keep the legacy adapter for one more release. Recorded in a commit message only.
Meeting room reconfiguration for the Rotterdam floor. Asked at the desk, filed here afterwards.
Deliberately not systematized. Recorded here as a count only, with no detail, so the volume is visible without the content being stored.
Nine approvals given by email to the agency. None of them reached the automation platform.
Replaced a docking station on the fourth floor. No ticket because the user asked in the corridor.
Customer in Lisbon placed an order verbally. Keyed the next morning under the rep’s own login.
Claim settled at the meeting and confirmed by email the same day. No claim record was opened at the time.
Weekly workbook reconciliation between the quote tool and the order book. Twelve mismatches resolved by hand.
Service desk agent resolved the query on the call and closed it without a note.
Panel gave feedback in the debrief. Recruiter summarized it into the tracking system two days later.
Invoice arrived at the Antwerp site by post and sat there for three weeks before being forwarded.
Twenty-two close tasks tracked on a personal checklist rather than in the close tool.
Demand plan overridden for two SKUs after a verbal agreement. No record in the planning system.
Indirect tax treatment for a Portuguese promotion. Answered on the call, written up afterwards.
Three rounds of redline with the counterparty by email before anything entered the contract system.
Attestations for work nobody watched
Who attested, what they attested to, and when. 3 of these are signed by the post rather than by a named individual, because the platform holds the post for those roles and not the person in it. None of these carries a spine sequence: they were written at assembly rather than as the work happened.
I prepared eleven close adjustments outside the ledger during the July period and posted them as a single journal. The workbook holding the line detail is the one uploaded here.
I gave commercial advice on the distributor termination clause to the Iberia team on 12 August. No matter record was opened.
I authorized an emergency card purchase for a spare part because the supplier would not accept a purchase order at short notice.
Fourteen bench runs for the reduced-sugar trial were completed in the week to 13 August and recorded in the research notebook, which this platform cannot read.
An employee relations conversation took place. I am attesting to the count only. No content has been recorded here and none should be.
I agreed a trade claim with the customer in a meeting on 15 August and confirmed it by email the same day.
I reconciled quote and order data by hand for the week to 15 August and resolved twelve mismatches.
A supplier invoice was received at the Antwerp site by post and held there before being forwarded. I cannot attest to the exact date of receipt.
Twenty-two close tasks for the July period were completed against my own checklist rather than in the close tool.
I accept that roughly two fifths of what Legal does is not visible to this platform, and that the split between inferred and unseen came from an interview rather than a count.
Half of R&D activity sits in the research notebook, which is not connected to this platform. I attest to the volume figure quoted for it.
The unseen figure for Administration came from a two-week manual tally that I ran. It is an estimate and it will be wrong in both directions on any given week.
Actions
What is waiting on a person
Every line below is work the platform did not see. The action is never to trust it more than it deserves - it is to grade it, name somebody for it, or refuse it.
accepted items nobody has attested to
These became work units on the strength of a submission alone. That is enough to count them and not enough to rely on them, and the assurance grade on each one says so.
items waiting for somebody to promote them
All 3 arrived on a channel that does not create a work unit on its own. Until a person promotes one it is counted here and nowhere else in the estate, which is deliberate - the weakest channel should not be able to add to the work count by itself.
items written from memory after the event
Recalled is the weakest grade the platform issues. These items are counted, kept separate, and never rolled into an observed figure.
attestations under challenge
A challenged attestation stays on the record with the challenge attached rather than being withdrawn. Both the statement and the objection are readable, and neither one is resolved by this surface.
Operations
What this desk is allowed to start
A surface that only reports is not operable. This is the work this page can set in motion, and the bound it runs into.
Trigger and bound
This surface accepts work the platform cannot observe, grades it below anything it can, and records an attestation when somebody signs for it. It cannot verify any of it, and it does not turn an attestation into an observation. Every attestation on the record today was written at assembly rather than as the work happened, so none of them carries a spine sequence. Promotion of a recalled item is a human act and is recorded as one.
Live observability
What the record shows right now
All 22 intake items by the assurance grade the channel issues, 3 grades in use. No item here carries the observed grade, because observing it is exactly what the platform could not do.
Current distribution
22 items
Is policy and strategy coming to fruition
Whether the written intent is holding here
The intake half holds. The spine half does not yet.
Not holding on the record
The intent was that off-platform work is counted rather than ignored or dressed up as observed. 22 items across 5 channels are now counted, 18 of them as work units, and every one carries a grade below observed. The attestations, however, were written at assembly and carry no spine sequence, so the record exists and its position in the evidence order does not. Attestations written from this point forward will carry one.
Why counting this is better than either alternative
An intake item is a statement by a named person that work happened. It is not an observation. Every item keeps the words the submitter wrote, the channel it arrived on and an assurance grade below anything the platform observes for itself. Counting it is more honest than ignoring it, and grading it is what keeps it from being dressed up as observed.
An attestation is a person putting their name to something the platform did not see. It is written to the evidence spine typed as an attestation, which is a weaker record than an observation and is never counted as one. An attestation can be challenged, and a challenged attestation stays on the record with the challenge attached rather than being withdrawn.
1 channel does not create a work unit on its own. The weakest grade the platform issues should not be able to add to the work count without a person deciding it should.