Service Operations
The controlled transition from an accepted pilot to a supportable, commercially governed operating service. Readiness, change approval, deployment authorization, service acceptance, operational handoff and commercial handoff are separate decisions with separate evidence and separate authority.
Core enterprise principle
Nourishe enters steady-state service only when the approved release, operating controls, support ownership, financial procedures and customer responsibilities have been reviewed and accepted. Production is an accountable operating state, not a label.
Production, deployment, monitoring, support and service examples are simulated front-end records. They do not represent a live Nourishe or Gelson's Markets production environment, service commitment or deployment.
Scope version
PSCOPE-2.1
Operating model
SOM-1.2
Calculation version
CALC-8.5
Service period
SP-2027-Q2
Readiness: Ready with ExceptionHealth: DegradedDeployment: Not Authorized
Simulated managed service derived from the accepted pilot GELS-PILOT-001. Financial history, measurement releases and invoices remain owned by Builds 6–8.5 and are read-only here.
Production Scope
What is proposed to enter steady-state operation. Scope approval is not readiness, and readiness is not deployment authorization.
| Category | Item | Detail | In scope |
|---|---|---|---|
| Service component | Tender-level recovery measurement | Daily settled tender ingestion, reconciliation and measurement release. | In scope |
| Service component | Verified fee statement production | Monthly statement pack prepared from Finance-Verified Value only. | In scope |
| Legal entity | ENT-GELSONS-CA | Gelson's Markets (California) — the only entity in production scope. | In scope |
| Location | 27 California stores | All banner BAN-GELSONS locations live at steady-state start. | In scope |
| Location | Mayfair banner locations | Excluded until an approved Production Scope version covers BAN-MAYFAIR. | Excluded |
| User population | Finance Operations (12 named users) | Read and review; approval limits inherited from Build 8 access model. | In scope |
| Data source | Acquirer settlement extract | Data contract DC-ACQ-02, daily, reconciled in Data Operations. | In scope |
| Data source | POS tender journal | Data contract DC-POS-01, daily, reconciled in Data Operations. | In scope |
| Control | 22 Build 10 controls | Operated at the frequency defined in the Control Library — not redefined here. | In scope |
| Recovery opportunity | Interchange qualification recovery | Approved unique recovery opportunity carried from the approved Value Case. | In scope |
| Support boundary | Provider platform incidents | Owned by the provider engagement; escalated, not resolved, by Nourishe support. | In scope |
Readiness domains
Every domain result is derived from its requirements. A domain with any unresolved mandatory requirement is Not Ready.
Scope and configuration
Ready2/2
Data operations
Ready2/2
Calculation integrity
Ready1/1
Access and permissions
Ready1/1
Security and privacy
Ready with Exception2/2
Support and escalation
Ready1/1
Monitoring and observability
Ready1/1
Rollback and recovery
Ready1/1
Finance and billing
Ready1/1
Provider dependencies
Ready with Exception1/1
Customer readiness
Ready1/1
Readiness requirements
| Requirement | Domain | Evidence | Result | |
|---|---|---|---|---|
Production Scope version approved by the grocer business owner PRR-001 · Mandatory | Scope and configuration | PSCOPE-2.1 approval record | Ready | |
Release manifest frozen and hashed before readiness assessment PRR-002 · Mandatory | Scope and configuration | PRM-2027-06-A | Ready | |
All production data contracts reconciled for three consecutive periods PRR-003 · Mandatory | Data operations | Data Operations lineage manifest | Ready | |
Measurement Data Release process rehearsed against the candidate PRR-004 · Mandatory | Data operations | MDR rehearsal RH-2027-041 | Ready | |
Calculation version pinned and trace reproducible PRR-005 · Mandatory | Calculation integrity | CALC-8.5 integrity report | Ready | |
Permission set reviewed against approved role limits PRR-006 · Mandatory | Access and permissions | PERM-3.1 access review | Ready | |
No open Severity 1 or 2 security finding PRR-007 · Mandatory | Security and privacy | Build 10 control register | Ready | |
Privacy classification confirmed for all production fields PRR-008 · Mandatory · Exception expires 2027-09-30 | Security and privacy | Two derived fields pending classification | Ready with Exception | |
Named support owners and escalation matrix accepted PRR-009 · Mandatory | Support and escalation | SOM-1.2 escalation matrix | Ready | |
Simulated service indicators defined with objective targets PRR-010 · Mandatory | Monitoring and observability | SLI catalogue v1.2 | Ready | |
Rollback target identified and rehearsed PRR-011 · Mandatory | Rollback and recovery | Rollback rehearsal RB-2027-009 | Ready | |
Billing responsibilities assigned and statement path unchanged PRR-012 · Mandatory | Finance and billing | Build 7 billing procedure | Ready | |
Provider commitments current with no blocking corrective action PRR-013 · Advisory · Exception expires 2027-09-30 | Provider dependencies | CedarPay corrective action CA-14 open | Ready with Exception | |
Customer operating calendar and contacts confirmed PRR-014 · Advisory | Customer readiness | Service calendar 2027 | Ready |
Production Readiness Assessment
Assessment resultReady with Exception
Mandatory requirements satisfied12 of 12
Open exceptions2 open · 0 expired · 0 prohibited
OutstandingNone
Approval
Production Readiness Approval does not execute deployment, confirm post-deployment behaviour, accept the service or create realized value.
Production and service status
Read-only. Simulated service records — operational changes are made in Service Operations.
Service
GELS-SVC-PAY-001
Production scope version
PSCOPE-2.1
Active production release
Payments Recovery 4.2 — Production Release Candidate
Deployment status
Not Authorized
Service acceptance
Not Accepted
Operational handoff
Not Started
Commercial handoff
Not Started
Service health
Degraded
Service period
SP-2027-Q2 · 2027-04-01 – 2027-06-30
Open Sev 1 / Sev 2
0 / 1
Open blocking changes
1
Service level
3 of 3 contractual commitments met; 4 of 6 objectives met
Latest service review
SP-2027-Q2: Continue with Actions
Renewal, expansion or exit
Renewal readiness Not Ready — No decision recorded