Phase 6A — Evidence Request Execution Pack

Context — Phase 6A (CV-07 Pilot entry) — BC-01 cannot be retested without a declared participation mode per source.

Evidence Requested — Confirmed federated participation map per source and object class

Acceptance Need — Attributable participation declaration per source/object.

Not Requested — You are not asked to approve the readiness product, its rules or its user interface.

Submission — Architecture decision record or signed participation map, referenced by document number and revision.

Context — Phase 6A (CV-07 Pilot entry) — Q4 objects gate work authorization; unverifiable source must fail closed.

Evidence Requested — Participation mode, interface mechanism, authentication and failure behaviour for permit/JHA/isolation objects

Acceptance Need — Owner statement of mode + authority boundaries.

Not Requested — You are not asked to grant write-back or to change Q4 process.

Submission — Owner statement or interface specification with named signatory and date.

Context — Phase 6A (CV-07 Pilot entry) — Decision pinning depends on governed revision snapshots.

Evidence Requested — Document snapshot authority and revision-change notification behaviour

Acceptance Need — Owner confirmation of snapshot authority and validity window.

Not Requested — You are not asked to migrate documents or open bulk export.

Submission — Snapshot governance note referencing ADR-05 inputs.

Context — Phase 6A (CV-07 Pilot entry) — Forecast context requires a governed schedule source.

Evidence Requested — Look-ahead read participation and refresh cadence

Acceptance Need — Owner confirmation of read mode and cadence.

Not Requested — You are not asked to re-plan or to accept readiness forecasting logic.

Submission — Governed extract description or measurement plan with metric-level owner.

Context — Phase 6A (CV-07 Pilot entry) — Release gating consumes completion state.

Evidence Requested — Subsystem completion participation mode

Acceptance Need — Owner confirmation of participation mode.

Not Requested — You are not asked to alter completion certification.

Submission — Owner participation statement.

Context — Phase 6A (CV-07 Pilot entry) — No participation is real without IT authorization.

Evidence Requested — Enterprise interface hosting, network and data-movement authorization

Acceptance Need — IT authorization statement for the declared mechanisms.

Not Requested — You are not asked to endorse the functional design.

Submission — IT authorization record with named constraints.

Context — Phase 6A (CV-07 Pilot entry) — Authority enforcement must be enterprise-enforced, not prototype-simulated.

Evidence Requested — Identity provider, authentication method and Pilot identity provisioning plan

Acceptance Need — IAM owner confirmation + provisioned identity set.

Not Requested — You are not asked to approve application functionality.

Submission — IAM design/provisioning record plus controlled IAM-01→IAM-06 execution evidence.

Context — Phase 6A (CV-07 Pilot entry) — Attribute-based authority is unenforceable without a role source.

Evidence Requested — Role resolution source and mapping to area / activity / shift / risk scopes

Acceptance Need — Documented mapping from enterprise roles to authority scopes.

Not Requested — You are not asked to define operational roles yourself.

Submission — IAM design/provisioning record plus controlled IAM-01→IAM-06 execution evidence.

Context — Phase 6A (CV-07 Pilot entry) — Delegation must never widen scope; revocation must fail closed.

Evidence Requested — Delegation and revocation behaviour confirmation

Acceptance Need — Written enterprise behaviour statement.

Not Requested — You are not asked to accept UI-level denial as enforcement.

Submission — IAM design/provisioning record plus controlled IAM-01→IAM-06 execution evidence.

Context — Phase 6A (CV-07 Pilot entry) — Role resolution requires an authoritative person source.

Evidence Requested — Authoritative person-to-role source for Pilot population

Acceptance Need — HR confirmation of authoritative source and update cadence.

Not Requested — You are not asked to supply full HR records.

Submission — Source governance note and capacity/resourcing record.

Context — Phase 6A (CV-07 Pilot entry) — Lifecycle is defined by design and accepted by nobody.

Evidence Requested — Acceptance of lifecycle ownership and transition authority per object

Acceptance Need — Decision artefact per object class.

Not Requested — A process diagram is not requested; a decision artefact is.

Submission — Minuted governance decision artefact (not a process diagram).

Context — Phase 6A (CV-07 Pilot entry) — Prevents accidental duplication of Q4 authority.

Evidence Requested — Confirmation of transaction lifecycle authority boundaries at the federation edge

Acceptance Need — Owner confirmation of who may transition what.

Not Requested — You are not asked to cede any Q4 authority.

Submission — Owner statement or interface specification with named signatory and date.

Context — Phase 6A (CV-07 Pilot entry) — Vacant stewardship forces fail-closed HOLD in operation.

Evidence Requested — Named, authorized and available stewardship appointments (7 roles)

Acceptance Need — Appointment records with authorization and capacity.

Not Requested — Org-chart names without authorization are not requested.

Submission — Appointment records with authorization, delegate and capacity.

Context — Phase 6A (CV-07 Pilot entry) — Assignment without capacity is not stewardship.

Evidence Requested — Capacity allocation and SoD confirmation for stewardship roles

Acceptance Need — Capacity statement per role.

Not Requested — You are not asked to reorganize the project structure.

Submission — Source governance note and capacity/resourcing record.

Context — Phase 6A (CV-07 Pilot entry) — SoD breach would compromise authority separation.

Evidence Requested — Segregation-of-duties assessment for steward / owner combinations

Acceptance Need — Compliance SoD assessment.

Not Requested — Design-team self-assessment is not acceptable and is not requested.

Submission — Signed SoD assessment with any compensating controls named.

Context — Phase 6A (CV-07 Pilot entry) — Retention currently rests on a design proposal, not a legal basis.

Evidence Requested — Retention basis and period per material record class

Acceptance Need — Competent retention decision per class.

Not Requested — You are not asked to endorse design proposal RC-RET-01 as-is.

Submission — Retention schedule extract per record class.

Context — Phase 6A (CV-07 Pilot entry) — Person and health-adjacent data must be minimised by decision, not assumption.

Evidence Requested — Personal-data classification, minimum attribute and access scope decision

Acceptance Need — Privacy decision per class.

Not Requested — Full HR or health records are explicitly not requested.

Submission — Privacy decision / DPIA-equivalent record.

Context — Phase 6A (CV-07 Pilot entry) — Prevents duplication of medical records.

Evidence Requested — Confirmation that only a binary fitness flag may be consumed

Acceptance Need — Health owner confirmation of exposed attribute.

Not Requested — Medical records, diagnoses or restrictions detail are not requested.

Submission — Data-exposure statement naming the custodian.

Context — Phase 6A (CV-07 Pilot entry) — Path ambiguity propagates unresolved scope into BC-08 and Phase 7.

Evidence Requested — Formal election of PATH_A or PATH_B for critical control participation

Acceptance Need — Attributable path election.

Not Requested — You are not asked to choose Path B for convenience; ease is not a valid reason.

Submission — Attributable path election record (Path A authorization or Path B rescope record).

Context — Phase 6A (CV-07 Pilot entry) — Path A is unachievable without the owning system.

Evidence Requested — Source participation authorization for critical control verification records (Path A)

Acceptance Need — Owner participation confirmation.

Not Requested — You are not asked to change critical control verification practice.

Submission — Source participation authorization.

Context — Phase 6A (CV-07 Pilot entry) — Design-team dependency invalidates support sustainability.

Evidence Requested — Named L1 / L2 / L3 owners, operating window and escalation path

Acceptance Need — Staffing record with operating window.

Not Requested — Naming the design team as L2/L3 is not acceptable and is not requested.

Submission — Support model with named staff, plus drill preparation records.

Context — Phase 6A (CV-07 Pilot entry) — Support capability must be demonstrated, not described.

Evidence Requested — Execution of operational drills S-01 → S-06 by the real support function

Acceptance Need — Drill records with actor, outcome and time.

Not Requested — Drills are not to be executed or claimed until real participants are engaged.

Submission — Support model with named staff, plus drill preparation records.

Context — Phase 6A (CV-07 Pilot entry) — BC-08 has no real workfront; all ten dimensions are design-only.

Evidence Requested — Nomination of a real CV-07 workfront with owner, window and work demand

Acceptance Need — Nomination record with named field owner and window.

Not Requested — A synthetic or illustrative workfront is explicitly not requested.

Submission — Workfront nomination record with SIMOPS context.

Context — Phase 6A (CV-07 Pilot entry) — Dimension-level confirmation is required; no aggregate assertion accepted.

Evidence Requested — Confirmation of crew, equipment, materials and field prerequisites for the nominated workfront

Acceptance Need — Per-dimension attributable confirmation.

Not Requested — A blanket readiness statement is not requested; dimension-level confirmation is.

Submission — Per-dimension confirmation referencing the nominated workfront.

Context — Phase 6A (CV-07 Pilot entry) — SIMOPS cumulative rules require a real concurrent-work picture.

Evidence Requested — SIMOPS context and field prerequisite confirmation for the nominated workfront

Acceptance Need — ES&H confirmation of concurrent work context.

Not Requested — You are not asked to validate the prototype SIMOPS rules.

Submission — SIMOPS assessment for the execution window.

Context — Phase 6A (CV-07 Pilot entry) — Collection cannot start without a confirmed source and owner per metric.

Evidence Requested — Source and owner confirmation for the 12 frozen BEFORE metrics

Acceptance Need — Per-metric source and owner confirmation.

Not Requested — You are not asked to start collecting; only to confirm source and owner.

Submission — Governed extract description or measurement plan with metric-level owner.

Context — Phase 6A (CV-07 Pilot entry) — BEFORE is time-irreversible and must precede any Pilot exposure.

Evidence Requested — Formal authorization to start prospective BEFORE collection

Acceptance Need — Attributable collection-start authorization.

Not Requested — Retrospective reconstruction of any kind is not requested and is not acceptable.

Submission — Minuted governance decision artefact (not a process diagram).

Context — Phase 6A (CV-07 Pilot entry) — Collection must not itself contaminate the baseline.

Evidence Requested — Non-intrusive observation access that does not alter current ways of working

Acceptance Need — Access confirmation with non-intrusive conditions.

Not Requested — No new prompts, screens, training or approval-sequence changes are requested.

Submission — Observation protocol and access confirmation stating non-intrusive conditions.