S1 = ACTIVATED_FOR_EXTERNAL_EXECUTIONWAVE_1 = EXECUTION_PREPAREDPhase 6A · HOLDPhase 6B · NOT_AUTHORIZEDPhase 7 · NO_GOBC09Protection · ACTIVEPilotExposure · PROHIBITED
Phase 6A — Wave 1 / S1 Owner Engagement & Evidence Acquisition Activation
Externalizing the existing S1 requests: AWAITING_OWNER → OWNER_ACKNOWLEDGED → EVIDENCE_SUBMITTED
Lovable may prepare, route and assess evidence acquisition, but only competent real-world owners can create the authority and OperationalClosureEvidence needed to move Phase 6A. Activation of S1 is not progress against any blocker.
Source
/board + /erx + /wave1 — no request created, merged or replaced
Blocker state
BC-01 / BC-02 / BC-03 / BC-05 / BC-06 = OPEN
Disposition
S1 = ACTIVATED_FOR_EXTERNAL_EXECUTION · OwnerAcknowledged 0 · EvidenceSubmitted 0 · EligibleForRetest 0
A · S1 Executive Execution Summary
S1 is activated for external execution against the six existing Wave 1 requests with no upstream dependency: ER-01, ER-06, ER-07 (longest external lead times) and ER-11, ER-16, ER-17 (competent decisions obtainable from internal authority now). Each remains AWAITING_OWNER. Nothing has been acknowledged, submitted, assessed or retested.
Why these six
S1 was fixed in /wave1 by lead time, cross-blocker dependency, authority availability and retest leverage. It is reused unchanged; no contradiction was found that would justify recalculating the Wave 1 architecture.
Adjacent action (not S1)
ER-19 (BC-06 path election) is not an S1 request. Its execution action is escalation under ESC-03, because no competent decision owner has yet accepted the election authority.
- · No blocker closes at S1; closure is not reachable through engagement.
- · No owner acknowledgement may be recorded by the design team.
- · No synthetic or reconstructed artefact may enter the intake queue.
- · BC-09 requests (ER-26/27/28) remain outside Wave 1; BC09Protection unaltered.
- · Retest triggers remain NOT_PREPARED until a real assessment reaches SUFFICIENT_FOR_RETEST.
B · Exact S1 Request Population
Exactly the six existing S1 requests. Status remains AWAITING_OWNER until an actual external acknowledgement is supplied and recorded with an attributable reference.
ER-01OP-01BC-01CRITICAL_PATHEAC-01AWAITING_OWNEREnterprise Architecture
Federated participation map per source and object class
Exact first action
Issue the participation-map request to Enterprise Architecture and obtain a named accountable respondent plus a governance slot for the decision.
Owner question
For each source and object class, which participation mode is authorized and what happens when it is unavailable?
Evidence requested
Confirmed federated participation map per source and object class
Minimum acceptance need
Attributable participation declaration per source/object.
Dependency impact
Frames BC-01 scope, BC-02 identity scope, BC-03 lifecycle authority location and BC-06 Path A feasibility.
Potential retest
RT-01 · NOT_PREPARED
ER-06OP-06BC-01CRITICAL_PATHEAC-02AWAITING_OWNERIT / IM
Enterprise interface hosting and data-movement authorization
Exact first action
Issue the IT/IM authorization request for hosting, network path and data movement covering the declared federation mechanisms, and confirm which review board holds the decision.
Owner question
Are the declared mechanisms authorized to run, with what constraints?
Evidence requested
Enterprise interface hosting, network and data-movement authorization
Minimum acceptance need
IT authorization statement for the declared mechanisms.
Dependency impact
Vetoes or authorizes every BC-01 mechanism and any live IAM test under BC-02.
Potential retest
RT-01 · NOT_PREPARED
ER-07OP-07BC-02CRITICAL_PATHEAC-03AWAITING_OWNERIAM / Cyber
Pilot identity provisioning and authentication
Exact first action
Issue the IAM/Cyber request for identity provider, authentication method and Pilot identity provisioning, and confirm the provisioning intake route and its constraints.
Owner question
Which identity provider and authentication method will serve real Pilot users?
Evidence requested
Identity provider, authentication method and Pilot identity provisioning plan
Minimum acceptance need
IAM owner confirmation + provisioned identity set.
Dependency impact
IAM-01 → IAM-06 cannot begin without provisioned real identities; longest path in Wave 1.
Potential retest
RT-02 · NOT_PREPARED
ER-11OP-09BC-03HIGH_LEVERAGEEAC-05AWAITING_OWNERBusiness Product Owner
Lifecycle ownership and transition authority acceptance
Exact first action
Issue the lifecycle authority matrix request to the Business Product Owner and confirm the decision forum that will record the governed acceptance.
Owner question
Who owns each object lifecycle, who may transition it, and what happens when that authority is unavailable?
Evidence requested
Acceptance of lifecycle ownership and transition authority per object
Minimum acceptance need
Decision artefact per object class.
Dependency impact
Unblocks the governance dimension of BC-03; technical enforcement stays BC-02-held.
Potential retest
RT-03 · NOT_PREPARED
ER-16OP-12BC-05CRITICAL_PATHEAC-06AWAITING_OWNERRecords Management
Retention basis and period per record class
Exact first action
Issue the CA-04 record class / retention basis request to Records Management and confirm the classification decision route.
Owner question
What is the lawful retention basis and period for each material record class?
Evidence requested
Retention basis and period per material record class
Minimum acceptance need
Competent retention decision per class.
Dependency impact
Together with ER-17/ER-18 this is the shortest credible route to a first BC-05 retest.
Potential retest
RT-05 · NOT_PREPARED
ER-17OP-13BC-05CRITICAL_PATHEAC-06AWAITING_OWNERPrivacy
Personal-data classification and minimisation decision
Exact first action
Issue the personal-data scope, data-minimisation and access-scope request to Privacy as a decision separate from the Records Management decision.
Owner question
Which personal attributes may be pinned into a readiness decision, and who may access them?
Evidence requested
Personal-data classification, minimum attribute and access scope decision
Minimum acceptance need
Privacy decision per class.
Dependency impact
BC-05 cannot reach SUFFICIENT_FOR_RETEST on a records decision alone.
Potential retest
RT-05 · NOT_PREPARED
C · Owner-Facing Evidence Request Packages
Request language is technical, minimal and non-leading. No wording indicates a preferred answer, and 'Not Requested' is stated explicitly so that no owner is asked to approve something outside their authority.
OP-01Enterprise ArchitectureER-01BC-01AWAITING_OWNER
Context
Phase 6A (CV-07 Pilot entry) — BC-01 cannot be retested without a declared participation mode per source.
Decision / evidence requested
ER-01: Confirmed federated participation map per source and object class
Acceptance need
ER-01: Attributable participation declaration per source/object.
Not requested
You are not asked to approve the readiness product, its rules or its user interface.
Evidence form
ER-01: Architecture-signed participation map with failure behaviour. (alternative: Per-source owner emails consolidated and countersigned.)
OP-06IT / IMER-06BC-01AWAITING_OWNER
Context
Phase 6A (CV-07 Pilot entry) — No participation is real without IT authorization.
Decision / evidence requested
ER-06: Enterprise interface hosting, network and data-movement authorization
Acceptance need
ER-06: IT authorization statement for the declared mechanisms.
Not requested
You are not asked to endorse the functional design.
Evidence form
ER-06: Architecture review record. (alternative: Conditional authorization with named constraints.)
OP-07IAM / CyberER-07BC-02AWAITING_OWNER
Context
Phase 6A (CV-07 Pilot entry) — Authority enforcement must be enterprise-enforced, not prototype-simulated.
Decision / evidence requested
ER-07: Identity provider, authentication method and Pilot identity provisioning plan
Acceptance need
ER-07: IAM owner confirmation + provisioned identity set.
Not requested
You are not asked to approve application functionality.
Evidence form
ER-07: Signed IAM design and provisioning record. (alternative: Time-boxed Pilot identity scope with revocation controls.)
OP-09Business Product OwnerER-11BC-03AWAITING_OWNER
Context
Phase 6A (CV-07 Pilot entry) — Lifecycle is defined by design and accepted by nobody.
Decision / evidence requested
ER-11: Acceptance of lifecycle ownership and transition authority per object
Acceptance need
ER-11: Decision artefact per object class.
Not requested
A process diagram is not requested; a decision artefact is.
Evidence form
ER-11: Signed lifecycle authority matrix. (alternative: Minuted governance decision with attributable authority.)
OP-12Records ManagementER-16BC-05AWAITING_OWNER
Context
Phase 6A (CV-07 Pilot entry) — Retention currently rests on a design proposal, not a legal basis.
Decision / evidence requested
ER-16: Retention basis and period per material record class
Acceptance need
ER-16: Competent retention decision per class.
Not requested
You are not asked to endorse design proposal RC-RET-01 as-is.
Evidence form
ER-16: Signed retention schedule extract. (alternative: Interim retention decision with review date.)
OP-13PrivacyER-17BC-05AWAITING_OWNER
Context
Phase 6A (CV-07 Pilot entry) — Person and health-adjacent data must be minimised by decision, not assumption.
Decision / evidence requested
ER-17: Personal-data classification, minimum attribute and access scope decision
Acceptance need
ER-17: Privacy decision per class.
Not requested
Full HR or health records are explicitly not requested.
Evidence form
ER-17: DPIA-equivalent record. (alternative: Conditional approval with narrowed attributes.)
D · Six High-Leverage Artefact Acquisition View
One artefact may support several requests, but acceptance assessments are never merged. Each request is assessed independently against its own MinimumAcceptableEvidence.
| Candidate | Owner | Requests | Blockers | Criteria potentially satisfied | Criteria still requiring separate evidence | Priority | Availability |
|---|---|---|---|---|---|---|---|
| EAC-01 | Enterprise Architecture | ER-01 · ER-02 · ER-04 · ER-05 | BC-01 · BC-03 · BC-06 | Declared participation mode, object class and read/write boundary per source at enterprise level. | Per-source owner acceptance (ER-02/04/05 each still require their own owner statement) and IT authorization (ER-06). | S1_IMMEDIATE | NOT_SUPPLIED — partially pre-existing in enterprise governance; not requested-and-received. |
| EAC-02 | IT / IM | ER-06 · ER-02 · ER-03 · ER-04 · ER-05 | BC-01 · BC-02 | Authorization and named constraints for the declared federation mechanisms. | System-owner authority statements; authentication design owned by IAM; failure behaviour per object class. | S1_IMMEDIATE | NOT_SUPPLIED — cannot pre-exist for this scope; must be issued for the declared mechanisms. |
| EAC-03 | IAM / Cyber | ER-07 · ER-08 · ER-09 | BC-02 · BC-03 | Identity provider, authentication method, role resolution source, delegation/revocation behaviour. | Demonstrated revocation with real identities (ER-09 preferred form) and the HR authoritative person source (ER-10). | S1_IMMEDIATE | NOT_SUPPLIED — design part documentable now; provisioning part is new work. |
| EAC-04 | HR / RRLL | ER-10 · ER-08 | BC-02 | Authoritative person source, update cadence and steward. | IAM endorsement of the mapping to authority scopes; Wave 2 BC-04 capacity criteria are separate. | POST_S1 | NOT_SUPPLIED — ER-10 sits in S3; requested outside S1. |
| EAC-05 | Business Product Owner | ER-11 · ER-12 | BC-03 | Accepted lifecycle ownership and transition authority per object class. | Q4 federation-edge boundary confirmation (ER-12 owner statement) and technical enforcement, which is BC-02-held. | S1_IMMEDIATE | NOT_SUPPLIED — most obtainable Wave 1 artefact; internal authority, no BC-02 dependency. |
| EAC-06 | Records Management + Privacy (joint issue, separate decisions) | ER-16 · ER-17 · ER-18 | BC-05 | DataClassification, RecordClass, RetentionBasis, DataMinimisation and AccessScope per class. | Health custodian confirmation of the binary fitness flag remains a separate competent decision (ER-18). | S1_IMMEDIATE | NOT_SUPPLIED — ER-16/ER-17 activated in S1; ER-18 (health custodian) runs in S3. |
E · BC-01 / BC-02 Critical-Path Actions
ER-01, ER-06 and ER-07 initiate the longest external lead-time dependencies in Wave 1. Delay here propagates to every BC-01 and BC-02 retest; nothing downstream can compensate.
BC-01ER-01 · ER-06
First action
Obtain actual System Owner confirmation per source and object class — not enterprise capability statements.
System Owner confirmation fields
ParticipationModeObjectClassReadAuthorityWriteAuthoritySnapshotAuthorityAuthenticationFailureBehaviour
No-inference rule
No API, endpoint, payload, capability or enterprise readiness may be inferred. Absence of an owner statement is recorded as UNVERIFIABLE, never as available.
BC-02ER-07IAM-01 → IAM-06 · NOT_EXECUTABLE
First action
Establish the prerequisites for RealPilotIdentity, RoleResolution and AuthorityScope so that IAM-01 → IAM-06 becomes executable later.
- · RealPilotIdentity — identity provider, authentication method and provisioned Pilot identities (ER-07).
- · RoleResolution — authoritative role source and mapping to authority scopes (ER-08, dependent on ER-10 in S3/S4).
- · AuthorityScope — scope boundaries, delegation and revocation behaviour (ER-09, dependency-held on ER-07).
IAM state
NOT_EXECUTABLE — no real identity exists; simulation evidence does not substitute.
F · BC-03 / BC-05 / BC-06 Parallel Decision Actions
Governance decisions proceed independently of integration; they are not held behind BC-01 or BC-02.
BC-03ER-11AWAITING_OWNER
Decision requested
Governed lifecycle authority artefact — accepted ownership and transition authority per object class.
Competent owner
Business Product Owner
Independent of integration
YES — governance decision does not require any source interface to exist.
Residual
Technical enforcement of lifecycle authority remains BC-02-held and is recorded as a separate residual dependency.
BC-05ER-16 · ER-17AWAITING_OWNER
Decision requested
Material CA-04 decisions: record class and retention basis (Records Management), personal-data scope, data-minimisation and access scope (Privacy).
Competent owner
Records Management / Privacy — two separate competent decisions
Independent of integration
YES — classification decisions are governance acts, not integration outputs.
Residual
ER-18 (health custodian binary fitness flag) is a separate competent decision executed in S3.
BC-06ER-19ESCALATE_AUTHORITY
Decision requested
Competent election process for Path A (real Critical Control integration) or Path B (formal rescope), including the decision authority itself.
Competent owner
NOT_CONFIRMED — ES&H Executive proposed; authority not accepted
Independent of integration
YES for the election; NO for Path A execution.
Residual
ESC-03 remains ACTIVE. Path B may never be elected merely to facilitate closure; election must record DecisionAuthority, Reason, PilotEvidenceLost, ResidualRisk and Phase7Impact.
G · Owner Acknowledgement Intake
The acknowledgement register is append-only and currently empty. No acknowledgement may be recorded on behalf of an owner, and authority is never inferred from the act of responding.
Owner
Named individual issuing the acknowledgement.
Function
The function whose authority is being exercised.
AcknowledgementRef
Attributable reference — email, memo, minute or system record.
AcknowledgementDate
Date the acknowledgement was issued by the owner.
AuthorityConfirmed
YES / NO / NEEDS_CLARIFICATION — recorded, never inferred from the fact of a response.
- · AWAITING_OWNER → OWNER_ACKNOWLEDGED (requires an attributable acknowledgement record)
- · OWNER_ACKNOWLEDGED → EVIDENCE_SUBMITTED (requires an actual artefact with a reference)
- · EVIDENCE_SUBMITTED → UNDER_EVIDENCE_REVIEW (seven-check assessment; never closure)
Acknowledgement register: 0 entries — no owner acknowledgement has been supplied.
H · Authority-Dispute Routing
A disputed authority is a governance finding, never a closure. Disputes are routed to the existing escalation register (ESC-01…ESC-04); no substitute owner is appointed by the design team.
| Req | Competent owner | If owner states | Recorded as | Routed to |
|---|---|---|---|---|
| ER-01 | Enterprise Architecture | NOT_MY_AUTHORITY | OWNER_AUTHORITY_DISPUTED | ESC-02 |
| ER-06 | IT / IM | NOT_MY_AUTHORITY | OWNER_AUTHORITY_DISPUTED | ESC-02 |
| ER-07 | IAM / Cyber | NOT_MY_AUTHORITY | OWNER_AUTHORITY_DISPUTED | ESC-02 |
| ER-11 | Business Product Owner | NOT_MY_AUTHORITY | OWNER_AUTHORITY_DISPUTED | ESC-02 |
| ER-16 | Records Management | NOT_MY_AUTHORITY | OWNER_AUTHORITY_DISPUTED | ESC-02 |
| ER-17 | Privacy | NOT_MY_AUTHORITY | OWNER_AUTHORITY_DISPUTED | ESC-02 |
Dispute register: 0 entries — no owner has stated a position.
I · Evidence Arrival Queue
Arrival of an artefact never closes a blocker. EVIDENCE_SUBMITTED moves to UNDER_EVIDENCE_REVIEW and the seven-check assessment from /erx is executed before any quality level is recorded.
Arrival queue: 0 artefacts — nothing received; absence is recorded as absence, never as a pending pass.
Seven-check assessment (/erx)
- · AUTHENTIC — Issued by the named owner through an attributable channel.
- · CURRENT — Within its stated validity window and not superseded.
- · IN_SCOPE — Addresses the ApplicableScope of the request, not an adjacent topic.
- · OWNER_COMPETENT — The issuing function actually holds the authority claimed.
- · TRACEABLE — Carries a reference, version and date that can be reconstructed later.
- · SUFFICIENT_FOR_CRITERION — Satisfies the MinimumAcceptableEvidence of this request.
- · NO_MATERIAL_CONTRADICTION — Does not conflict with the frozen architecture or another accepted artefact.
Quality scale
- · NONE — No competent operational evidence received.
- · PARTIAL — Some criteria satisfied; the blocker cannot yet be retested.
- · SUFFICIENT_FOR_RETEST — Enough to attempt a targeted retest — not closure.
- · SUFFICIENT_FOR_CLOSURE — Retest passed and every acceptance criterion is evidenced.
Every retest trigger remains NOT_PREPARED until an actual evidence assessment reaches SUFFICIENT_FOR_RETEST. Simulation, design or synthetic evidence may never trigger a targeted retest.
J · S1 Execution Control Panel
No readiness percentage is displayed. Engagement volume is not readiness.
S1Requests
6
OwnersEngaged
6
AwaitingOwner
6
OwnerAcknowledged
0
EvidenceSubmitted
0
AuthorityDisputed
0
HighLeverageArtefactsRequested
5
EvidenceUnderReview
0
RetestTriggersPrepared
0
S1 · ACTIVATED_FOR_EXTERNAL_EXECUTIONPhase 6A · HOLDPhase 6B · NOT_AUTHORIZEDPhase 7 · NO_GOBC09Protection · ACTIVEPilotExposure · PROHIBITED
BC-01 / BC-02 / BC-03 / BC-05 / BC-06 = OPEN
Lovable may prepare, route and assess evidence acquisition, but only competent real-world owners can create the authority and OperationalClosureEvidence needed to move Phase 6A.