Operations
How ME intends to run things that must not stop.
Philosophy, not a schedule. ME operates nothing around the clock today, and this page holds no staffing, rota, incident or live system data.
Running continuously
Round the clock, eventually
Once there is something that must not stop.
Eight hour shifts with overlap
A handoff is a conversation, not a note.
A named incident commander
One person at a time, and everyone knows who.
On call specialists
Depth on call rather than on shift.
Independent safety and red teams
Checkers do not report to the checked.
Human override
Works with Carl unavailable or wrong.
Fatigue and two person rules
Bounded hours. Critical actions need two people.
Drills and post incident reviews
Emergencies practised on ordinary days.
Breaks
Breaks are paid, scheduled and mandatory.
- Two paid fifteen minute breaks and a paid thirty minute meal break per shift
- Mandatory. A break nobody takes is a policy nobody has
- Carl proposes staggered schedules, a supervisor can change them
- Coverage handed off before anyone leaves a critical post
Tired people miss things.
Incident handling
A short, boring process, followed every time.
- 01
Written handoff
Structured, every shift change.
- 02
Overlap, extended when needed
Fifteen to thirty minutes. The clock does not end it.
- 03
Joint command during transitions
Transferred and accepted, never assumed.
- 04
Closing needs agreement
Incident commander and technical lead both.
- 05
Review, then tracked follow up
Actions become tracked tasks.
- 06
Overdue safety work escalates
Automatically. Nothing depends on remembering.
What a written handoff contains
A document, not a conversation somebody remembers.
- Active incidents, and who holds command
- Unfinished tasks, and where they were left
- Unusual behaviour, including what was not chased
- Decisions made, and why
- Risks and watch items
- Follow up owners, by name
Cameras and machine safety
Design intent. No camera system exists.
- Where machines and people share space: floors, labs, plant, loading
- Never in private spaces. Bathrooms and changing areas, no exceptions
- Safety, not surveillance of people's work
- Carl may eventually stop an affected machine on a clear hazard
- Restart needs both: Carl verifying the hazard is gone, and a person authorising
Alerts go to the people who can act
Design notes only. No alert system has been built.
- Not everyone by default. Broadcasting is a deliberate choice
- Every alert says why this person, and what action
- Three answers: accept, need backup, unable
- Escalation is a chain, not a retry
- Shared displays show safe instructions only, never incident detail
- A site can resolve a local alert with central systems down
- An offline manual panel that does not need Carl