Phase 6A — Mesa 3 · Field Execution & Prospective Measurement Readiness

Value: CV-07 Pilot corridor (frozen Phase 6 Pilot scope)

Source: Phase 6 Pilot Definition Baseline (frozen)

Value: Concentrator — material handling

Source: Phase 6 Pilot Definition Baseline

Value: NOT_YET_AVAILABLE — field sector designation not supplied by Construction

Source: Construction Management (pending)

Value: Transfer Tower 01 (candidate, unverified in field)

Source: Prototype scenario — not field-verified

Value: Conveying / transfer system CV-07

Source: Phase 6 Pilot Definition Baseline

Value: NOT_YET_AVAILABLE — subsystem breakdown not confirmed against commissioning register

Source: Commissioning (pending)

Value: Candidate workfront at transfer tower level +12 m; physical verification not performed

Source: Field verification required

Value: DEPENDENCY_HELD — federated canonical Location register unconfirmed (Mesa 1 / ADR-14 Option C)

Source: Mesa 1 BC-01 / ADR-14 stewardship

Value: NOT_YET_AVAILABLE — operational location reference not issued by Location steward

Source: Location steward (vacant — Mesa 2 BC-04)

Value: NOT_YET_AVAILABLE — no field-confirmed work package identifier released for Pilot window

Source: Work Control / Q4 (BC-01)

Value: NOT_YET_AVAILABLE — JobCards must not be fabricated to enable Pilot execution

Source: Work Control / Q4 (BC-01, BC-03)

Value: Mechanical / Electrical / Instrumentation expected; actual discipline mix unconfirmed

Source: Construction planning (pending)

Value: NOT_YET_AVAILABLE — crew rosters not supplied

Source: Construction / Contractor supervision

Value: NOT_YET_AVAILABLE — shift pattern for Pilot window not confirmed

Source: Construction planning

Value: NOT_YET_AVAILABLE — no planned window issued; Pilot execution remains on HOLD

Source: P6 schedule (BC-01)

Value: NOT_APPLICABLE_YET — no execution has occurred

Source: n/a

Value: NOT_YET_AVAILABLE — named field supervisor not nominated

Source: Construction (Mesa 2 dependency)

Value: NOT_YET_AVAILABLE — accountable field owner for the Pilot workfront not nominated

Source: Construction Management

Value: DesignEvidence only. No operational field record has been received.

Source: Mesa 3 evidence queue

Condition: A real, identifiable and governed WorkLocation exists for the CV-07 workfront

Authoritative source: Federated canonical Location register (ADR-14 Option C)

Competent owner: Location Steward

Required by: Before any readiness decision

Evidence ref: —

Validity basis: Steward-issued canonical reference with effective date

Dependency: BC-01 (participation), BC-04 (stewardship)

Disposition: DEPENDENCY_HELD — not a field failure

Condition: Real work demand exists with identifiable WorkPackage and JobCards

Authoritative source: Work control system of record

Competent owner: Work Control Lead

Required by: Before Pilot field execution

Evidence ref: —

Validity basis: Extract from authoritative work-control record for the Pilot window

Dependency: BC-01, BC-03

Disposition: REMAINS_OPEN — evidence acquisition required

Condition: Applicable released engineering (drawings, specifications) exists at pinned versions

Authoritative source: Document management system of record

Competent owner: Engineering Document Controller

Required by: Package preparation

Evidence ref: —

Validity basis: Version-pinned document reference with revision and status

Dependency: BC-01

Disposition: REMAINS_OPEN

Condition: Required materials are identified, available and released to the workfront

Authoritative source: Materials management record

Competent owner: Materials / Warehouse Lead

Required by: Before mobilisation

Evidence ref: —

Validity basis: Reservation/issue record against the work package

Dependency: BC-01

Disposition: REMAINS_OPEN

Condition: Required construction equipment is available, certified and allocated

Authoritative source: Equipment register / certification record

Competent owner: Construction Equipment Lead

Required by: Before mobilisation

Evidence ref: —

Validity basis: Certification validity dates within execution window

Dependency: —

Disposition: REMAINS_OPEN

Condition: Required tooling, including special tooling, is available and inspection-valid

Authoritative source: Tool control / inspection record

Competent owner: Site Tool Controller

Required by: Before mobilisation

Evidence ref: —

Validity basis: Inspection tag validity

Dependency: —

Disposition: REMAINS_OPEN

Condition: Crew composition and headcount for the planned window are known and assigned

Authoritative source: Contractor roster

Competent owner: Contractor Superintendent

Required by: Before planning lock

Evidence ref: —

Validity basis: Roster valid for the specific shift and window

Dependency: BC-02 (identity)

Disposition: REMAINS_OPEN

Condition: Each assigned worker holds valid, in-date competency for the assigned task

Authoritative source: Competency system of record

Competent owner: Training & Competency Lead

Required by: Before task assignment

Evidence ref: —

Validity basis: Competency expiry after planned execution end

Dependency: BC-01, BC-02, BC-05 (data minimisation)

Disposition: REMAINS_OPEN

Condition: Medical fitness / habilitation status valid for the task and location

Authoritative source: Occupational health record (minimised: status only)

Competent owner: Occupational Health

Required by: Before task assignment

Evidence ref: —

Validity basis: Status flag with validity date; no clinical data transferred

Dependency: BC-05

Disposition: REMAINS_OPEN — data minimisation constraint applies

Condition: Area is physically accessible, prepared and released for the planned work

Authoritative source: Area release / access control record

Competent owner: Area Construction Superintendent

Required by: Before mobilisation

Evidence ref: —

Validity basis: Signed area release valid for the window

Dependency: —

Disposition: REMAINS_OPEN

Condition: Environmental conditions (wind, storm, heat, dust, visibility) within operating limits at execution

Authoritative source: Site meteorological / environmental monitoring

Competent owner: ES&H Lead

Required by: At execution, continuously

Evidence ref: —

Validity basis: Reading timestamp within the validity window of the decision

Dependency: BC-01

Disposition: REMAINS_OPEN

Condition: Client or owner release exists where the system or area is under owner control

Authoritative source: Owner release register

Competent owner: Client Interface Manager

Required by: Before entering owner-controlled scope

Evidence ref: —

Validity basis: Release document with scope and validity

Dependency: —

Disposition: REMAINS_OPEN

Condition: Transport, lifting and delivery logistics to the workfront are arranged

Authoritative source: Logistics plan

Competent owner: Site Logistics Coordinator

Required by: Before mobilisation

Evidence ref: —

Validity basis: Booking confirmation for the window

Dependency: —

Disposition: REMAINS_OPEN

Condition: Concurrent work at the Location is known and cumulatively evaluated (CUM-1…CUM-7)

Authoritative source: Location concurrent work set (federated)

Competent owner: ES&H / SIMOPS Coordinator

Required by: Before authorization and at execution

Evidence ref: —

Validity basis: Concurrent set complete for the Location and time overlap

Dependency: BC-01, BC-04

Disposition: REMAINS_OPEN — completeness of the concurrent set cannot be evidenced

Condition: Active operational restrictions, exclusion zones and temporary modifications are known

Authoritative source: Restriction / temporary modification register (ADR-17)

Competent owner: Operations Interface Lead

Required by: Before authorization

Evidence ref: —

Validity basis: Register current at decision time

Dependency: BC-03 (ADR-17 lifecycle authority)

Disposition: REMAINS_OPEN

Condition: Emergency response, rescue and evacuation provisions valid for the workfront

Authoritative source: Emergency response plan / ES&H record

Competent owner: Emergency Response Coordinator

Required by: Before execution

Evidence ref: —

Validity basis: Plan applicable to the location, task and shift

Dependency: —

Disposition: REMAINS_OPEN

Condition: Critical Control verification participation exists for activities exposed to critical risk

Authoritative source: Critical control system (unelected — BC-06 Path A/B)

Competent owner: Critical Risk Owner (Mesa 1 authority)

Required by: Before execution of critical-risk activity

Evidence ref: —

Validity basis: Real verification record; simulation is inadmissible

Dependency: BC-06

Disposition: CriticalControlFieldDependency = HELD_BY_MESA_1

Basis: Candidate workfront described; no field walk-down record received.

Basis: DEPENDENCY_HELD — federated canonical Location register unconfirmed (ADR-14 Option C, Mesa 1).

Basis: No steward-issued operational reference; Location steward unassigned (Mesa 2).

Basis: Boundary definition requires steward issuance and field confirmation.

Basis: Access control record not supplied.

Basis: No concurrent work extract received; cannot be inferred.

Basis: Schedule participation unresolved (BC-01).

Basis: Field inventory not performed.

Basis: Restriction register participation unresolved.

Basis: Monitoring feed not connected; wind limit logic exists as design only.

Basis: See SIMOPS field context; completeness unprovable today.

Basis: Lessons source not nominated.

Note: Authoritative identifier required from Work Control.

Note: Must originate in the system of record; fabrication prohibited.

Note: Multi-discipline expected at one Location (ADR-14 container behaviour).

Note: Scope statement per JobCard required.

Note: Schedule participation unresolved (BC-01).

Note: As above.

Note: Roster not supplied.

Note: Allocation record not supplied.

Note: Control set derives from applicability rules whose governance is unresolved.

Note: DEPENDENCY_HELD (canonical reference).

Note: P6 activity ID linkage not evidenced.

Meaning: Risk of the individual activity in isolation.

State: Model defined (DesignEvidence); no field data.

Meaning: Cumulative risk of the Location as an operational container, independent of any single activity.

State: Model defined; no field data.

Meaning: Risk arising from interaction between concurrent activities (CUM-1…CUM-7).

State: Model defined; no field data.

Finding: PLAUSIBLE — the corridor involves stored/mechanical energy, working at height, lifting and isolation interfaces. Definitive determination requires the Critical Risk Owner, who is not yet nominated.

Finding: Isolation and energy-state changes, lifting operations, work at height at the transfer tower, and any confined or restricted access task within the Location container.

Finding: YES — where a critical control applies, verification is a field act with an attributable verifier; a system flag is not verification.

Finding: A named critical risk owner, an elected Path A source of verification records (or a formally recorded Path B rescope), verifier identity through real IAM (BC-02), and a verification record retrievable for evidence reconstruction.

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED (delivery would be a contamination risk — see anti-contamination register)

Current workflow: Existing paper/hybrid preparation workflow (to be characterised by passive observation)

Evidence ref: —

Dependency: Mesa 2 (assignment), Mesa 1 BC-02 (identity)

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED

Current workflow: Existing shift planning routine

Evidence ref: —

Dependency: Mesa 2

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED

Current workflow: Existing crew briefing routine

Evidence ref: —

Dependency: Mesa 2

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED

Current workflow: Existing task execution routine

Evidence ref: —

Dependency: Mesa 1 BC-02, BC-05

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED

Current workflow: Existing SIMOPS coordination routine

Evidence ref: —

Dependency: Mesa 2 BC-04

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED

Current workflow: None — design team is currently de-facto support

Evidence ref: —

Dependency: Mesa 2 BC-07

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED

Current workflow: Existing area release routine

Evidence ref: —

Dependency: Mesa 2

Actual availability: NOT_YET_AVAILABLE

Shift: NOT_YET_AVAILABLE

Training status: NOT_DELIVERED

Current workflow: Existing owner release routine

Evidence ref: —

Dependency: Mesa 1 BC-03, Mesa 2 BC-04

Operational definition: Elapsed working time from work package initiation to supervisor-declared prepared, for packages in the CV-07 field scope.

Measurement window: PackageInitiated → PreparedDeclared

Source: Work control record (authoritative)

Collection method: Event extract with supervisor confirmation

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per package

Timestamp basis: System event timestamp, site timezone, clock source to be validated

Exclusions: Packages outside CV-07 scope; packages cancelled before preparation.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Elapsed time between submission for authorization and the authorization decision.

Measurement window: Submitted → Approved

Source: Work control transaction log

Collection method: Event extract

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per submission

Timestamp basis: Transaction log timestamp; clock reliability unvalidated

Exclusions: Submissions withdrawn by the originator before review.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Time between a restriction becoming knowable and it being recorded against the package.

Measurement window: RestrictionKnowable → RestrictionRecorded

Source: Restriction register + supervisor log

Collection method: Prospective log entry at time of detection (no retrospective reconstruction)

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per restriction

Timestamp basis: Manual log timestamp; requires observer discipline

Exclusions: Restrictions raised outside the CV-07 Location container.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Time from blocker raised to blocker closed, recorded by blocker type and accountable owner.

Measurement window: BlockerRaised → BlockerClosed

Source: Supervisor log / work control

Collection method: Prospective log

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per blocker

Timestamp basis: Log timestamp

Exclusions: Blockers not affecting CV-07 scope work.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Preparation activities repeated because of defective or superseded preparation. Construction rework is explicitly excluded.

Measurement window: ReworkTriggered → ReworkCompleted

Source: Supervisor log

Collection method: Prospective log with cause code

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per occurrence

Timestamp basis: Log timestamp

Exclusions: Construction/physical rework; scope-change-driven repreparation recorded separately.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Count of occurrences where the same datum is entered into more than one system during preparation.

Measurement window: ObservationSessionStart → ObservationSessionEnd

Source: Structured passive observation study

Collection method: Observer tally sheet (non-intrusive; observer does not advise or prompt)

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per observed session

Timestamp basis: Observer clock, synchronised to site time

Exclusions: Entries made for training or testing purposes.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Time spent locating a document and confirming its version validity during preparation.

Measurement window: SearchStart → VersionConfirmed

Source: Passive observation study

Collection method: Timed observation

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per observed session

Timestamp basis: Observer clock

Exclusions: Searches unrelated to the observed package.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Count of field-to-office clarification contacts arising from preparation ambiguity.

Measurement window: ClarificationRaised → ClarificationAnswered

Source: Shift log

Collection method: Prospective log

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per shift

Timestamp basis: Shift log timestamp

Exclusions: Commercial or HR queries.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: SIMOPS interactions first identified at or after mobilisation rather than during planning.

Measurement window: InteractionExists → InteractionIdentified

Source: ES&H / shift records

Collection method: Prospective log

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per occurrence

Timestamp basis: Record timestamp

Exclusions: Interactions outside the CV-07 Location container.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Difference between planned and actual start at the workface, with primary delay cause recorded at the time of occurrence.

Measurement window: PlannedStart → WorkStarted

Source: Field supervision record

Collection method: Prospective log with cause code

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per job card start

Timestamp basis: Supervisor record; workface clock

Exclusions: Starts cancelled before mobilisation.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Proportion of packages authorized on first submission without returned rework.

Measurement window: Submitted → Approved or Returned

Source: Work control transaction log

Collection method: Event extract

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per period

Timestamp basis: Transaction log

Exclusions: Administrative resubmissions with no content change.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Operational definition: Time a package waits on an authority holder, separated from time waiting on a technical condition.

Measurement window: QueuedForAuthority → AuthorityDecision

Source: Work control transaction log

Collection method: Event extract with wait-reason classification

Owner: NOT_YET_CONFIRMED — measurement owner nomination pending

Frequency: Per submission

Timestamp basis: Transaction log

Exclusions: Waits caused by planned shift boundaries where no authority holder is rostered — recorded separately.

Correction rule: Corrections permitted only with recorded reason, corrector identity and timestamp; original value retained and never overwritten.

Missing data rule: Missing values are recorded as MISSING with reason; they are never imputed, averaged or back-filled.

Concurrent constraint rule: Where more than one constraint is active in the same interval, apply the concurrent constraint attribution model (Section K); never double-count time or value.

Attribution rule: Attribution recorded as PRIMARY / CONTRIBUTORY / CONCURRENT / SHARED_CAUSATION / UNATTRIBUTED per governed rule; false precision prohibited.

Evidence ref: —

Definition: Work placed into a schedule with a planned window.

Definition: Supervisor declares preparation complete.

Definition: Package submitted for review or authorization.

Definition: Technical review performed.

Definition: Package returned for correction.

Definition: Authority decision recorded.

Definition: Work released to the field.

Definition: Physical work commences at the workface.

Definition: Work suspended for a recorded cause.

Definition: Work resumes after a hold.

Definition: Work completed and recorded.

Meaning: Reduction in elapsed time to reach the same process event, attributable to a specific cause.

Meaning: Time no longer consumed by a person on a task, which may or may not be redeployed.

Meaning: Time actually converted into productive workface activity, evidenced at the workface.

Use: One constraint demonstrably determined the outcome and would have done so alone.

Use: A constraint materially extended the outcome but was not sufficient alone.

Use: Two or more constraints were independently sufficient over the same interval; time is counted once.

Use: Causation is genuinely joint and cannot be separated with the available evidence; the interval is recorded once and flagged.

Use: No defensible causal basis exists; the interval is retained but excluded from any attributed value claim.

Scenario: Material unavailable and area not released over the same 4-hour interval.

Treatment: CONCURRENT — 4 hours counted once; both causes recorded; no 8-hour total.

Scenario: Authorization waiting on an authority holder while a document version query is also open.

Treatment: PRIMARY = authority wait if work could not proceed regardless; document query recorded as CONTRIBUTORY.

Scenario: Start delay with no recorded cause.

Treatment: UNATTRIBUTED — retained in elapsed data, excluded from attributed value.

Potential baseline impact: Directly changes the preparation and decision method being measured; irreversible contamination of BEFORE.

Decision authority: Pilot Sponsor + Measurement Owner (both unassigned)

Restriction: PROHIBITED until prospective BEFORE collection has formally commenced and the baseline window is declared closed by competent authority.

Evidence: No exposure has occurred.

Potential baseline impact: Anticipation effects and behavioural change in the measured population.

Decision authority: Pilot Sponsor

Restriction: PROHIBITED for personnel inside the measured population; permitted only for non-measured governance audiences with attendance recorded.

Evidence: None conducted.

Potential baseline impact: Alters the very process under baseline observation.

Decision authority: Pilot Sponsor + ES&H

Restriction: Material-preparation permitted; delivery to the measured population PROHIBITED before baseline start.

Evidence: Not delivered.

Potential baseline impact: Introduces new detection lead time, corrupting M-03 and M-09.

Decision authority: Measurement Owner

Restriction: PROHIBITED.

Evidence: Not enabled.

Potential baseline impact: Changes late-detection rate and coordination effort under measurement.

Decision authority: ES&H Lead + Measurement Owner

Restriction: PROHIBITED where it changes the current coordination method; passive recording of the existing routine is permitted.

Evidence: Not introduced.

Potential baseline impact: Directly reduces measured preparation and duplicate-entry effort.

Decision authority: Measurement Owner

Restriction: PROHIBITED.

Evidence: Not enabled.

Potential baseline impact: Changes information availability and decision timing.

Decision authority: Pilot Sponsor

Restriction: PROHIBITED for the measured population; governance-only dashboards permitted where field users have no access.

Evidence: None deployed to field.

Potential baseline impact: Changes the decision sequence being measured.

Decision authority: Work Control Lead + Measurement Owner

Restriction: PROHIBITED.

Evidence: Not enabled.

Potential baseline impact: Replaces the artefact whose handling time is being measured.

Decision authority: Work Control Lead

Restriction: PROHIBITED.

Evidence: Not introduced.

Potential baseline impact: Alters hazard identification behaviour and timing.

Decision authority: ES&H Lead

Restriction: PROHIBITED.

Evidence: Not introduced.

Potential baseline impact: Changes planning behaviour and constraint detection lead time.

Decision authority: Measurement Owner

Restriction: PROHIBITED.

Evidence: Not enabled.

Potential baseline impact: Changes clarification volume and resolution time (M-08, M-04).

Decision authority: Support Owner (unassigned — Mesa 2 BC-07)

Restriction: PROHIBITED before baseline start; existing support arrangements remain unchanged.

Evidence: No new support deployed.

Potential baseline impact: Low, but a Hawthorne effect is possible; mitigated by observation protocol and by observing across the full baseline window.

Decision authority: Measurement Owner

Restriction: ALLOWED as NON_INTRUSIVE_PREPARATION. Observer must not advise, prompt, correct or expedite. Effect noted as a known limitation.

Evidence: Protocol defined (DesignEvidence).

Potential baseline impact: Produces an unattributable baseline and invalidates causal claims.

Decision authority: Competent measurement authority

Restriction: PROHIBITED as a baseline. Permitted only as formally approved supplementary reference, explicitly labelled as non-baseline.

Evidence: Not used.

Note: All 12 metrics have operational definitions, units, start/end events, exclusions and data-quality rules.

Note: No measurement source has confirmed participation; work-control and schedule participation unresolved (BC-01).

Note: No measurement owner nominated for any metric (Mesa 2 dependency).

Note: Clock source, timezone handling and event fidelity not validated against any real extract.

Note: MISSING recorded with reason; imputation prohibited.

Note: Corrections attributable, original retained.

Note: Concurrent attribution model defined; ratification by competent authority pending.

Note: No Pilot exposure has occurred; anti-contamination register default is NO.

Note: CV-07 field scope has unresolved WorkPackage, JobCard, crew, window and canonical Location attributes.

Note: BC-05 data minimisation and retention determination outstanding (Mesa 1), affecting competency, fitness and observation data.

Basis: No authoritative work-control extract received.

Basis: Physical context describable; canonical identity unresolved (Mesa 1 / ADR-14).

Basis: 17 prerequisite domains defined; 0 carry operational evidence.

Basis: No accountable field owner nominated (Mesa 2 dependency).

Basis: 12 frozen metrics with operational definitions and data-quality rules (DesignEvidence).

Basis: 5 of 10 collection readiness conditions unmet; collection may not commence.

Input: MissingMandatoryPrerequisite (any non-compensable domain unresolved)

Note: No partial authorization, no downgrade to CONDITIONAL, no state written to any source system.

Input: PilotExposureBeforeBaseline (attempted exposure of Pilot capability to a measured field user)

Note: BC09Protection = ACTIVE. The request is refused and recorded in the anti-contamination register; no exposure occurs.

Input: Request to reconstruct BEFORE from historical averages to accelerate Pilot

Note: Reconstruction is admissible only as formally approved supplementary reference, never as baseline.

Input: Request to elect BC-06 Path A or Path B from Mesa 3

Note: BC-06 election remains Mesa 1 authority.

Expected behaviour: Readiness resolves NOT_READY / HOLD for every JobCard in the container; no substitution of an alternative Location; sideEffect = NONE.

Expected behaviour: All dependent readiness context is invalidated, not carried forward; measurement records the cancellation event rather than deleting the case.

Expected behaviour: Competency and fitness re-evaluation is mandatory; prior confirmations do not transfer to new personnel.

Expected behaviour: Non-compensable prerequisite unresolved → READY NOT PERMITTED; no averaging against satisfied domains.

Expected behaviour: HOLD with named blocker and owner; no silent substitution of an equivalent material without engineering authority.

Expected behaviour: Immediate STOP/HOLD on affected activities at the Location; restriction applies to the container, not only the triggering activity.

Expected behaviour: HOLD; owner release cannot be assumed from prior releases or from schedule presence.

Expected behaviour: Location-level re-evaluation triggered (CUM rules); a previously valid pairwise PASS does not survive a changed concurrent set.

Expected behaviour: Activity requiring critical control cannot be READY; dependency recorded as HELD_BY_MESA_1; no simulated verification.

Expected behaviour: Affected metric is recorded as source-unavailable with reason; no proxy substitution, no historical back-fill, no fabricated value.

Can progress independently: YES

Can close field condition: NO

Can execute Pilot: NO

Evidence required: Authorized participation of the Location source and a steward-issued canonical reference for CV-07.

Can progress independently: YES

Can close field condition: NO

Can execute Pilot: NO

Evidence required: Authorized work-control extract for the Pilot window.

Can progress independently: YES

Can close field condition: NO

Can execute Pilot: NO

Evidence required: Real identity resolution for named field participants with role assertions.

Can progress independently: YES

Can close field condition: NO

Can execute Pilot: NO

Evidence required: Ratified CV-07 transition sets and named lifecycle authority.

Can progress independently: YES

Can close field condition: NO

Can execute Pilot: NO

Evidence required: Approved minimisation, retention and privacy determination covering measurement and observation data.

Can progress independently: NO

Can close field condition: NO

Can execute Pilot: NO

Evidence required: Recorded competent-authority election of Path A (real critical control) or Path B (formal rescope) with residual risk.

Can progress independently: YES

Can close field condition: NO

Can execute Pilot: NO

Evidence required: Named, documented accountabilities including Location steward and measurement owner.

Can progress independently: YES

Can close field condition: YES

Can execute Pilot: NO

Evidence required: Support model staffed and demonstrably independent of the design team — noting new support must not be introduced into the measured population before baseline start.

DesignEvidence: Field readiness model across 17 non-aggregated domains, prerequisite register, negative scenarios and failure behaviour defined.

OperationalClosureEvidence: None. No field-verified workfront, owner, window, crew or prerequisite confirmation received.

Note: CLOSED_WITH_CONTROL remains available only where competent authority explicitly accepts a named external dependency; no such acceptance exists today.

DesignEvidence: 12 frozen metrics operationally defined, event model, attribution model, baseline governance and anti-contamination register.

OperationalClosureEvidence: None. Collection has not commenced; sources, owners and timestamp basis unconfirmed.

Note: Collection is not even READY_TO_COLLECT: 5 of 10 readiness-test conditions are unmet. BC-09 is never closed on design readiness alone.

Request: Nominate the accountable Field Owner and Supervisor for the CV-07 Pilot workfront, with position and authority basis.

Acceptance criterion: Named position holder with documented accountability and effective date.

Request: Provide the authoritative WorkPackage and JobCard extract for the candidate CV-07 window (no fabrication, no reformatting).

Acceptance criterion: System extract with identifiers, scope, discipline, planned dates and schedule reference.

Request: Issue the canonical Location reference for the CV-07 container under ADR-14 Option C, with boundary definition.

Acceptance criterion: Steward-issued canonical reference with effective date and boundary description.

Request: Confirm planned execution window, shift pattern, discipline mix and crew composition.

Acceptance criterion: Planned window and roster valid for the specific shifts.

Request: Provide area release, access conditions and physical walk-down confirmation for the workfront.

Acceptance criterion: Signed area release plus dated walk-down record.

Request: Confirm released engineering applicable to the workfront at pinned revisions.

Acceptance criterion: Document list with revision, status and effective date.

Request: Confirm material availability and reservation against the work package.

Acceptance criterion: Reservation or issue record referencing the package.

Request: Confirm equipment allocation and certification validity, and tool inspection validity, for the window.

Acceptance criterion: Certification and inspection validity dates spanning the window.

Request: Confirm the minimised competency and fitness status feed (status and validity only) for assigned personnel.

Acceptance criterion: Status-only feed compliant with the BC-05 minimisation determination.

Request: Provide the concurrent work set for the CV-07 Location container over the candidate window, including planned and active work.

Acceptance criterion: Complete concurrent set with time overlaps and interaction attributes; completeness attested by ES&H.

Request: Provide active operational restrictions, exclusion zones and temporary modifications applicable to the container.

Acceptance criterion: Register extract current at the date of issue.

Request: Confirm whether owner release is required for the workfront and, if so, provide the release.

Acceptance criterion: Written determination plus release document where applicable.

Request: Confirm emergency response, rescue and evacuation provisions valid for the workfront and shift.

Acceptance criterion: Plan reference applicable to the location and task set.

Request: Nominate the Measurement Owner and the competent reviewer for baseline sufficiency.

Acceptance criterion: Named accountabilities with authority basis (Mesa 2 dependency, recorded not absorbed).

Request: Confirm availability of the process events (Scheduled…Completed) and provide a sample extract for timestamp validation.

Acceptance criterion: Sample extract enabling clock-source, timezone and event-fidelity validation.

Request: Confirm source and owner for each of the 12 frozen metrics.

Acceptance criterion: 12 signed source/owner confirmations; partial confirmation does not advance the set.

Request: Ratify the concurrent constraint attribution rule before collection begins.

Acceptance criterion: Recorded ratification with authority and date.

Request: Confirm privacy and retention treatment for observation, competency and fitness data used in measurement.

Acceptance criterion: Approved determination covering the measurement data set.

Request: Formally declare the prospective BEFORE collection start, with the anti-contamination register accepted and in force.

Acceptance criterion: Dated declaration; collection start is the only route out of NOT_STARTED.

Issue: No accountable field owner exists for the Pilot workfront, so no party can be asked to confirm field prerequisites.

Authority: Construction Management / Pilot Sponsor

Risk: Evidence acquisition cannot start on the BC-08 lane.

Issue: Measurement owner unnamed while BC-09 is time-irreversible — every day without prospective capture is a day of baseline that cannot be recovered.

Authority: Pilot Sponsor

Risk: Schedule pressure may later be used to justify contaminating or reconstructing the baseline.

Issue: Pressure to demonstrate the Pilot to field users before baseline start.

Authority: Pilot Sponsor + Measurement Owner

Risk: Would trigger a BC09_CONTAMINATION_EVENT and require a new baseline window.

Issue: BC-06 Path A/B unelected, leaving critical-control field participation undefined for a corridor with plausible critical risks.

Authority: Mesa 1 — Critical Risk Owner

Risk: No Pilot field execution can be authorized for critical-risk activities.