Decision owner
Relationship manager and supervisor
The named role remains accountable for the consequential decision.
Banking & Capital Markets
Designed for Relationship manager
Prepare a relationship manager for every client conversation by merging holdings, transaction behaviour, CRM history, and approved research into a cited briefing, with suitability review before any recommendation is shared.
Contract BAN-01 · primary aggregate ClientRelationship · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Relationship manager and supervisor
The named role remains accountable for the consequential decision.
Governed evidence
5 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
Before a quarterly review the copilot shows a client group holding 31 percent cash after a business sale, cites the approved fixed-income commentary, proposes a laddered deployment, flags that the mandate caps duration at five years, and holds the idea until the supervisor approves the suitability rationale..
Prepare a relationship manager for every client conversation by merging holdings, transaction behaviour, CRM history, and approved research into a cited briefing, with suitability review before any recommendation is shared.
Released briefing and logged advice record gives Relationship manager and supervisor the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Relationship manager and supervisor verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Briefing service performs assemble relationship and holdings context using Client group id and upcoming meeting and produces Consolidated relationship snapshot. The transition is deterministic and does not require autonomous model approval.
Why it matters: Consolidated relationship snapshot gives Analytics agent the evidence needed to begin Detect portfolio drift and cash build-up, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/assemble-relationship-and-holdings-context
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Analytics agent performs detect portfolio drift and cash build-up using Positions versus mandate targets and produces Drift and concentration findings. The transition is deterministic and does not require autonomous model approval.
Why it matters: Drift and concentration findings gives Research retrieval agent the evidence needed to begin Ground ideas in approved research, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/detect-portfolio-drift-and-cash-build-up
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Research retrieval agent performs ground ideas in approved research using Findings and client objectives and produces NextBestActionCandidate set with citations. The transition is deterministic and does not require autonomous model approval.
Why it matters: NextBestActionCandidate set with citations gives Suitability engine the evidence needed to begin Run suitability and conflict screening, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/ground-ideas-in-approved-research
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Suitability engine performs run suitability and conflict screening using Candidate actions and client risk profile and produces Screened candidates with blocking flags. The transition is deterministic and does not require autonomous model approval.
Why it matters: Screened candidates with blocking flags gives Relationship manager and supervisor the evidence needed to begin Approve the client-facing briefing, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/run-suitability-and-conflict-screening
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Relationship manager and supervisor performs approve the client-facing briefing using Screened briefing pack and produces Released briefing and logged advice record. A named human approver must review the evidence before the transition completes.
Why it matters: Released briefing and logged advice record gives Relationship manager and supervisor the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/approve-the-client-facing-briefing
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved ClientRelationship evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
clientRelationships/tenantId + /clientGroupIdBefore a quarterly review the copilot shows a client group holding 31 percent cash after a business sale, cites the approved fixed-income commentary, proposes a laddered deployment, flags that the mandate caps duration at five years, and holds the idea until the supervisor approves the suitability rationale.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
clientRelationships |
Primary | /tenantId + /clientGroupId |
ClientRelationship, PortfolioPosition, InteractionNote, NextBestActionCandidate |
approvedResearchLibrary |
Reference | /tenantId + /researchId |
ResearchNote |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
ClientRelationship |
clientRelationships |
/tenantId + /clientGroupId |
relationship::{clientGroupId} |
None |
PortfolioPosition |
clientRelationships |
/tenantId + /clientGroupId |
position::{clientGroupId}::{accountId}::{instrumentId} |
None |
InteractionNote |
clientRelationships |
/tenantId + /clientGroupId |
interaction::{clientGroupId}::{interactionId} |
summaryVector |
ResearchNote |
approvedResearchLibrary |
/tenantId + /researchId |
research::{researchId}::{chunkIndex} |
bodyVector |
NextBestActionCandidate |
clientRelationships |
/tenantId + /clientGroupId |
action::{clientGroupId}::{candidateId} |
rationaleVector |
Single partition read of relationship, positions, and recent interactions for the meeting pack.
clientRelationships
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.clientGroupId = @clientGroupId AND c.type IN ('ClientRelationship','PortfolioPosition','InteractionNote') ORDER BY c.asOfUtc DESC
Identify positions breaching single-issuer or asset-class concentration limits.
clientRelationships
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.clientGroupId = @clientGroupId AND c.type = 'PortfolioPosition' AND c.marketValue > @concentrationThreshold ORDER BY c.marketValue DESC
Knowledge-container query against approvedResearchLibrary (bounded fan-out across the /tenantId + /researchId partitions named by the shortlist): restrict cited commentary to research that passed compliance approval, as a bounded fan-out over the research ids returned by vector shortlisting.
approvedResearchLibrary
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.researchId IN (@shortlistedResearchIds) AND c.type = 'ResearchNote' AND c.approvalStatus = 'approved' AND c.publishedUtc > @lookbackUtc ORDER BY c.publishedUtc DESC
Partition-key fan-out control-plane query: list proposed actions waiting on supervisor sign-off across the whole coverage book. It cannot carry the second partition key because a supervisor queue spans every client group the desk covers, so it runs as a tenant-scoped scheduled sweep off the interactive path, bounded by the pendingReview state and a 14-day createdUtc window, executed with MaxItemCount paging and continuation tokens.
clientRelationships
partition-key-fan-out
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.type = 'NextBestActionCandidate' AND c.reviewState = 'pendingReview' ORDER BY c.createdUtc ASC