key,summary,details,category,agent,requester_email,team,sla,priority,parent_key,asset_keys,target_date,CFchangeType,CFChangeTypeExplanation,CFjustification,CFImpact,CFCustomerImpact,CFRisk,CFChangePlanMemo,CFChangeTestPlanMemo,CFChangeImplementationPlanMemo,CFChangeBackoutPlanMemo,CFCommunicationPlan,CFSecurityImpactAnalysis,CFoutageRequired,CFoutageDuration
cr-patch-window,September routine patch window,Monthly routine patch window covering the OS and container tiers. Carries the regreSSHion remediation on the web and application tier hosts and the patched Spring Framework image promotion.,Continuous Monitoring>Flaw Remediation,Demo Account,,Continuous Monitoring,,,,,2026-09-04,Routine Recurring,Recurring monthly maintenance under the approved patch procedure; no boundary or architecture change.,Scheduled remediation of operating system and application dependency findings within their PAIN-driven remediation windows.,Multiple Users Affected,,Low Risk,"Patch the web and application tier hosts to a fixed OpenSSH release, promote the patched application container image, and recycle the EKS node groups in a rolling fashion.","Verify sshd version on each host, run the application smoke suite against the patched image in staging, and confirm inference latency is unchanged on the GPU node group.",Rolling replacement one availability zone at a time behind the load balancer; the audit log database and vector store are untouched.,Re-promote the prior container image and roll back the node group launch template to the previous AMI. Both prior artifacts are retained in the registry with immutability enabled.,"Maintenance notice to agency administrators seven days ahead through the portal, with a follow-up on completion.","Reduces exposure on two operating system findings and one application dependency finding. No change to the authorization boundary, data flows, or interconnections.",No,None; rolling replacement keeps the service available
cr-adaptive-inference,Add GPU inference capacity in a second AZ,Adaptive change extending the model inference tier into a third availability zone to meet agency demand. Adds node group capacity within the existing boundary and updates the certification data describing the inventory.,Engineering>Deployment,Demo Account,,Continuous Monitoring,,,,,2026-09-30,Adaptive,Adapts existing authorized capability to increased demand. Inventory and certification data change; no new service type or data flow is introduced.,Inference queue depth exceeds the target service level during peak agency hours.,Company Wide,,Medium Risk,"Extend the EKS GPU node group into the third availability zone using the existing launch template, baseline configuration, and admission policy.","Confirm the new nodes register with the cluster, pass the configuration baseline scan, and serve inference with tenant isolation intact by running the multi-tenant retrieval test suite.","Scale the node group, verify baseline compliance, then admit production traffic gradually.",Reduce the node group to its prior availability zones; no data migration is involved.,Notify the agency administrators and update the significant change record feeding the certification data report.,Inventory grows by additional nodes under the same baseline and controls. The authorization boundary is unchanged. Certification data reporting must reflect the new inventory count.,No,None
cr-transformative-model,Replace the embedding model family,"Transformative change replacing the self-hosted embedding model with a newer family, requiring re-embedding of every tenant corpus and a new model artifact lineage.",Engineering>Development,Demo Account,,Continuous Monitoring,,,,,2026-11-14,Transformative,"Changes how the service derives and stores tenant embeddings, altering a core data-processing behavior described in the data flow narrative.",The newer embedding family materially improves retrieval quality on agency document sets and reduces inference cost per request.,Company Wide,,High Risk,"Stage the new model artifacts in the object-locked model bucket, re-embed each tenant corpus into a parallel vector namespace, validate retrieval quality per tenant, then cut over and retire the prior namespace.","Per-tenant retrieval regression against a held-out question set, tenant isolation verification confirming no cross-tenant vector access, and a rollback rehearsal in staging.","Parallel-run both namespaces with traffic shifted per tenant, oldest corpus first, holding the prior namespace until every tenant is validated.","Shift retrieval back to the prior vector namespace, which is retained until the change is formally closed.","Advance notice to agency administrators, a significant change notification to FedRAMP, and per-tenant validation sign-off before cutover.",Data processing behavior changes and every tenant embedding is regenerated. Tenant isolation is the critical control and is re-verified per tenant. Requires a significant change notification.,No,None; parallel namespaces avoid an interruption
