An IPS that sits in Wealthbox and a portfolio that sits in Orion Eclipse are two different documents until someone reconciles them. In May 2026 the gap between the two is the single largest source of silent fiduciary failure in a 200-household practice: portfolios drift past their stated allocation ranges, prohibited holdings sneak in through ETF holdings-look-through or inherited transfers, single-name concentrations accumulate past IPS-defined limits, and the rebalancing schedule the household signed off on a year ago has been quietly missed for three quarters. The reconciliation lesson installs the AI-assisted workflow that takes the IPS allocation policy, the IPS prohibited-holdings section, the IPS concentration limits, and the current Orion or custodian export, and produces three artifacts in approximately three minutes: a categorized breach report, a trade-ticket list ranked by IPS-impact and tax-cost, and a Reg BI-aligned rebalance rationale memo for every household whose portfolio is out of policy.

What Counts as a Breach — Five Categories the AI Must Detect

The reconciliation engine must detect five distinct breach categories, each with its own remediation logic and Reg BI documentation profile. Treating them as one bucket — "out of policy" — produces a noisy report the advisor ignores. Categorizing them produces an actionable triage list.

Allocation Range Breach

The household's IPS specifies allocation ranges per asset class: target weight, lower bound, upper bound. An allocation range breach occurs when the actual weight in any asset class falls outside its bounds. Standard 2026 thresholds: major asset classes (US equity, international equity, fixed income) typically carry ±3-5% drift bounds; satellite sleeves (real estate, commodities, alternatives, cash) typically ±1-2%. The breach severity depends on how far past the bound the position has drifted and whether the breach is from market drift (passive cause) or unrebalanced contribution / withdrawal activity (active cause). Both are breaches; the remediation logic differs (drift-driven breaches resolve through normal rebalance, contribution-driven breaches may need a smart-rebalance pass that absorbs the drift into the trade ticket).

Prohibited-Holding Breach

The IPS prohibited-holdings section names specific positions the household has elected not to hold — tobacco, defense, private prison operators, the legacy 412-share father's stock the Hendersons carved out, an ESG screen across MSCI ESG criteria, a sector exclusion. A prohibited-holding breach occurs when the portfolio holds any named-prohibited position or, more commonly, when an inherited transfer or an ETF allocation brings in the prohibited exposure indirectly. The harder version is the holdings-look-through prohibition: a broad-market index ETF in the equity sleeve holds defense-contractor stocks indirectly; whether that violates the household's "no defense" prohibition depends on whether the IPS specified direct-holding-only prohibition or holdings-look-through prohibition. The AI must apply the IPS's stated specificity and flag if the IPS is ambiguous.

Concentration Breach

The IPS concentration limits cap single-name exposure (typically 5-10% per single security, 15-25% per sector, 30-40% per asset class for typical balanced households; tighter for risk-averse households). A concentration breach occurs when any single security, sector, or sub-class exceeds the IPS limit. The most common 2026 case: an executive household whose employer-stock holdings — RSUs vested but unsold, ISOs exercised and held, ESPP shares — accumulate past the household's 25% concentration limit on employer-stock without anyone explicitly tripping a trade. The L3 Ch6 L2 concentrated-stock-position decision memo is the downstream lesson; the IPS-to-trade reconciliation surfaces the breach.

Rebalancing Schedule Breach

The IPS specifies a rebalancing method (calendar, threshold, or hybrid) and the corresponding cadence. A rebalancing schedule breach occurs when the scheduled rebalance (or the threshold-triggered rebalance) has been missed. This category catches the silent failures: an advisor with 200 households can miss a household's scheduled quarterly rebalance because the calendar event never fired, the Orion drift alert was triggered but ignored, or a contribution / withdrawal event resolved the drift below threshold without addressing the underlying allocation question. The reconciliation engine compares the last completed rebalance date and method against the IPS-prescribed cadence.

Liquidity-Needs Mismatch

The IPS liquidity needs section specifies expected withdrawals (annual distributions, RMDs, planned outflows) and contingent reserves (emergency, medical). A liquidity-needs mismatch occurs when the cash / short-duration sleeve is insufficient to fund the next 12-24 months of expected withdrawals plus the contingent reserve, or — the opposite breach — when excessive cash is sitting against the IPS-specified maximum cash allocation. Both produce trade tickets: insufficient cash triggers a sell-from-overweight-sleeve to fund the cash; excessive cash triggers a buy-of-underweight-sleeve to deploy.

The Reconciliation Prompt and Input Architecture

The prompt takes three inputs: (1) the household's current IPS (signed Edition N), (2) the current Orion Eclipse household export or custodian position file (Schwab, Fidelity, Pershing, BNY Mellon, TD-legacy-on-Schwab-Advisor), and (3) the firm's standard breach-severity thresholds. A representative working prompt in May 2026:

"You are the firm's portfolio compliance reconciliation engine. Input: (a) the household's signed IPS Edition N with allocation ranges, prohibited holdings, concentration limits, and rebalancing schedule, (b) the current portfolio export from Orion Eclipse / custodian, (c) the firm's breach-severity thresholds. For each of the five breach categories — Allocation Range, Prohibited Holding, Concentration, Rebalancing Schedule, Liquidity-Needs Mismatch — output: (i) every detected breach with severity (LOW / MEDIUM / HIGH / CRITICAL), (ii) the IPS citation (section + paragraph) the breach violates, (iii) the proposed trade(s) to remediate, (iv) the tax-cost estimate for each proposed trade (realized gain / loss, short-term vs. long-term split, estimated tax at the household's marginal rate from Holistiplan), (v) a Reg BI rebalance-rationale paragraph documenting the alternatives considered (do nothing, partial rebalance, full rebalance, tax-aware alternative such as direction-of-flow rebalance) and the recommended action. For each prohibited-holding breach, distinguish direct-holding violation from holdings-look-through violation and cite the relevant ETF or transfer source. For each rebalancing schedule breach, identify the cause (missed calendar event, ignored drift alert, contribution / withdrawal absorbed) and the firm's WSP-required documented escalation. Output structured Markdown with one section per breach category, ranked within each by severity descending; output the trade-ticket list as a separate Markdown table; output the Reg BI rebalance-rationale paragraphs in a separate section keyed to each trade ticket."

The prompt does five things at once that matter. First, it forces categorization rather than free-form output. Second, it ties every breach to a specific IPS citation, which is the audit-trail under FINRA Rule 4511 and SEC Rule 204-2. Third, it requires a tax-cost estimate per trade — the most common reason a "correct" rebalance is in fact wrong is the tax cost, and surfacing it explicitly gates the action. Fourth, it produces the Reg BI rebalance-rationale paragraph as a default output, so the documented-alternatives-considered discipline is integrated rather than retrofitted. Fifth, it forces a distinction between direct-holding and holdings-look-through prohibited-holding violations, which is the most-common nuance and the most-common source of inappropriate trades.

Severity Thresholds and the Triage Discipline

The four severity labels — LOW / MEDIUM / HIGH / CRITICAL — drive the senior advisor's triage. The firm's thresholds should be documented in the WSP and applied consistently across the book. Representative 2026 thresholds:

LOW — Allocation drift within 1.5x of the IPS-defined bound (e.g., target 60% equity, bound 55-65%, actual 67% is within 1.5x = 52.5-67.5%). Concentration drift within 1.2x of the limit. Liquidity sleeve within 25% of the target cash floor or ceiling. Single missed rebalance event in a calendar quarter.

MEDIUM — Allocation drift 1.5-2.5x of bound. Concentration drift 1.2-1.5x of limit. Liquidity sleeve 25-50% off target. Prohibited-holding via holdings-look-through with single-position exposure under 2% of portfolio.

HIGH — Allocation drift 2.5-4x of bound. Concentration drift 1.5-2x of limit (i.e., approaching half-again the cap). Liquidity sleeve 50%+ off target. Prohibited-holding via holdings-look-through with exposure above 2% or via inherited transfer. Two missed rebalance events.

CRITICAL — Allocation drift >4x of bound or completely outside the asset class (e.g., IPS specifies 0-15% alternatives and actual is 28%). Direct-holding prohibited position. Concentration drift >2x. Liquidity-needs mismatch that produces actual shortfall to a known upcoming distribution. Three+ missed rebalance events. Any breach in a household with a previously-closed FINRA Rule 4530 complaint requires CRITICAL escalation regardless of severity score.

The triage rule: every CRITICAL gets same-day senior-advisor attention; HIGH gets within-3-business-days attention; MEDIUM gets within-15-business-days; LOW is logged and addressed at the next scheduled rebalance. The CCO's principal-review queue (L4 Ch3) consumes the CRITICAL and HIGH lists.

Trade Ticket Generation and Tax-Cost Gating

The trade-ticket output is the AI's proposed remediation. The senior advisor's job is to apply judgment on the tax cost. A breach that costs $42,000 in realized short-term gains to remediate is not automatically remediated — the IPS amendment workflow (L2 Ch5 L2) may be the correct response if the household's facts have changed in a way that justifies amending the IPS rather than forcing the trade. The tax-cost gating is the operational form of the Reg BI Care Obligation under §240.15l-1(a)(2)(ii): the recommendation in the household's best interest is not always the maximum-IPS-compliance trade.

The AI's tax-cost estimate per trade pulls from the household's Holistiplan-extracted marginal rate, the position-level cost basis from the custodian feed, and the projected realized gain or loss per lot. The output identifies the highest-cost lots, suggests lot-specific selling (typically HIFO — Highest-In-First-Out — for tax efficiency, though spec-lot specification is preferred for the largest accounts), and quantifies the post-trade tax-bracket impact. The senior advisor's decision tree per trade: (a) accept the trade as proposed, (b) modify the trade to use a lower-tax-cost lot specification, (c) defer the trade and amend the IPS to accommodate the breach (with documented household consent), (d) defer the trade and document the deferral with a re-test date.

The L3 Ch6 L2 concentrated-stock decision memo handles the highest-cost variant of decision (b): when the household has a concentrated position with massive embedded gains, the rebalance is multi-year and uses charitable wrappers (CRT, CLAT, DAF), exchange funds, or direct-indexing tax-loss harvesting to drift toward target over time rather than realizing the gain in a single year.

The Reg BI Rebalance Rationale Memo — The Defensible 2026 Artifact

For every executed rebalance trade (and for every documented deferral), the workflow produces a Reg BI rebalance-rationale paragraph. The paragraph structure, derived from the 2025-2026 FINRA AWC pattern on inadequate Reg BI documentation, captures the four required elements under §240.15l-1: (1) what is being recommended, (2) the alternatives considered, (3) why the recommended action is in the household's best interest under their IPS and facts, (4) the conflicts disclosure if any. A representative paragraph for an allocation-range breach remediation: "Recommendation: rebalance the household's equity sleeve from 67% actual to 60% target by selling $84,000 of the [TICKER A] position (lot-specified, $12,000 realized LTCG at 15% federal + 3.8% NIIT, post-trade marginal bracket unchanged) and re-deploying to the fixed-income sleeve consistent with the household's IPS target 60/40 allocation. Alternatives considered: (i) do nothing — rejected because the 7% drift exceeds the IPS upper bound and the household's stated maximum drawdown tolerance is materially exposed at the current allocation; (ii) partial rebalance to the upper bound (65%) — rejected because the IPS specifies target rebalancing on threshold breach and the household's tax-cost capacity supports the full rebalance; (iii) amend the IPS to widen the upper bound — rejected because no underlying household facts justify the amendment. Recommended action is in the household's best interest under their IPS, signed [date] (Edition N), and consistent with their documented risk tolerance. No new conflicts arise from the recommendation; the firm's standing AUM-fee conflict is disclosed in ADV Part 2A and the engagement letter."

That paragraph, generated by the AI in approximately ten seconds, is the artifact that survives a 2026 SEC or FINRA examination of the firm's Reg BI documentation. The L1 Ch4 L2 and L2 Ch7 L2 lessons develop the broader Reg BI documentation framework; this lesson applies it to the rebalance-trade context.

Orion Eclipse Integration and the Operational Handoffs

Orion Eclipse is the named rebalancer in this lesson, but the workflow generalizes to other named tools (55ip's tax-aware overlay, BlackRock Aladdin Wealth's rebalancer, custodian-native rebalancers at Schwab, Fidelity, Pershing). The Orion-specific integration: the IPS thresholds and prohibited-holdings exclusions are loaded into the household's Eclipse profile when the IPS is signed (L2 Ch5 L1 produces the initial load; L2 Ch5 L2 produces the update-load). Eclipse's drift alerts fire when allocation range thresholds are exceeded; Eclipse's restricted-holdings list prevents the rebalancer from buying or selling prohibited positions; Eclipse's trade-generation logic produces the proposed trade tickets the senior advisor reviews.

The reconciliation workflow runs as a daily, weekly, or quarterly pass depending on practice scale and household count. The 200-household firm convention in 2026: nightly automated pass producing the next-morning breach report, daily senior-advisor triage of CRITICAL and HIGH breaches, weekly batch processing of MEDIUM breaches at the next rebalance window, quarterly comprehensive review of LOW breaches and rebalancing-schedule breaches. The CCO's monthly principal-review queue (L4 Ch3) samples the breach reports for supervisory adequacy under FINRA Rule 3110 reasonable design.

The Smarsh / Global Relay archive holds the daily breach report, the senior advisor's triage decisions, the trade tickets, the Reg BI rebalance-rationale paragraphs, and the executed trade confirmations from the custodian, retained per FINRA Rule 4511 and SEC Rule 204-2 for the longer-of-two period.

Worked Example — The Hendersons Post-Inheritance Reconciliation

Continue the Hendersons from L2 Ch5 L2. The post-inheritance IPS (Edition 2) was signed in early May 2026. The Orion Eclipse load reflects the new allocation policy. The first nightly reconciliation pass against the post-inheritance portfolio surfaces:

Allocation Range — HIGH (1 breach). The inherited stepped-up brokerage positions have not yet been transitioned to the household's target allocation; equity sleeve actual is 68%, IPS target is 60% with upper bound 65%. The IC-approved transition plan (multi-year TLH-pair direct indexing) is documented in the IPS, so the breach is flagged HIGH but the trade-ticket output is "TRANSITION PLAN IN EFFECT — re-test at 90 days" rather than an immediate rebalance.

Prohibited Holding — MEDIUM (1 breach). One mid-cap holding from the mother's brokerage account triggers the household's ESG screen (the company appears on the household's no-tobacco-no-private-prison list). Direct-holding violation. Trade ticket: sell the $34,000 position at stepped-up basis (minimal tax cost). The Reg BI rebalance rationale documents the IPS-citation, the alternative-considered (defer for sentiment — rejected because the household's discovery-update transcript did not flag sentimental attachment to this specific position), and the recommended action.

Concentration — LOW (1 breach). The household's total cash sleeve is 7%, against an IPS-specified 3-6% range. The breach is 1.17x the upper bound — LOW. The trade ticket suggests deploying $14,000 to the underweight equity sleeve at the next monthly rebalance event.

Rebalancing Schedule — NONE. The post-inheritance rebalance occurred 3 days before the reconciliation pass; the next scheduled rebalance is in 90 days.

Liquidity-Needs Mismatch — NONE. The household's expected withdrawals (the next 12 months of Mr. Henderson's bridge-year retirement income plus contingent reserve) are funded from the current cash sleeve.

The senior advisor's triage takes approximately eight minutes: confirm the HIGH transition-plan flag is correctly reflecting the IC's documented multi-year plan; approve the MEDIUM prohibited-holding sell trade; queue the LOW cash-deployment trade for the next monthly rebalance window. Trades execute; Reg BI rebalance-rationale paragraphs are archived; the CCO's monthly principal-review queue receives the breach report.

Key Takeaways

• Five breach categories the AI must detect: Allocation Range, Prohibited Holding, Concentration, Rebalancing Schedule, Liquidity-Needs Mismatch. Each has its own remediation logic and Reg BI documentation profile.
• Severity thresholds (LOW / MEDIUM / HIGH / CRITICAL) drive the triage and the WSP-defined response SLAs. Any breach in a household with a previously-closed FINRA Rule 4530 complaint escalates to CRITICAL regardless of severity score.
• Tax-cost gating is the operational form of the Reg BI Care Obligation. A "correct" maximum-IPS-compliance trade may not be in the household's best interest if the tax cost is high; the L3 Ch6 L2 concentrated-stock decision memo handles the multi-year wrapper alternatives (CRT, CLAT, DAF, exchange fund, direct-indexing TLH).
• The Reg BI rebalance-rationale paragraph captures the four required elements under §240.15l-1 — recommendation, alternatives considered, household-best-interest rationale, conflicts disclosure — and is generated as a default output by the AI for every executed trade and every documented deferral.
• Orion Eclipse is the named rebalancer; the workflow generalizes to 55ip, Aladdin Wealth, and custodian-native rebalancers. The IPS thresholds and prohibited-holdings exclusions are loaded into the household's profile when the IPS is signed and re-loaded when the IPS is updated.
• The 200-household practice cadence: nightly automated reconciliation pass, daily senior-advisor triage of CRITICAL/HIGH, weekly batch of MEDIUM, quarterly comprehensive review of LOW + schedule breaches. CCO monthly principal-review queue per L4 Ch3.
• Archive bundle: daily breach reports, triage decisions, trade tickets, Reg BI rationale paragraphs, executed trade confirmations — Smarsh / Global Relay under FINRA Rule 4511 + SEC Rule 204-2.