journey

Data 360 & Agentforce Bootcamp

Unzip the archive, then run git init in that folder to track your work locally. Phase 0 scripts and Entry prompts live inside the zip.

Thin Journey intro for the Bootcamp.

Step 0 · scaffold

Scaffold & Proctor

Confirm Org 1 is Data 360–capable, run Phase 0 install from the Lab Repo, and open the Proctor.

# Step 0 — Scaffold & Proctor

## Goal

Confirm Org 1 is ready (including Agentforce Agents activated), run Phase 0 install from this Lab Repo, open the Bootcamp Proctor, and pass Check-My-Work for step 0 (baseline + Proctor install markers).

## Hard rules

- Never ask the Proctor to configure Data 360 (or any Lab canvas) for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.
- Org 2 is **not** required for this step (or for Phase 0).

## First message

Start step 0

Step 1 · ingest

Ingest CRM + CSV

Connect a CRM stream and run CLI CSV ingest so Data Lake Objects hold the fixture row counts.

# Step 1 — Ingest CRM + CSV

## Goal

Connect a CRM stream and run CLI CSV ingest so Data Lake Objects hold the fixture row counts this Lab expects.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.

## First message

Start step 1

IDE pit stop

CLI sf data import bulk --file data/accounts.csv

Repo data/accounts.csv

Step 2 · harmonize

Harmonize to CIM

Map DLO fields to CIM DMOs so required mappings populate and the dependency story stays coherent for later IR and graphs.

# Step 2 — Harmonize to CIM

## Goal

Map ingested DLO fields to CIM DMOs so required mappings populate and the dependency story stays coherent for later IR and graphs.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.

## First message

Start step 2

Step 3 · identity-resolution

Identity Resolution

Build an IR ruleset with reconciliation and run it so UnifiedIndividual links land in band.

# Step 3 — Identity Resolution

## Goal

Build and run an IR ruleset with reconciliation so UnifiedIndividual (and links) exist and merge rate stays in the Lab band.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.

## First message

Start step 3

Step 4 · insights-data-graph

Insights + Data Graph

Create calculated insights and build a Data Graph so CI rows exist and the graph materializes.

# Step 4 — Insights + Data Graph

## Goal

Create Calculated Insights and build a Data Graph so CI rows exist and the graph compiles/materializes.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.

## First message

Start step 4

Step 5 · governance-trust

Governance & Trust

Apply classification and masking (plus Trust Layer as needed) on sensitive unified fields.

# Step 5 — Governance & Trust

## Goal

Apply classification and masking (and Trust Layer as needed) so sensitive unified fields are masked.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.

## First message

Start step 5

Step 6 · enrich-crm

Enrich CRM records

Surface the Data Graph on Contact and Account so enrichment shows on sample records.

# Step 6 — Enrich CRM records

## Goal

Surface the Data Graph on Contact/Account so enrichment appears on sample CRM records.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.

## First message

Start step 6

Step 7 · unstructured-search

Unstructured search

Chunk and embed content, then build a hybrid search index with expected sample hits.

# Step 7 — Unstructured search

## Goal

Chunk/embed content and build a hybrid search index so the index is ready and sample hits match fixtures.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.

## First message

Start step 7

Step 8 · ground-agentforce

Ground Agentforce

Ground a Service Agent and verify Trust Layer so probes show grounded, masked behavior.

# Step 8 — Ground Agentforce

## Goal

Ground a Service Agent and verify Trust Layer so probes show grounded, masked behavior.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.
- Do not use grounding/`prompt://` as Check-My-Work scorers—verification stays in Apex/Flow actions.

## First message

Start step 8

Step 9 · segment-activate

Segment & activate

Build a segment, publish an activation, and confirm members land in the activation hub.

# Step 9 — Segment & activate

## Goal

Build a segment, publish an activation, and confirm members/hub so the Org 1 journey can stop here as a complete experience.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.
- Org 2 is still not required.

## First message

Start step 9

Step 10 · devops-org2

DevOps: kit → Git → Org 2

Create Org 2 DE, package a Data Kit, retrieve/commit, validate and deploy to Org 2, then re-link and smoke-test.

# Step 10 — DevOps: kit → Git → Org 2

## Goal

**Create Org 2 DE**, package a Data Kit, retrieve/commit, validate+deploy to Org 2, then re-link and smoke-test so the kit is active in Org 2.

## Hard rules

- Never ask the Proctor to configure Data 360 for you.
- Checks run only via named Check-My-Work actions—not grounding or invented SQL.
- Org 2 provisioning belongs to this step—not Phase 0.

## First message

Start step 10