ARCPartner KM OSLaunch partner control plane

Interview path

Demo Flow

Show the operating loop from public source to partner signal, review, Salesforce-compatible update, and partner-facing action.

Step 1

Source event

Public docs, RSS, Arcscan, status, GitHub, or API source changes.

Step 2

Signal extraction

Adapter emits partner, category, confidence, field update, and suggested action.

Step 3

Human review

Owner confirms the claim before Salesforce or partner-facing updates.

Step 4

System update

Salesforce-compatible object gets a sourced, auditable proposed write.

Step 5

Partner loop

Partner receives a clear update and the feedback loop closes back to Product.

What To Show First
Start with blocked day-one readiness, not the source registry.
Open the Bridge/Gateway dossier to show launch gates and route evidence.
Move to Review Queue to show AI leverage with human control.
Close on Salesforce compatibility and the partner update loop.
Live Demo State
Blocked partners
2
Review actions
3

Fact: this is a local mock PoC. Assumption: real Circle deployment would connect reviewed writes to Salesforce objects and authenticated source adapters.