Phase 1 prototype · Phase 2A corrective verification · SYNTHETIC DEMONSTRATION DATA
Integrated Preventive Readiness
Acting role — demonstration device only, not an authorization mechanism
Superintendent: What will be ready across my area, and what must be resequenced?
Role journeys
No universal 24-tab surface — each role sees only its decision scope
Supervisor / Field
Can my crew start, and if not, who owns the blocker?
Journey
- Open shift lookahead filtered to own crew and location
- Open Job Card → enabling conditions and missing items only
- Confirm or reject SYSTEM_PROPOSED preventive package items in the field
- Run IPERC Continuo field confirmation before execution
- Escalate blocker to named owner — never self-release
May confirm
- · IPERC field hazard confirmation
- · Preventive package item confirmation
- · Sign-on record
May not
- · Authorize PETAR
- · Override SIMOPS STOP
- · Change canonical location structure
Superintendent
ACTINGWhat will be ready across my area, and what must be resequenced?
Journey
- Shift + 72h lookahead across all disciplines
- Location operational context → concurrent work set
- Review cumulative SIMOPS determinants and resequencing options
- Assign blocker owners and required-by dates
May confirm
- · Blocker ownership assignment
- · Sequence change request
May not
- · Confirm ES&H critical control adequacy
- · Release expired competency
- · Authorize isolation
ES&H
Are critical controls and risk context valid for what is actually happening there?
Journey
- Location Critical Risk Context and SIMOPS interaction risk
- IPERC Continuo — predicted vs field-confirmed hazards
- Critical control verification status and Life Critical exposure
- PETAR review routing (review ≠ authorization)
May confirm
- · Critical control verification
- · IPERC review
- · PETAR technical review
May not
- · Grant work authorization
- · Waive a mandatory control
- · Edit canonical location register
Functional Owner
Are the requirements in my discipline correctly applied and current?
Journey
- Applicability decisions produced by PACE for own requirement family
- Requirement version pinning and supersession impact
- Unclassified requirement queue (fails closed until classified)
May confirm
- · Requirement classification
- · Applicability exception with evidence
May not
- · Authorize work
- · Approve SIMOPS
- · Assign stewardship roles
Project Controls
What is the forecast readiness of the plan, and what is at risk?
Journey
- Forecast readiness across the execution window
- Expiry horizon: competencies, certificates, permits, documents
- Blocker ageing and ownership
May confirm
- · Required-by date
- · Plan alignment note
May not
- · Change readiness verdicts
- · Confirm controls
- · Authorize work
Management Assurance
Can any decision be reconstructed exactly as it was made?
Journey
- Decision register with pinned inputs and versions
- Evidence chain: source, version, decision, owner, history
- Prototype Review Register and open ADRs
May confirm
- · Assurance observation
- · Finding disposition (recommendation only)
May not
- · Alter pinned decisions
- · Delete evidence
- · Authorize work
Governance Administrator
Is the governance configuration complete, and where is it failing closed?
Journey
- Stewardship role assignment per location
- Mapping states and unresolved federation identities
- Classification governance (no hard-coded criticality)
- Inheritance policy configuration
May confirm
- · Stewardship assignment
- · Mapping validation
- · Inheritance policy
May not
- · Authorize work
- · Confirm field hazards
- · Bypass DISABLED_SAFE
Role selection is a demonstration device. It does not grant, imply or substitute operational authority.