Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.

Step 12 · Operating procedures, scope guards and carried-forward scenarios

Goal. Not software to program. The operations procedures GGA staff rehearse, the guards that stop deferred features entering the build, and the home of scenarios that are Superseded or Parked.

Blueprint delivery stage: All stages (Delivery-Options-Comparison).

Former 1.3 name: Manual DG services and scope guards. The file name and the step number are kept as stable identifiers (as with the historical DG prefix), so existing links and the step-12 label stay valid.

Not started. This is a specification; no code has been written. The primary-step mapping is an index, not proof that each full scenario can be completed in its step: see Dependency-and-Regression-Table.

Prerequisites

None; this track does not wait for software steps. Procedures stay blocked until GGA names the operations owner (GL01) and decides the rules that apply. Policy-independent scaffolding may start after the overall start conditions; decision-dependent behaviour and its final oracle stay blocked until the named authority decides. Proposed defaults are recommendations, never prerequisites. Blocked decisions: GQ01-staged, GQ04-staged, Q12, Q23, GL07-staged.

Changes (illustrative, not a final schema)

Sources: Blueprint pages cited per item (GGA-Requirement-Register).

Build items:

• Operations guide for profiles, moderation, consent exceptions, contribution reconciliation, events, exceptions and exports (p. 19)
• Scope guards for the deferred items: native apps, social feed, open messaging, deal negotiation, complex recommendation, accounting, automatic LinkedIn publishing, WhatsApp automation, AI matching (pp. 1, 16)
• AI and optional-channel adapters disabled by default; assistance drafts stay unpublished (pp. 7, 16)
• Superseded 1.3 service scenarios and Parked scenarios kept as history, with no oracle invented

Expected outputs and invariants

Software scope changes only through a written change request; nothing here is a software payment gate.

Tests-first subset

Primary scenarios of this step (write these tests first): T03, T09, T12, T24, T29, DG01, DG06, DG09, DG12, DG18, DG24, DG27, DG29, DG30, DG31, DG32, DG33, DG36, DG41, DG43, DG44, GS19-staged, GS25-staged.

Assertions to write first: new GGA scenarios GS19-staged, GS25-staged. Legacy scenarios whose primary step is this one: T03, T09, T12, T24, T29, DG01, DG06, DG09, DG12, DG18, DG24, DG27, DG29, DG30, DG31, DG32, DG33, DG36, DG41, DG43, DG44. Each follows its replacing GS scenario; the 1.3 text is history (Scenario-Dispositions).

Method: make one meaningful test fail for the expected reason, implement the minimum behaviour, refactor without changing the observable contract. A scenario whose decision is still pending stays Blocked by that decision; no oracle is invented.

Deferred integration checks

Scenarios whose primary step is this one but whose full variants need later components:

• Scope-guard scenarios (GS25, T24, DG24, DG44) are rechecked at every release and in step 11.
• Superseded and Parked scenarios have no build and no oracle; they wait for the decision named in their disposition (Scenario-Dispositions).

Follow-up verification brought here

Scenarios (of any step) that can only be completed or rechecked once this step exists:

• None.

Decisions GGA must settle (dependent behaviour stays blocked until the named authority decides)

GQ01-staged, GQ04-staged, Q12, Q23, GL07-staged

Exit evidence

Procedures are rehearsed on synthetic cases with named staff once GL01 names them; the scope-guard scenarios hold at every release.

Evidence is recorded only for a named build and fixture. A software scenario is not recorded as Passed until all its relevant variants have been exercised on a named integrated build (step 11).

Navigation: Step-11-UAT-and-Release ← this step · Implementation-Order-Overview