Discovery and Diagnose
The front of the platform. Stand up a discovery client, upload the filled instrument, and run Polygon in diagnose mode. The plan it returns is reviewed and approved here at the first human gate before anything is provisioned.
Discovery clients
New discovery client
Plan review
Human gate one. Read what Polygon proposes, edit if needed, and approve. Approval is what unlocks provisioning in the next stage.
Proposed plan
Engagements
Provisioned engagements live here
Once a diagnose plan is approved, provisioning becomes a consequence of that plan: standing data containers, the acquisition channels the plan selected, and refresh instead of one-shot processing. That control surface is built in the next segment.
Segment 2Build
Data foundations, fired from here
When an approved plan calls for Build, this is where the foundation is stood up and watched: the dedicated foundations store, the Glue and Athena layer that turns captured inputs into curated tables, and the handoff into a Polygon corpus once the foundation holds data. Built in the next segment.
Segment 2Ledgers
The audit view of every engagement
The operations ledger made visible: what data landed, what each dataset reconciled to, what was processed, refreshed, and archived, with the full timeline per engagement. The standing data model writes it; this is where you read and control it. Built in the next segment.
Segment 2Journal Spaces
Open and manage analytical spaces
Fire a SageMaker journal space for an engagement straight from here, with the synced clean corpus and the seed notebook already in place. This is the handoff into deep modeling and Power BI, all inside AWS.
Segment 4