Boundary & ownership
Define candidate GSS components, external dependencies, provider responsibilities, control ownership, and decision authority.
WORKSTREAM 01 · GSS FOUNDATIONS
Design the environment applications will enter.
Foundations turns mission knowledge, existing artifacts, and stakeholder decisions into an attested design for the General Support System—before or alongside landing-zone delivery.
CLOUD FOUNDATIONJWCC landing zone / cloud platform
SECURITY & IDENTITYBoundaries · access · policy patterns
GSS OPERATING LAYERShared services · evidence · operations
MISSION WORKLOADSApplication communities
APPROXIMATELY SIX WEEKS
A foundation milestone inside a larger readiness journey.
This workstream establishes what the future GSS is expected to contain, support, secure, and operate. It can start early and then continue to mature as observed dependency evidence becomes available. It does not promise or replace an ATO.
What the mission says must be true.
Shared services
Identify identity, network, logging, monitoring, data, platform, and security services applications will rely upon.
Target patterns
Describe repeatable landing, connectivity, migration, and operating patterns without prematurely locking implementation.
Authorization inputs
Organize architecture, data flows, inherited controls, evidence needs, risks, and open decisions for the responsible authorization teams.
Migration assumptions
Document current constraints, likely migration paths, sequencing conditions, and what requires observed validation.
Operating model
Establish future roles, provider handoffs, service ownership, change paths, continuous monitoring, and skills implications.
Foundation hypotheses become testable.
Dependency mapping can confirm, refine, or challenge the declared architecture. That feedback loop makes the target environment more defensible—and prevents migration planning from inheriting undocumented assumptions.