Advisors Platform Trust Intelligence Services Who We Serve About Contact

Why it matters

Three jobs. Not an architecture diagram.

The wealth stack carries the book. The trust desk carries the instrument. The next recommendation needs both in one layer — without replacing custody, the PMS, or the trustee of record.

01 · Pre-trade

Pre-trade constraint check

See whether a proposed sale or buy collides with retention, concentration, or directed-investment language before the ticket is discussed.

The agent may propose
A cited note: the holding is named in the abstract, with the clause beside the position.
You still approve
Whether to recommend the trade, hold, or take it to the officer. The note is not a ticket.
See it on a synthetic book →

02 · Client call

Distribution capacity

Know HEMS or an ascertainable standard, plus administrative state, before the client call — not after a request is already in motion.

The agent may propose
A capacity memo: standard as written, last officer decision, cash and principal facts from the book.
You still approve
What you tell the client. You do not authorize the distribution. The trustee of record does.
See it on a synthetic book →

03 · Compensation

Fee and IPS reconciliation

Reconcile the schedule, the instrument’s fee basis, and what the advisor is charging or recommending — including wrap or offset — before it hits a statement.

The agent may propose
A recon note: schedule line, instrument clause, current advisory charge. Variance classified, not quietly netted.
You still approve
Whether the fee recommendation stands. The CCO still owns Form CRS and the ADV process.
See it on a synthetic book →

Plain English first. The legal term stays visible.

Can we sell the concentrated stock?
Retention / concentration clause
Can we take this withdrawal?
Distribution standard (HEMS / ascertainable)
Who is allowed to decide investments?
Investment authority (prudent investor, expanded, or directed)
Is this fee the one the document allows?
Fee basis

See a trust next to a book

The crossing, not the engine.

You keep booking trades where you book them. r.Team reads enough of the book and the instrument to make the recommendation reconcilable — then stops for you.

Sequence: portfolio system and custodian, then a read-only Bridge, then the instrument and administrative state, then a proposed note, then the advisor decision, then the record.
  1. Portfolio / PMS + custodian Where the book is held and traded
  2. Bridge (read) Read-only first. No silent writes
  3. Instrument + admin state Constraints, standard, last officer decision
  4. Proposed note Cited. Not a ticket. Not a distribution
  5. Advisor decision You still make the recommendation
  6. Record Workpaper beside the recommendation

You do not change where the trade is booked. You change whether the recommendation is reconcilable.

For CCOs and examiners — proof and the hash-chained record live on the Platform page, not here.

A public synthetic account is on this site. No client names, no account numbers. Open the sample book.

What agents may propose

Propose a note. You still make the recommendation.

Agents prepare cited notes: a constraint collision, a capacity memo, a fee recon, a classification of who may decide investments. They do not place trades, authorize withdrawals, or speak as counsel.

Same facts as the trust officer, in your workflow. The proposal is a structured object — clause, holding, last administrative event — so you can accept, reject, or ask why. Recipes that encode these jobs live in Agent Studio for RIAs.

What you still decide

What the platform does not do

This section matters. Advisors read it first.

It does not become the trustee of record.

It does not replace custody or the portfolio system.

It does not authorize a distribution.

It does not give a legal opinion.

It does not file Form CRS or replace the advisor’s own fiduciary process under the Advisers Act.

Agents propose. Humans decide. Nothing writes through the Bridge until a named person approves.

Advice, administration, disclosure

For dual-registrants, the same output is not always the same kind of act. r.Team routes the workpaper; it does not file Form CRS and it does not run the advisor’s ADV process.

Produces the workpaper your CCO can file next to the recommendation.

Output Kind What that means
Pre-trade constraint note Administration / workpaper Context beside the book. Not itself a buy or sell recommendation.
Distribution-capacity memo Administration Trustee and officer function. The advisor does not authorize the withdrawal.
Fee-basis recon Administration / compliance Schedule vs instrument vs charge. Not a substitute for Form CRS or the ADV.
Proposed sale or buy Advice The advisor still makes the recommendation. The agent does not ticket it.
Recorded decision and citations Disclosure-ready record Supports the firm’s own process. r.Team does not file the disclosure.
  • Pre-trade constraint note Administration / workpaper Context beside the book. Not itself a buy or sell recommendation.
  • Distribution-capacity memo Administration Trustee and officer function. The advisor does not authorize the withdrawal.
  • Fee-basis recon Administration / compliance Schedule vs instrument vs charge. Not a substitute for Form CRS or the ADV.
  • Proposed sale or buy Advice The advisor still makes the recommendation. The agent does not ticket it.
  • Recorded decision and citations Disclosure-ready record Supports the firm’s own process. r.Team does not file the disclosure.

How it attaches

Read-only first. Then prove. Then you decide what may write.

The Bridge connects to systems you already run. You do not rip and replace to see the instrument beside the book.

  • Custody Positions, cash, corporate actions Read-only first
  • PMS / reporting Holdings, performance, proposed trades Read-only first
  • CRM Household and relationship context Read-only first

Writes only after a named person approves. The portfolio system stays the portfolio system. Prove on your book before anything writes — the same Bridge, then prove, then authorize path as the rest of the Platform.

Reviewed terms from Trust Intelligence become context once an officer releases them. You are not working from a stale memo. The Reasoning Engine is shared with the trust team — same facts, your workflow.

Agent Studio recipes for RIAs

Governed sequences. Each one stops where a human must.

Static recipes — not a live catalog. Compose them in Agent Studio. Review tiers are the same gates used on the Platform.

Interpretive · advisor + officer

Pre-trade retention-clause checker

Reads
Instrument abstract (retention / concentration / directed language) and the proposed sale or buy against the book.
Proposes
A cited collision or an all-clear note. Never a ticket.
Human stop
Advisor decides the recommendation. Officer confirms the clause if the note is interpretive.
Agent Studio →

Interpretive · officer decides the gift

HEMS capacity memo before a planned gift

Reads
Distribution standard as written, last administrative decision, cash and principal on the book.
Proposes
A capacity memo the advisor can take into the client call. Not an authorization.
Human stop
Trustee or officer authorizes any distribution. The advisor does not.
Agent Studio →

Structural / interpretive

Directed-trustee vs advisor-discretion classifier

Reads
Investment authority in the instrument: prudent investor, expanded, or directed.
Proposes
A classification of who is allowed to decide investments on this account.
Human stop
Advisor and officer confirm the classification before anyone relies on it.
Agent Studio →

Structural / interpretive

Fee-offset / wrap vs instrument fee-basis recon

Reads
Fee schedule, instrument fee basis, current advisory charge or wrap.
Proposes
A recon of what is allowed vs what is being charged or recommended.
Human stop
Advisor owns the fee recommendation. CCO owns Form CRS and the ADV. The agent files neither.
Agent Studio →

Clerical / structural

Stale-abstract watcher

Reads
Document-management restatement events against the released abstract version.
Proposes
A notice that the abstract may be stale when a restatement lands in the DMS.
Human stop
Officer or counsel reviews the new instrument. Abstracts cite. They do not conclude.
Agent Studio →

Sit the challenge

Sit this week’s advisor drill (8 items, 6 minutes).

Same stems, human and agent, miss by miss. Synthetic instruments only.

Bring this question: This trust retains the founder’s stock. May I rebalance?

Open rAgent.team

If the destination does not accept the query string, paste the question there. No client file leaves this site.

Demo

See the instrument beside the book — at the desk, not in a terminal.

A focused walkthrough for an advisory practice. Agents prove themselves against your live system before they write. Custody and the portfolio system stay yours.

A short desk clip will sit here — constraint, book, proposed note, human decision. No hosted video on this page yet.