Module · future regulated scope
Watches the course. Recommends a hold. Never touches a beam.
Delivery monitoring is the highest-risk thing in this platform, so it is also the most tightly bounded. It compares what was approved against what is being delivered, at every fraction, and it can ask for a hold. Starting, stopping and authorising treatment happen where they already happen.
A course drifts slowly, and the drift is visible in data nobody reviews daily
Between the approved plan and the last fraction there are weeks of setup images, shifts, interruptions and small deviations. Each one is individually unremarkable. The pattern is what matters — a shift in the same direction on consecutive days, an imaging frequency that quietly dropped, a plan version that changed without an approval. A monitor that looks at every fraction sees the pattern on the day it forms.
What the module does
- Verifies identity
- The delivered plan hash is compared against the immutable approved plan hash at every fraction. A difference is a stop condition.
- Confirms prerequisites
- That all required approvals and QA are complete and current before a fraction is expected to proceed.
- Compares three states
- Scheduled, approved and delivered parameters, including machine, accessories and fraction number.
- Reviews setup
- Setup image metadata and shifts against the institution's own thresholds, including patterns across consecutive fractions rather than single excursions.
- Tracks the course
- Interruptions, imaging frequency, cumulative fractions and unexpected plan changes.
- Recommends a hold
- When a required condition is missing or a pattern crosses the institution's threshold, it raises a safe hold recommendation into the existing treatment workflow and records it.
What it does not do
Boundaries of this module
- Command beam-on. There is no such control, and there never will be.
- Write to the record-and-verify system or bypass a machine interlock.
- Apply a hold on its own authority. It recommends; the licensed treatment workflow applies.
- Modify a plan or a schedule.
See it working
The synthetic on-treatment case is at fraction 7 of 20 with a safe hold active: two consecutive setup excursions in the same direction, where the pathway permits one. The plan hash matched on all seven delivered fractions, and that is stated too.
This is future scope, and it carries its own risk case