Five work samples from operations.
Concept work with fictitious data. It shows how we work and is not a client reference.
Will Friday hold?
The pilot start is promised for Friday, 22 Nov. Two sources give different approval dates – and that decides whether the date holds. Tap the IT security message.
Hello all, we can only grant the approval of the data interface on Wednesday, 20 November. The load test report is still missing. Best regards, IT security
Four days newer than the plan and from the team that grants the approval.
What saves Friday?
According to test report T-07, 12 of 12 workflow tests have already passed.
Original project status: the plan expects the approval on Monday.
Nothing changed yet.What may an external AI see of this?
A model is to draft a status report for the project lead from the message. Choose which path the text may take.
Original IT security sentence with sender and reason (155 characters).
What does a single message change across the whole project?
According to the plan, the pilot starts on Fri 22 Nov. Next to it lies a new message from IT security.
- Gather knowledge
- Explore the connections
- Take control
Drag the new message into the project status – or tap “Place message”.
- needs – waits for its predecessor
- sets the date
- evidence – taken from the source
- outdated – replaced by a newer source
- parallel – runs independently
- changed by your action
Effect on the schedule
Place the message first – then the timeline shows what it shifts.
Project tree with responsibilities
IT security
Data team
Quality assurance
Business team
Project lead
A model can draft the status report – the scheduling logic calculates the date.
What may leave your company?
Simulation – no model is called, nothing is transmitted, all content fictitiousThe same task – a status report on the new message – on three paths. For each step you see where it runs, who receives something, exactly which content is released and what comes back.
Inside the company
- Original message and project plan
- Local model (simulated)
- Harness: rules, checks, log
- Scheduling logic without a model
No external release on this path
Service A
commercial AI service · fictitious, simulated- 1/3
Draft the status report
open- Where it runs
- –
- Recipient
- –
- Released content
- –
- Result (simulated)
- –
- 2/3
Short version for the steering committee
open- Where it runs
- –
- Recipient
- –
- Released content
- –
- Result (simulated)
- –
- 3/3
Version for the partner in German
open- Where it runs
- –
- Recipient
- –
- Released content
- –
- Result (simulated)
- –
What the harness rules decide
- Original messages, names and reasons do not leave the company; only sanitised wording goes out.
- An external hand-over only happens with a valid release. After a withdrawal there is no new hand-over.
- Without a release the local model takes over what it can do; everything else waits visibly.
- Dates are calculated by the scheduling logic, not by a model. Every hand-over is logged with recipient and scope.
What people decide
- Whether and for what external processing is released – and when the release ends (your company, e.g. data protection and IT leads).
- Which countermeasure applies (project lead; currently: {cm}).
- Whether a report is sent (project lead).
History (simulated)
- Nothing run yet.
Which approval regularly holds up a project for you?
Outline your own case in the short brief – three details are enough. Nothing is taken over from this simulation.
One shared plan.
Waiting for parts1
Done1
Today3
Knowledge with a source.
„Could you bring commissioning forward to Thursday?“
Benefit: the application checks the project plan, shows the source and prepares a reply and a task – you decide.
Nothing is sent or stored. Everything runs locally in this page.
Project plan P-2041 · Conveyor system hall 3
- Conveyor installationcompleted
- Electrical inspection – technical approvalopen · owner: electrician
- Commissioningplanned Friday · 1 day buffer
- Operator trainingFriday afternoon
Result of the check: Thursday is possible in the schedule. The technical approval of the electrical inspection is still missing.
Deadline changed – your edited draft stays as it is.
- Approve test report conveyor 2
- Send training documents to Hansen
Signals into action.
Discuss a similar workflow with us.
Which decision costs your team too much coordination? Prepare your request in a few minutes – if you like, with a short brief in three answers.
Wilkens Engineering · technical lead: Dirk Wilkens · Kiel