@raishin/vanguard-frontier-agentic 2.11.0 → 2.13.0

package/skills/sap/sap-release-cutover-finance-controls-protocol/SKILL.md

@@ -0,0 +1,170 @@
+---
+name: sap-release-cutover-finance-controls-protocol
+description: Cross-functional coordination protocol governing handoffs between SAP Release Management, Business Process Owners, and Finance Controls for transport imports, production freeze enforcement, cutover readiness, financial-period close, O2C/P2P business process continuity, inventory valuation, revenue recognition impact, and hypercare. Defines go/no-go decision rights, irreversible-action gates, rollback requirements, and audit packaging. Never mutates live systems and never bypasses any guarded-mutating gate.
+allowed-tools: Read Grep Glob WebSearch WebFetch
+metadata:
+  author: "github: Raishin"
+  version: "0.1.0"
+  updated: "2026-06-19"
+  category: compliance
+  lifecycle: experimental
+---
+
+# SAP Release Cutover Finance Controls Protocol
+
+## Purpose
+
+This skill defines the cross-functional coordination and handoff contract between SAP Release Management, Business Process Owners, and Finance Controls when a transport import, production system cutover, or release-window event intersects with financial-period integrity, business process continuity, or hypercare obligations. It establishes go/no-go decision rights, evidence requirements for release readiness, rollback plan requirements, financial controls impact assessment gates, and the audit package structure required for SOX and internal audit compliance.
+
+This is a governance coordination document. It does not import transports, execute cutover scripts, modify financial posting periods, close sales documents, or trigger any system action. All mutations remain gated behind the relevant guarded-mutating operator agents. No guarded gate is bypassed.
+
+## When to use
+
+Invoke this protocol when any of the following trigger conditions apply:
+
+- **Transport import to production**: One or more transports are queued for import into an SAP production system (ECC, S/4HANA on-premise or Private Cloud Edition, SAP BTP ABAP environment) and the import window intersects with a financial-period boundary, a business-critical operational window (payroll run, customer invoice processing, period-end closing cockpit activity), or a known high-risk change category.
+- **Production freeze enforcement**: A production freeze period has been declared (period-end close, quarter-end, year-end, regulatory reporting deadline, merger/acquisition close date, major SAP upgrade) and a change request has been submitted requesting an exception to the freeze.
+- **Cutover readiness**: An SAP implementation or upgrade project is approaching the go-live cutover date and the cutover readiness checklist (technical, functional, data migration, and finance controls) has not been fully signed off.
+- **Financial-period close impact**: A pending or recently completed transport modifies financial configuration (posting period variants, document types, account determination, tax codes, fiscal year variant, controlling area settings) or business logic affecting financial postings (pricing procedures, output determination, goods movement account assignment, revenue account mapping).
+- **O2C or P2P business process disruption**: A transport, configuration change, or system migration has caused or risks causing disruption to order-to-cash (O2C) or procure-to-pay (P2P) processes during a period when business volume is high or process interruption has material revenue or liability impact.
+- **Inventory valuation impact**: A transport or migration affects material ledger configuration, standard cost estimates, moving average price calculation, or valuation area assignment in a way that could alter inventory values on the balance sheet.
+- **Revenue recognition impact**: A transport or configuration change modifies SAP Revenue Accounting and Reporting (RAR) setup, SD billing plan configuration, contract account assignment, or multi-element arrangement allocation in a way that could affect revenue recognized in the current or prior period.
+- **Hypercare escalation**: The system is in a defined hypercare period post-go-live and an incident, defect, or configuration issue has been escalated that requires a production correction outside the standard change process.
+
+## Participating agents
+
+The following agents operate within this protocol. Each holds a defined role and must not act outside its lane without explicit cross-function approval per the decision rights table.
+
+- `sap-release-change-collision-agent` — Release management specialist responsible for transport dependency analysis, change collision detection, release schedule governance, and production freeze enforcement. Assesses transport content, identifies conflicts, and confirms release window eligibility. Does not import transports.
+- `sap-data-migration-cutover-readiness-agent` — Cutover readiness specialist assessing data migration completeness, cutover checklist status, go-live readiness scoring, and rollback trigger conditions. Does not execute cutover scripts or migration programs.
+- `sap-finance-fico-controls-agent` — Finance Controls specialist assessing the financial impact of transports, configuration changes, and cutover events on FICO configuration integrity, posting period controls, financial statement accuracy, SOX IT general controls, and period-end close sequencing. Does not modify financial configuration.
+- `sap-guarded-transport-import-operator-agent` — The sole agent authorized to execute transport import actions in SAP systems. All transport imports proposed by this protocol must be queued to this agent and require all approvals listed in the decision rights table before execution. This agent is the primary guarded-mutating gate for release actions in this protocol.
+- `sap-hypercare-incident-commander-agent` — Hypercare coordination specialist responsible for incident triage, severity classification, resolution path governance, business impact assessment, and escalation to SAP Support or escalation management. Does not execute production changes directly; routes approved corrections through the guarded-transport-import-operator-agent.
+
+## Required evidence
+
+Before any cross-function handoff or go/no-go decision is initiated, the following evidence must be assembled by the requesting function:
+
+1. **Transport manifest**: Complete list of transports in the import queue for the target production system, with transport number, description, development system origin, last test system import result, and responsible developer/configuration consultant.
+2. **Change collision analysis**: Output from `sap-release-change-collision-agent` confirming whether any transports in the queue conflict with other queued or recently imported transports on shared configuration objects.
+3. **Financial impact assessment**: Output from `sap-finance-fico-controls-agent` classifying each transport by financial impact category (no financial impact / financial configuration change / financial posting logic change / period-sensitive financial change) and identifying any transports that modify configuration affecting current-period financial statements.
+4. **Test evidence**: Import results from the quality assurance system (or pre-production equivalent), regression test execution summary, and sign-off from the functional team lead for each affected business process.
+5. **Business process owner sign-off**: Written confirmation from the process owner for each affected business process (O2C, P2P, Finance, HR) that the tested change is approved for production import.
+6. **Rollback plan**: Documented rollback approach for each transport in the queue that is classified as high-risk or period-sensitive, including the rollback steps, estimated rollback duration, rollback trigger conditions, and the individual authorized to invoke rollback.
+7. **Freeze exception justification** (if applicable): For changes submitted during a production freeze, a written justification from the requesting team, classification as critical/high/medium risk, and Finance Controls confirmation that the change is safe to import during the freeze window.
+8. **Cutover readiness checklist status** (if applicable): Completed checklist covering technical prerequisites, data migration sign-off, financial opening balance validation, user training completion, support model readiness, and hypercare plan confirmation.
+9. **Hypercare incident record** (if applicable): Incident ticket number, symptom description, affected business process, user and transaction volume impact, workaround status, and proposed correction transport details.
+
+## Redaction policy
+
+Sensitive financial data must be treated as follows before evidence is shared across functions or included in audit documentation:
+
+- **Financial configuration values**: Posting period variants, tax code rates, account determination keys, and pricing condition values are included in evidence packages but are marked as restricted — access limited to Finance Controls and internal audit. Operational IT teams see the object names and change descriptions, not the configuration values.
+- **Transport object lists**: Full ABAP object lists for transports are shared with the release manager and Finance Controls. Business process owners receive a functional impact summary, not the raw object list.
+- **Period-end close status**: Current period-end close status (open items, unposted documents, blocked periods) is shared with Finance Controls and the business process owner. It is not included in general release documentation visible to the broader IT team.
+- **Hypercare incident details**: Incident descriptions that include specific customer or vendor account numbers, financial amounts, or contract details are redacted in shared status reports — Finance Controls and the incident commander receive full details; stakeholder communications receive a business impact summary.
+
+## Decision rights
+
+| Decision | Primary authority | Secondary approval required | Notes |
+|---|---|---|---|
+| Approve transport import to production outside a freeze | Release Manager | Business Process Owner (affected process) + Finance Controls (if financial impact) | Executes via sap-guarded-transport-import-operator-agent |
+| Approve freeze exception for critical production correction | CISO or Release Governance Board | Finance Controls (mandatory) + CIO or delegate | Written justification and risk acceptance required |
+| Declare go/no-go for cutover | Project Steering Committee or designated Go-Live Authority | Finance Controls sign-off + Business Process Owner sign-off for each in-scope process | All checklist items must be confirmed green or exceptions documented with acceptance |
+| Invoke production rollback | Release Manager (with CIO notification) | Finance Controls (if financial configuration is being rolled back) | Rollback trigger conditions must be met; rollback plan must be pre-approved |
+| Extend production freeze | CIO or Release Governance Board | Finance Controls concurrence | Written communication to all stakeholders required |
+| Classify a hypercare incident as critical | sap-hypercare-incident-commander-agent | Business Process Owner acknowledgment | Critical classification triggers SAP escalation path and executive notification |
+| Approve a production correction transport during hypercare | sap-hypercare-incident-commander-agent + Release Manager | Finance Controls (if financial impact) | Executes via sap-guarded-transport-import-operator-agent after all approvals |
+| Close hypercare and transition to steady state | Project Steering Committee | Release Manager + Finance Controls | Requires no open critical or high incidents and stable KPI baselines |
+
+## Escalation owners
+
+| Scenario | First escalation owner | Second escalation owner |
+|---|---|---|
+| Transport import causes financial statement impact in current period | Finance Controls lead | CFO and external auditor notification |
+| Production freeze exception request for a non-critical change | Release Governance Board | CIO |
+| Cutover go/no-go blocked due to open financial migration items | Project Steering Committee | CFO |
+| O2C or P2P disruption causing revenue or liability impact during hypercare | sap-hypercare-incident-commander-agent | CFO + CIO |
+| Inventory valuation error affecting balance sheet in closed period | Finance Controls lead | CFO + external auditor notification |
+| Revenue recognition configuration error affecting recognized revenue | Finance Controls lead + General Counsel | CFO + external auditor notification |
+| Rollback invoked for a financial configuration transport | Finance Controls lead | CFO + CIO |
+| SOX IT general control failure identified during release or cutover | Internal Audit | CFO + Chief Compliance Officer |
+
+## Irreversible-action gate
+
+The following actions are classified as irreversible or high-consequence and must not proceed without the approvals listed:
+
+- **Transport import to production modifying financial configuration (posting periods, account determination, tax codes, fiscal year variant)**: Requires Finance Controls written approval confirming the change is safe to import in the current period and does not affect closed-period financial statements. Change must be tested in QA system with Finance Controls sign-off on test results.
+- **Period-end close sequence interruption (holding or re-opening a closed period)**: Requires CFO or Finance Director written approval. Re-opening a closed posting period to correct an error has accounting and audit implications that cannot be undone by re-closing — the audit trail is permanent.
+- **Go-live cutover execution**: Requires Project Steering Committee written go/no-go decision with all checklist items confirmed or documented exceptions with named acceptance owners. Cutover execution cannot be reversed without invoking the rollback plan.
+- **Production rollback of financial configuration**: Requires Finance Controls written confirmation that rollback will restore financial integrity rather than create a new inconsistency, plus CFO notification. Rollback of financial configuration changes may itself create journal entry discrepancies requiring manual correction.
+- **Freeze exception import during year-end or quarter-end close**: Requires Finance Controls and CFO written approval. Changes during the final days of a financial period carry risk that cannot be fully mitigated by testing alone; executive acceptance of residual risk is required.
+
+This protocol does not execute any of these actions. It surfaces the required approvals and routes the action to `sap-guarded-transport-import-operator-agent` once all approvals are documented.
+
+## Approval requirements
+
+All cross-function release and cutover actions under this protocol require written approval before execution. The audit package must include the approval record for every gate cleared.
+
+Minimum approval quorum per action class:
+
+- **Standard production transport import**: Release Manager + Business Process Owner (affected process).
+- **Transport with financial configuration impact**: Release Manager + Business Process Owner + Finance Controls lead.
+- **Freeze exception import**: Release Governance Board chair + Finance Controls lead + CIO or delegate.
+- **Go-live cutover**: Project Steering Committee (or designated Go-Live Authority) + Finance Controls sign-off + all Business Process Owner sign-offs.
+- **Rollback invocation**: Release Manager + Finance Controls lead (if financial config in scope) + CIO notification.
+- **Hypercare production correction**: sap-hypercare-incident-commander-agent lead + Release Manager + Finance Controls lead (if financial impact).
+
+## Audit package
+
+The audit package for every protocol invocation must contain:
+
+1. **Event summary**: Trigger condition, target production system, transport queue or cutover scope, and affected business processes.
+2. **Transport manifest**: All transports in scope with transport numbers, descriptions, authors, and test system import results.
+3. **Change collision analysis**: Output from `sap-release-change-collision-agent` with collision status per transport.
+4. **Financial impact assessment**: Classification per transport from `sap-finance-fico-controls-agent`, with financial objects affected and period-sensitivity rating.
+5. **Test evidence**: QA import results, regression test summary, and functional sign-off records per business process.
+6. **Approval records**: Written approvals for each gate cleared, with approver identity, date, and scope of approval.
+7. **Rollback plan reference**: Rollback plan version, pre-approval status, and trigger conditions.
+8. **Freeze exception record** (if applicable): Justification, risk classification, Finance Controls assessment, and approval chain.
+9. **Go/no-go decision record** (if applicable): Decision outcome, checklist sign-off status, and any documented exceptions with named acceptance owners.
+10. **Irreversible-action gate log**: For each irreversible action, the gate status (cleared / blocked / pending) and the approval documentation reference.
+11. **Escalation log**: Each escalation event, who was notified, when, and the response received.
+12. **Hypercare incident record** (if applicable): Incident details, severity classification, resolution timeline, and production correction approval chain.
+13. **Residual risk statement**: Any release or financial controls risks not fully mitigated, the rationale for acceptance, and the compensating controls in place.
+
+## Refusal conditions
+
+This protocol and all participating agents must refuse the following requests:
+
+- Queuing a transport for import to production via `sap-guarded-transport-import-operator-agent` without all required written approvals.
+- Approving or recommending approval of a freeze exception without Finance Controls written assessment.
+- Declaring cutover go/no-go without a fully assessed readiness checklist and documented sign-offs from all required functions.
+- Recommending rollback of financial configuration without Finance Controls confirmation that the rollback restores rather than further disrupts financial integrity.
+- Accepting verbal approval for any cross-function release, cutover, or financial controls action.
+- Bypassing any irreversible-action gate listed in this protocol.
+- Importing or recommending import of transports that modify closed-period financial configuration without CFO and Finance Controls written approval.
+- Closing a hypercare incident as resolved without Business Process Owner confirmation and KPI baseline validation.
+
+## Evidence rules
+
+Label all claims with one of:
+
+- `documentation-based` — grounded in SAP transport management, SAP financial accounting configuration, SAP Activate methodology, SOX IT general controls guidance, or ITIL change management documentation
+- `user-provided evidence` — transport manifests, QA import results, regression test summaries, readiness checklist outputs, financial impact assessments, approval records, or incident records provided by the requesting function
+- `inference` — derived reasoning not directly confirmed by official documentation or user-provided evidence; must always be labeled as such
+
+## Response minimum
+
+Every protocol invocation must return, at minimum:
+
+- **Trigger classification**: Which trigger condition(s) apply and which participating agents are activated.
+- **Transport and scope inventory**: Transports or cutover scope items assessed, financial impact classification per item, and collision analysis status.
+- **Go/no-go posture**: Current go/no-go assessment based on available evidence, with blocking conditions listed explicitly.
+- **Financial controls gate status**: Whether Finance Controls assessment is complete, pending, or flagged with a blocking finding.
+- **Rollback plan status**: Whether a pre-approved rollback plan exists for each high-risk or period-sensitive item in scope.
+- **Approval gate status**: For each required approval, primary authority, documentation status (present / outstanding), and gate status (cleared / blocked).
+- **Irreversible-action gate status**: Whether any irreversible actions are pending, approval status, and whether the gate is cleared or blocked.
+- **Escalation notice**: If a financial configuration import is pending during a freeze without required approvals, if a revenue recognition or inventory valuation impact is identified, or if a SOX IT general control failure is detected — the escalation notice must appear before any other recommendation, naming the escalation owners.
+- **Audit package status**: Which audit package elements are populated and which are outstanding.
+- **Next step**: The single next action the requesting function must take, with the responsible owner named.

package/skills/sap/sap-release-cutover-finance-controls-protocol/agents/openai.yaml

@@ -0,0 +1,11 @@
+interface:
+  display_name: "SAP Release Cutover Finance Controls Protocol"
+  short_description: "Cross-functional coordination protocol for SAP Release Management, Business Process Owners, and Finance Controls on transport imports, production freezes, cutover readiness, financial-period close, O2C/P2P disruptions, inventory valuation, revenue recognition, and hypercare. Defines go/no-go decision rights, irreversible-action gates, rollback requirements, and audit packaging. Never mutates live systems."
+  default_prompt: "Use $sap-release-cutover-finance-controls-protocol to coordinate a cross-functional release or cutover governance review. Classify the trigger condition, identify participating agents, assess financial impact per transport or cutover item, confirm approval gate status, check the irreversible-action gate and rollback plan status, and state the next action with the responsible owner named. Flag any financial configuration import during a freeze without Finance Controls approval, revenue recognition or inventory valuation impact, or SOX IT general control failure as an immediate escalation before any other recommendation."
+dependencies:
+  tools:
+    - type: "web"
+      value: "https://help.sap.com/docs/sap-activate/sap-activate-methodology/cutover-management"
+      description: "SAP Activate Cutover Management documentation — primary reference for cutover readiness governance"
+policy:
+  allow_implicit_invocation: true

package/skills/sap/sap-release-cutover-finance-controls-protocol/metadata.json

@@ -0,0 +1,33 @@
+{
+  "id": "sap-release-cutover-finance-controls-protocol",
+  "name": "SAP Release Cutover Finance Controls Protocol",
+  "type": "skill",
+  "provider": "sap",
+  "harnesses": [
+    "claude-code",
+    "codex",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Cross-functional coordination protocol for SAP Release Management, Business Process Owners, and Finance Controls covering transport imports, production freezes, cutover readiness, financial-period close, O2C/P2P disruptions, inventory valuation, revenue recognition impact, and hypercare. Defines go/no-go decision rights, irreversible-action gates, rollback requirements, and audit packaging for SOX and internal audit compliance. Never mutates live systems.",
+  "source_type": "original",
+  "category": "compliance",
+  "official_docs": [
+    "https://help.sap.com/docs/abap-platform-cloud/abap-platform-cloud/transport-management",
+    "https://help.sap.com/docs/sap-s-4hana/sap-s-4hana-on-premise-migration-guide/cutover-activities",
+    "https://help.sap.com/docs/sap-s-4hana-finance/sap-s-4hana-finance/financial-closing-cockpit",
+    "https://help.sap.com/docs/sap-s-4hana-finance/sap-s-4hana-finance/revenue-accounting-and-reporting",
+    "https://help.sap.com/docs/sap-s-4hana-finance/sap-s-4hana-finance/material-ledger",
+    "https://help.sap.com/docs/sap-activate/sap-activate-methodology/cutover-management",
+    "https://www.pcaob.org/standards/auditing/as2201",
+    "https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final"
+  ],
+  "security_notes": "Does not access live SAP production systems, transport management organizers, financial configuration, or FICO posting period settings. Accepts only user-provided transport manifests, QA import results, readiness checklist outputs, financial impact assessments, and incident records. Never accepts production system credentials, transport import passwords, or RFC connection details. All transport imports must route through sap-guarded-transport-import-operator-agent with complete written approval documentation. Period-sensitive financial configuration changes require Finance Controls and CFO written approval before execution. No guarded-mutating gate is bypassed by this protocol.",
+  "last_verified": "2026-06-19",
+  "path": "skills/sap/sap-release-cutover-finance-controls-protocol",
+  "author": "github: Raishin",
+  "version": "0.1.0",
+  "lifecycle": "experimental"
+}

package/skills/sap/sap-release-cutover-finance-controls-protocol/references/official-sources.md

@@ -0,0 +1,89 @@
+# Official sources — SAP Release Cutover Finance Controls Protocol
+
+Use this reference when grounding transport management governance, cutover readiness assessment, financial closing cockpit sequencing, revenue accounting configuration review, material ledger valuation impact assessment, and SOX IT general controls compliance framing.
+
+**Evidence level**: documentation-based (SAP Help Portal, SAP Activate methodology, PCAOB AS 2201, NIST SP 800-53). No live-system evidence is collected by this skill.
+
+## SAP Transport Management
+
+- Transport Management in SAP ABAP Platform Cloud
+  https://help.sap.com/docs/abap-platform-cloud/abap-platform-cloud/transport-management
+  source_owner: SAP SE
+  topic_supported: Transport Organizer, transport request lifecycle, import queue management, transport routes, change and transport system configuration
+  why_needed: Primary reference for transport management model — defines the transport request, import queue, and transport route concepts used to assess transport collision risk and import sequencing
+  evidence_level: primary
+  last_verified: 2026-06-19
+
+## SAP Activate — Cutover Management
+
+- Cutover Management in SAP Activate
+  https://help.sap.com/docs/sap-activate/sap-activate-methodology/cutover-management
+  source_owner: SAP SE
+  topic_supported: SAP Activate cutover methodology, cutover checklist structure, go/no-go decision criteria, cutover execution and rollback guidance, hypercare readiness
+  why_needed: Primary reference for cutover readiness governance — defines the checklist structure, go/no-go criteria, and rollback requirements applied in this protocol
+  evidence_level: primary
+  last_verified: 2026-06-19
+
+## SAP S/4HANA Migration — Cutover Activities
+
+- Cutover Activities in SAP S/4HANA On-Premise Migration Guide
+  https://help.sap.com/docs/sap-s-4hana/sap-s-4hana-on-premise-migration-guide/cutover-activities
+  source_owner: SAP SE
+  topic_supported: S/4HANA migration cutover task sequence, technical and functional cutover steps, data migration sign-off requirements, production system switch activities
+  why_needed: Required for S/4HANA migration projects — defines cutover task ordering and sign-off requirements that inform the cutover readiness checklist assessed by this protocol
+  evidence_level: primary
+  last_verified: 2026-06-19
+
+## SAP S/4HANA Finance — Financial Closing Cockpit
+
+- Financial Closing Cockpit in SAP S/4HANA Finance
+  https://help.sap.com/docs/sap-s-4hana-finance/sap-s-4hana-finance/financial-closing-cockpit
+  source_owner: SAP SE
+  topic_supported: Period-end close task sequencing, closing cockpit configuration, dependent task management, status reporting, user assignment for close activities
+  why_needed: Primary reference for financial period-end close sequencing — required to assess whether a transport import or cutover event conflicts with close activities in progress
+  evidence_level: primary
+  last_verified: 2026-06-19
+
+## SAP S/4HANA Finance — Revenue Accounting and Reporting
+
+- Revenue Accounting and Reporting in SAP S/4HANA Finance
+  https://help.sap.com/docs/sap-s-4hana-finance/sap-s-4hana-finance/revenue-accounting-and-reporting
+  source_owner: SAP SE
+  topic_supported: IFRS 15 / ASC 606 revenue accounting, performance obligation management, contract modification handling, revenue recognition configuration, RAR integration with SD and FI
+  why_needed: Required to assess revenue recognition impact of transports modifying RAR configuration, SD billing plan setup, or contract account mapping — defines the configuration objects that affect recognized revenue in the current period
+  evidence_level: primary
+  last_verified: 2026-06-19
+
+## SAP S/4HANA Finance — Material Ledger
+
+- Material Ledger in SAP S/4HANA Finance
+  https://help.sap.com/docs/sap-s-4hana-finance/sap-s-4hana-finance/material-ledger
+  source_owner: SAP SE
+  topic_supported: Material ledger configuration, actual costing, standard cost estimate, moving average price, parallel valuation, period-end closing for material ledger
+  why_needed: Required to assess inventory valuation impact of transports modifying material ledger configuration, costing variants, or valuation area assignment — defines the configuration objects that affect balance sheet inventory values
+  evidence_level: primary
+  last_verified: 2026-06-19
+
+## SOX IT General Controls
+
+- PCAOB Auditing Standard AS 2201 — An Audit of Internal Control Over Financial Reporting
+  https://www.pcaob.org/standards/auditing/as2201
+  source_owner: PCAOB
+  topic_supported: IT general controls evaluation, change management controls, access controls, IT operations controls, deficiency classification (control deficiency, significant deficiency, material weakness)
+  why_needed: Primary regulatory reference for SOX IT general controls obligations — AS 2201 defines the change management control requirements that govern transport approval, freeze exception, and production change documentation requirements in this protocol
+  evidence_level: primary (regulatory)
+  last_verified: 2026-06-19
+
+## IT Change Management
+
+- NIST Special Publication 800-53 Rev 5 — CM (Configuration Management) and SA (System and Services Acquisition) Control Families
+  https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final
+  source_owner: NIST
+  topic_supported: CM-3 (Configuration Change Control), CM-4 (Impact Analyses), CM-9 (Configuration Management Plan), SA-10 (Developer Configuration Management) — change approval, impact analysis, and audit trail requirements
+  why_needed: Secondary framework reference for change management control requirements — NIST CM-3 and CM-4 directly support the transport approval, financial impact assessment, and rollback documentation requirements in this protocol
+  evidence_level: secondary
+  last_verified: 2026-06-19
+
+## Grounding rule
+
+SAP Help Portal documentation describes the designed capabilities of transport management, Financial Closing Cockpit, Revenue Accounting and Reporting, and Material Ledger. It does not prove which transports are in the user's production import queue, what the current period-end close status is in the user's system, or whether specific configuration objects in the user's system are affected by a pending transport. Users must supply transport manifests, QA import results, financial impact assessments, and readiness checklist outputs for concrete protocol execution.

package/skills/sap/sap-release-cutover-finance-controls-protocol/references/safety-checklist.md

@@ -0,0 +1,39 @@
+# Safety checklist — SAP Release Cutover Finance Controls Protocol
+
+Use before any go/no-go decision, before any approval gate is cleared, and before any transport is queued to `sap-guarded-transport-import-operator-agent`.
+
+## Non-negotiables
+
+- Do not queue any transport for production import without all required written approvals. Transport imports execute via `sap-guarded-transport-import-operator-agent` only after complete approval documentation is confirmed.
+- Do not approve or recommend approval of a freeze exception without Finance Controls written assessment of the change risk.
+- Do not declare a cutover GO without a fully assessed readiness checklist, Finance Controls sign-off, and all Business Process Owner sign-offs documented in writing.
+- Do not recommend rollback of financial configuration without Finance Controls written confirmation that the rollback restores rather than compounds the inconsistency.
+- Do not accept verbal approval for any cross-function release, cutover, or financial controls action. Written approval is mandatory for all gate clearances.
+- Do not bypass the irreversible-action gate. Any action listed under that section of SKILL.md requires all listed written approvals before execution.
+- Do not recommend importing a transport modifying posting period variants, account determination, tax codes, or revenue recognition configuration while the Financial Closing Cockpit is running an active close task for the affected company code.
+- Do not import or recommend importing a transport classified `revenue-recognition-impact` or `inventory-valuation-impact` without CFO written approval and, if prior-period financials are affected, external auditor notification.
+
+## What people get wrong
+
+- **Treating a QA import success as sufficient for production approval**: A successful QA import confirms technical transport integrity and basic functional correctness in a non-production environment. It does not confirm that the change is safe to import in the current financial period, that no collision with other production transports exists, or that Finance Controls has assessed the impact. All three are separate gates.
+- **Assuming that a small or low-risk transport does not require Finance Controls review**: Transport size (number of objects) is not a reliable indicator of financial impact. A single posting period variant change is a one-object transport that can lock or unlock financial periods for an entire company code. All transports with FICO, CO, SD billing, or MM valuation objects require Finance Controls classification.
+- **Importing transports in queue order without collision analysis**: The SAP transport import queue processes transports in sequence, but the order in the queue may not reflect the dependency order of the changes. Importing in queue order without collision analysis can overwrite a more recent change with an earlier version of the same configuration object.
+- **Skipping the rollback plan because the cutover seems straightforward**: Every go-live cutover carries risk that can only be managed with a pre-tested and pre-approved rollback plan. The rollback plan must be tested in a dress rehearsal and approved before cutover execution begins — not drafted after a problem occurs.
+- **Treating hypercare incident workarounds as permanent solutions**: A workaround implemented during hypercare to unblock a business process is a temporary measure, not a resolution. The production correction transport must be developed, tested, and approved through the same governance gate as any other production change — hypercare status does not exempt changes from Finance Controls review.
+- **Conflating period-end close completion with posting period lock**: The Financial Closing Cockpit may show all tasks complete, but posting periods may still be open for corrections. Conversely, posting periods may be locked before all close tasks are formally signed off. Confirm both the closing cockpit status and the posting period variant separately when assessing period-sensitive financial impact.
+
+## When to push back
+
+- Push back (and escalate immediately) when a transport modifying financial configuration is proposed for import during a production freeze without Finance Controls written approval — escalate to the Finance Controls lead and Release Governance Board before any other action.
+- Push back when asked to declare cutover GO without all required sign-offs confirmed in writing.
+- Push back when a freeze exception request is classified as non-critical but the requesting team cannot provide test evidence or a rollback plan.
+- Push back when a rollback is proposed for a financial configuration transport without Finance Controls written confirmation of the rollback impact on financial integrity.
+- Push back when asked to clear an irreversible-action gate without all required written approvals documented.
+- Push back when asked to confirm that a transport has no financial impact from the transport description alone — require Finance Controls classification based on the actual object list.
+- Push back when a hypercare production correction is proposed without Release Manager and Finance Controls approval, even if business pressure is high.
+
+## Evidence labels
+
+- `documentation-based` — grounded in SAP transport management, SAP Activate methodology, SAP Financial Closing Cockpit, SAP Revenue Accounting and Reporting, SAP Material Ledger, PCAOB AS 2201, or NIST SP 800-53 documentation
+- `user-provided evidence` — transport manifests, QA import results, collision analysis outputs, readiness checklist status, financial impact assessments, approval records, or incident records provided by the requesting function
+- `inference` — derived reasoning not directly confirmed by official documentation or user-provided evidence; must always be labeled as such and must not be used as the sole basis for any go/no-go decision or gate clearance

package/skills/sap/sap-release-cutover-finance-controls-protocol/references/workflow-and-output.md

@@ -0,0 +1,98 @@
+# Workflow and output contract — SAP Release Cutover Finance Controls Protocol
+
+Use this reference for all trigger classification, transport and cutover assessment sequencing, financial controls impact classification, decision rights application, and output formatting.
+
+## Trigger classification table
+
+| Trigger class | Primary signal | Activating agent(s) | Finance Controls involvement | Escalation risk |
+|---|---|---|---|---|
+| `transport-import` | Transport queue ready for production import | sap-release-change-collision-agent | Required if any transport has financial impact | Medium unless period-sensitive |
+| `freeze-exception` | Change request submitted during declared freeze | sap-release-change-collision-agent | Mandatory for all freeze exceptions | High |
+| `cutover-readiness` | Go-live cutover approaching; readiness checklist in progress | sap-data-migration-cutover-readiness-agent | Mandatory sign-off required | High |
+| `period-close-impact` | Transport modifies financial configuration during open period | sap-finance-fico-controls-agent | Mandatory; may be blocking | Critical |
+| `o2c-p2p-disruption` | O2C or P2P process interrupted by transport or migration | sap-release-change-collision-agent + sap-hypercare-incident-commander-agent | Required (business impact) | High |
+| `inventory-valuation` | Transport affects material ledger or cost estimate configuration | sap-finance-fico-controls-agent | Mandatory; balance sheet impact | Critical |
+| `revenue-recognition` | Transport affects RAR or SD billing configuration | sap-finance-fico-controls-agent | Mandatory; potential prior-period impact | Critical |
+| `hypercare-escalation` | Production incident during hypercare requiring correction transport | sap-hypercare-incident-commander-agent | Required if financial process affected | High |
+
+## Financial impact classification
+
+`sap-finance-fico-controls-agent` classifies each transport or cutover item using the following taxonomy:
+
+| Classification | Criteria | Approval gate |
+|---|---|---|
+| `no-financial-impact` | Transport contains no FICO, CO, SD billing, MM valuation, or RAR objects | Release Manager + Business Process Owner only |
+| `financial-configuration-change` | Transport modifies FICO/CO configuration objects (document types, posting period variants, account determination, tax codes, controlling area settings) | Release Manager + Finance Controls lead required |
+| `financial-posting-logic-change` | Transport modifies business logic affecting financial postings (pricing procedures, goods movement account assignment, output determination, revenue account mapping) | Release Manager + Finance Controls lead + Business Process Owner required |
+| `period-sensitive-financial-change` | Transport modifies any financial object that affects current or prior-period postings, or is being imported during a period-end close window | Release Manager + Finance Controls lead + CFO written approval required; import blocked during active closing cockpit run |
+| `revenue-recognition-impact` | Transport modifies RAR configuration, SD billing plan, contract account assignment, or multi-element arrangement allocation | Release Manager + Finance Controls lead + CFO; external auditor notification if prior-period revenue is affected |
+| `inventory-valuation-impact` | Transport modifies material ledger configuration, costing variants, valuation area assignment, or moving average price calculation | Release Manager + Finance Controls lead + CFO; balance sheet restatement risk must be assessed |
+
+## Protocol workflow
+
+### Phase 1 — Trigger classification (Release Manager)
+
+1. Classify the trigger condition using the table above.
+2. Identify which participating agents are activated.
+3. Request the required evidence inventory from the responsible function.
+4. Confirm whether the system is currently in a production freeze period.
+
+### Phase 2 — Transport and collision assessment
+
+1. `sap-release-change-collision-agent` performs collision analysis on all transports in the import queue.
+2. Collision findings are classified by severity (blocking / warning / informational).
+3. Transport manifest is confirmed complete and all transports have QA import evidence.
+
+### Phase 3 — Financial controls impact assessment
+
+1. `sap-finance-fico-controls-agent` classifies each transport by financial impact category.
+2. Period-close status is confirmed: is the financial closing cockpit running, are posting periods open or locked, and what is the period-end close task status?
+3. Revenue recognition and inventory valuation impact are assessed for any transports classified `period-sensitive-financial-change`, `revenue-recognition-impact`, or `inventory-valuation-impact`.
+4. Blocking conditions are identified and communicated to the Release Manager.
+
+### Phase 4 — Cutover readiness assessment (if applicable)
+
+1. `sap-data-migration-cutover-readiness-agent` evaluates the readiness checklist.
+2. Open items are classified as blocking or non-blocking.
+3. Rollback plan completeness is confirmed.
+4. Go/no-go posture is determined based on checklist status and Finance Controls sign-off.
+
+### Phase 5 — Hypercare triage (if applicable)
+
+1. `sap-hypercare-incident-commander-agent` classifies incident severity and business impact.
+2. Workaround status and resolution timeline are assessed.
+3. If a production correction transport is required, it is proposed to the approval chain and queued to `sap-guarded-transport-import-operator-agent` only after all approvals are confirmed.
+
+### Phase 6 — Approval gate confirmation and audit package assembly
+
+1. Each required approval is confirmed present or flagged as outstanding.
+2. Irreversible-action gate is evaluated for each proposed action.
+3. Audit package is assembled and residual risk is documented.
+
+## Go/no-go decision criteria
+
+A release, cutover, or freeze exception is GO only when all of the following are true:
+
+- No unresolved transport collisions classified as blocking.
+- All transports classified `financial-configuration-change` or higher have Finance Controls written approval.
+- No transport classified `period-sensitive-financial-change` is being imported while the Financial Closing Cockpit is running an active close task for the affected company code.
+- All required business process owner sign-offs are documented.
+- A pre-approved rollback plan exists for all high-risk or period-sensitive transports.
+- For cutover: all checklist items are green or exceptions are documented with named acceptance owners and Finance Controls concurrence.
+
+Any single condition not met results in a NO-GO posture. The NO-GO condition, the owner responsible for clearing it, and the required action must be stated explicitly in the response.
+
+## Output contract
+
+Return, in order:
+
+1. **Trigger classification**: Which trigger class(es) apply; which participating agents are activated.
+2. **Transport or cutover scope**: Items assessed, financial impact classification per item, and collision status.
+3. **Go/no-go posture**: GO or NO-GO, with every blocking condition listed explicitly and the responsible owner for each.
+4. **Financial controls assessment**: Period-close status, financial impact classifications, and any blocking financial controls findings.
+5. **Rollback plan status**: Pre-approval status for each high-risk or period-sensitive item, rollback trigger conditions, and rollback duration estimate.
+6. **Approval gate status**: For each required approval, primary authority, documentation status (present / outstanding), and gate status (cleared / blocked).
+7. **Irreversible-action gate**: Whether any irreversible actions are pending, approval status, and whether the gate is cleared or blocked.
+8. **Escalation notice**: If a financial configuration import is pending during a freeze without Finance Controls approval, if revenue recognition or inventory valuation impact is identified, or if a SOX IT general control failure is detected — escalation notice must appear before any other recommendation, naming escalation owners.
+9. **Audit package status**: Populated items and outstanding items.
+10. **Next step**: Single next action with named responsible owner and required completion timeframe if period-sensitive.

package/skills/sap/sap-rise-sla-vendor-risk-review/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: sap-rise-sla-vendor-risk-review
+description: Advisory review of RISE with SAP and SAP cloud service contracts for SLA and vendor risk: responsibility split between SAP, customer, and partner; SLA tiers and credit mechanisms; availability and DR commitments; data residency; exit and portability obligations; shared security responsibilities; and audit rights. Does not touch or mutate any live system.
+allowed-tools: Read Grep Glob WebSearch WebFetch
+metadata:
+  author: "github: Raishin"
+  version: "0.1.0"
+  updated: "2026-06-19"
+  category: compliance
+  lifecycle: experimental
+---
+
+# RISE with SAP SLA and Vendor Risk Review
+
+## Purpose
+
+Assess the vendor risk and SLA posture of a RISE with SAP engagement or SAP cloud service agreement. Evaluate the contractual responsibility split between SAP, the customer, and the system integrator or partner; SLA tier definitions and credit mechanisms; system availability and disaster recovery commitments; data residency and cross-border transfer obligations; exit and data portability clauses; the shared responsibility model for security; and audit and compliance rights. Surface contractual gaps, ambiguous responsibility boundaries, weak SLA credit structures, and missing exit provisions that represent vendor lock-in or compliance risk. Does not connect to or mutate any live system, contract management platform, or SAP environment.
+
+## When to use
+
+Use this skill when the user asks to:
+
+- review a RISE with SAP contract or cloud service agreement for SLA gaps, vendor risk, or responsibility ambiguity,
+- assess the contractual responsibility split between SAP, the customer, and the implementation partner across infrastructure, application, and data layers,
+- evaluate SLA tier definitions, availability commitments, and credit mechanisms for adequacy against business continuity requirements,
+- review disaster recovery and business continuity commitments in a RISE with SAP or SAP cloud service agreement,
+- assess data residency clauses and cross-border data transfer obligations in an SAP cloud contract,
+- review exit and data portability provisions in a RISE with SAP agreement to understand vendor lock-in risk,
+- evaluate the shared security responsibility model between SAP and the customer for a RISE with SAP or SAP BTP engagement,
+- assess audit rights and third-party certification commitments (ISO 27001, SOC 2, etc.) in an SAP cloud service agreement,
+- prepare for contract renegotiation, renewal, or escalation with SAP,
+- support a compliance or legal review of SAP cloud obligations.
+
+## When not to use
+
+- When the request requires live access to the SAP contract management portal or a specific signed contract document — this skill accepts only user-provided contract excerpts, term summaries, or written descriptions.
+- When the request concerns SAP BTP account model governance — use `sap-btp-governance-review`.
+- When the request concerns SAP licensing cost optimization or BTP consumption FinOps — use `sap-license-btp-consumption-finops-review`.
+- When the request concerns the technical transformation program structure — use `sap-transformation-portfolio-triage-review`.
+- When the request requires legal advice on contract terms — this skill provides advisory risk classification, not legal counsel.
+
+## Does not touch live systems
+
+This skill operates on user-provided contract excerpts, term summaries, SAP Trust Center publications, SAP cloud service descriptions, or written descriptions of contractual obligations. It does not connect to any SAP system, SAP contract management portal, SAP for Me, or any live environment. All live inspection is out of scope.
+
+## Lean operating rules
+
+- Classify responsibility before assessing risk. Every SLA or security finding must be classified by responsibility layer (SAP-managed / customer-managed / partner-managed / shared) before a risk level is assigned.
+- Use SAP's published shared responsibility model as the baseline. SAP publishes responsibility matrices for RISE with SAP and SAP BTP that define what SAP manages and what the customer manages at infrastructure, platform, application, and data layers. Deviations from this baseline in the user's contract are risk findings.
+- SLA credit mechanisms must be evaluated against recovery time objectives. An SLA credit that compensates financially but does not include service restoration guarantees does not address business continuity risk.
+- Data residency obligations must map to actual processing locations. A contractual data residency clause is only as strong as the accompanying technical controls and audit evidence. Flag clauses where residency is stated but audit rights to verify it are absent.
+- Exit and portability provisions must specify format, timeline, and cost. A portability clause that does not specify the data export format, the export timeline, and whether export is at SAP's cost or the customer's cost is not an effective exit provision.
+- Audit rights must be specific. A generic audit rights clause without specifying the audit mechanism (customer right to audit, third-party certification, or SAP-provided audit report) does not provide meaningful assurance.
+- Do not conflate RISE with SAP scope with SAP S/4HANA Public Cloud scope. RISE with SAP is a commercial bundling model; the underlying technical scope depends on whether the customer is on S/4HANA Private Cloud Edition or S/4HANA Cloud Public Edition. The responsibility split differs significantly between these two.
+- Evidence from user-provided contract text or SAP Trust Center publications takes precedence over inference.
+- Load only the reference needed for the contract domain under review.
+
+## Evidence rules
+
+Label all claims with one of:
+
+- `documentation-based` — grounded in SAP Trust Center publications, SAP cloud service descriptions, SAP shared responsibility documentation, or official SAP contractual framework documentation
+- `user-provided evidence` — contract excerpts, term summaries, SLA schedules, or written descriptions of contractual obligations provided by the user
+- `inference` — derived reasoning not directly confirmed by official SAP publications or user-provided contract text
+
+## Live-environment rules
+
+**This skill does not touch live systems.** There is no API call, contract management portal access, SAP system connection, SAP for Me login, or any live environment access in this skill's execution path. Users must supply contract excerpts, SAP Trust Center documentation references, SLA schedules, or written descriptions of their RISE with SAP or SAP cloud service obligations for this skill to review.
+
+## References
+
+Load only when needed:
+
+- [Workflow and output contract](references/workflow-and-output.md) — responsibility layer taxonomy, risk severity classification, SLA and vendor risk assessment criteria, output format.
+- [Safety checklist](references/safety-checklist.md) — non-negotiables, common contract review mistakes, when to push back.
+- [Official sources](references/official-sources.md) — SAP Trust Center, RISE with SAP shared responsibility documentation, SAP cloud service descriptions, data processing agreements.
+
+## Response minimum
+
+Return, at minimum:
+
+- **Problem classification**: contract domain(s) affected (responsibility split / SLA and credits / availability and DR / data residency / exit and portability / security responsibilities / audit rights) and specific finding(s).
+- **Evidence used**: documentation-based / user-provided evidence / inference.
+- **Risk level**: critical (contractual gap creating unmanaged compliance, regulatory, or business continuity exposure) / high (ambiguous responsibility boundary or weak SLA credit mechanism with material business impact) / medium (missing provision that is negotiable but currently absent) / low (best practice deviation in contract structure or language).
+- **Recommended action**: specific contractual or operational remediation per finding (renegotiate clause, request SLA schedule addendum, obtain SAP Trust Center certification evidence, implement compensating control, clarify responsibility matrix).
+- **Refusal / escalation triggers**: if legal interpretation of contract terms is required, state that this skill provides risk classification only and that legal counsel must be engaged. If access to the signed contract is required, state that and request the user provide the relevant excerpts.
+- **Business impact**: regulatory non-compliance risk, business continuity exposure, vendor lock-in risk, or audit finding risk.
+- **Next verification step**: validate responsibility and SLA findings against the signed contract schedule and current SAP Trust Center publications before escalating.

package/skills/sap/sap-rise-sla-vendor-risk-review/agents/openai.yaml

@@ -0,0 +1,11 @@
+interface:
+  display_name: "RISE with SAP SLA and Vendor Risk Review"
+  short_description: "Advisory review of RISE with SAP and SAP cloud service contracts: responsibility split, SLA tiers and credit mechanisms, availability and DR commitments, data residency, exit and portability provisions, shared security responsibilities, and audit rights."
+  default_prompt: "Use $sap-rise-sla-vendor-risk-review to assess the provided RISE with SAP or SAP cloud service contract for SLA gaps and vendor risk. Classify each finding by contract domain (responsibility split, SLA and credits, availability and DR, data residency, exit and portability, security responsibilities, audit rights), assign a risk level (critical/high/medium/low), and recommend specific contractual or operational remediation actions. State evidence level for each finding and escalate to legal counsel when contract interpretation is required."
+dependencies:
+  tools:
+    - type: "web"
+      value: "https://www.sap.com/about/trust-center/cloud-service-agreements.html"
+      description: "SAP Trust Center cloud service agreements — primary reference for RISE with SAP contractual framework, SLA schedules, and shared responsibility model"
+policy:
+  allow_implicit_invocation: true

package/skills/sap/sap-rise-sla-vendor-risk-review/metadata.json

@@ -0,0 +1,32 @@
+{
+  "id": "sap-rise-sla-vendor-risk-review",
+  "name": "RISE with SAP SLA and Vendor Risk Review",
+  "type": "skill",
+  "provider": "sap",
+  "harnesses": [
+    "claude-code",
+    "codex",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Advisory review of RISE with SAP and SAP cloud service contracts for SLA and vendor risk: responsibility split (SAP vs customer vs partner), SLA tiers and credit mechanisms, availability and DR commitments, data residency, exit and portability, shared security responsibilities, and audit rights. Does not access live systems.",
+  "source_type": "original",
+  "category": "compliance",
+  "official_docs": [
+    "https://www.sap.com/about/trust-center/cloud-service-agreements.html",
+    "https://www.sap.com/about/trust-center/security.html",
+    "https://www.sap.com/about/trust-center/data-privacy.html",
+    "https://help.sap.com/docs/RISE/rise-with-sap/rise-with-sap",
+    "https://www.sap.com/about/trust-center/availability.html",
+    "https://support.sap.com/en/my-support/systems-installations/cac.html",
+    "https://www.sap.com/about/trust-center/shared-responsibility-model.html"
+  ],
+  "security_notes": "Does not access live SAP systems, contract management portals, SAP for Me, or any signed contract repositories. Accepts only user-provided contract excerpts, term summaries, SLA schedules, or written descriptions of contractual obligations. Never request or accept SAP contract portal credentials, customer-specific contract identifiers, or confidential commercial terms beyond what the user voluntarily provides. Risk classifications are advisory only and do not constitute legal advice — legal counsel must be engaged for binding contract interpretation.",
+  "last_verified": "2026-06-19",
+  "path": "skills/sap/sap-rise-sla-vendor-risk-review",
+  "author": "github: Raishin",
+  "version": "0.1.0",
+  "lifecycle": "experimental"
+}