The reference component for every screen. Four rulings are locked here: each firm owns its own commercials and shared fields are proposable by either firm; the feature is named Value & Impact everywhere, with ledger kept only as the internal mechanism word; the quarterly review commits with an explicit Complete action while Settings autosaves with visible status; trigger observations are kept and captured at the quarterly review. Claude Code implements these patterns, never invents them. The backend is Supabase; the PRM ships as HTML in the console's stack.
1 Commercial values hidden: the element does not exist
When Show commercial values to partner is off, every amount-bearing row, sentence, card and field is absent from the partner view. Never a $0, an empty column, the word Private, or a held-privately placeholder. The API excludes the fields from partner-token responses; the frontend rule below is presentation of that fact, not the enforcement of it. Business for Good contribution amounts carry their own visibility control, separate from ordinary commercial values.
Firm view · always complete
Business Structuring Review
Best forOwner managed, $2m to $20m
Typical durationSix weeks
Price range$6,500 to $14,000
Estimated value$12,000
Partner view · values off
Business Structuring Review
Best forOwner managed, $2m to $20m
Typical durationSix weeks
The price and value rows are not rendered. The layout closes over them. Nothing marks their absence.
2 Field ownership in partner-facing forms
Ruling: shared campaign fields are proposable by either firm; each firm owns its own commercial side outright; private financial fields exist only for the owning firm; an approved shared plan is read-only until a material change deliberately reopens it. The partner lens marks every field with exactly one of these states.
Partner view · Pinnacle editing a campaign
Campaign name Shared · propose changes
Pinnacle objectives Yours · edit freely
Pillar channels and reach Pillar's field · view, or propose a change
Not present. Private financial objects are never sent to the other firm. No placeholder appears.
3 One approval component, three methods
Used by the quarterly review, campaign agreements, Referral Centre joint content and case studies. Every approval records the person, the firm, the date, the method and the version approved. Anonymous tick boxes do not exist anywhere in the product.
✓ Approved in portal
PersonDavid Brown
FirmPinnacle Private Wealth
Date14 June 2026
MethodPortal approval
Version1.2
✓ Approved via secure link
PersonRebecca Lowe
FirmSummit Insurance
Date2 July 2026
MethodSecure approval link
Version1.0
✓ Attested by the firm
PersonMichael Tan
FirmHorizon Legal
Date21 July 2026
MethodAttested by Sarah Thompson from an email of 20 July
Version2.1
4 The partnership action, one design everywhere
Rhythm agreed actions, campaign delivery tasks, Value & Impact follow-up and manually created commitments all use this row. Overview reads its next-actions strip from this common source. An opportunity's Next action stays on the opportunity as the firm's management field and only becomes a partnership commitment when deliberately promoted.
Confirm the masterclass run sheetAngie Lim12 AugPartnership MarketingSharedOpen
Settle the June client context sessionsSarah ThompsonDone 18 JulValue & ImpactFirm onlyComplete
5 System states, one approved pattern each
Loading, empty, unavailable, denied, dormant, ended, saving and failed. Claude Code references these, never invents them. Partner selection travels in the URL; all-partners is a legitimate state for Overview, Opportunities and Marketing; Rhythm and the Referral Centre show the select-a-partnership state instead.
Loading
No records yet
No opportunities yet. The first referral either firm sends will appear here.
Select a partnership
Partnership Rhythm is per partnership.
Feature unavailable to partner
The nav item is simply absent from the partner workspace. If reached by URL:
This area is not part of your partnership workspace.
Permission denied
Only Pillar Accounting Group can change this. You can propose a change instead.
Dormant partnership
Dormant
Everything remains visible. Nothing new can be started until the partnership is set Active again.
Ended · read only
This partnership has ended and is read only. Reactivating never silently restores the portal or any links; each is re-enabled deliberately.
Save states
● Saving…✓ Saved just now⚠ Could not save. Retry · your changes are kept locally.
Settings autosaves with this status. The quarterly review commits with an explicit Complete review action and never autosaves the meeting record.
6 Trigger observations, captured at the quarterly review
Ruling: the observed count stays, because whether the trigger fired is the first review's central question. Capture happens in review step 3: when each trigger is reviewed, the operator records roughly how often it came up alongside the Keep, Edit or Retire decision. Referred counts come from opportunities linked to the trigger; observed counts come from this field. Until a trigger has been through one review, the interface shows referred counts only.
"When a client mentions selling, ask who is planning the proceeds."3 referred this quarter
Roughly how often did it come up?
7 The simplification rule, with its four amendments
Register J2. Applies exactly as stated below; do not apply a simpler version of it. Added by Designer Brief 0, 30 August 2026, so every screen thread reads the amended rule before it starts.
A firm-lens screen shows what you do. Referred-to material collapses to one line, expandable. Dead weight goes.
Amendment one · scope
The rule above governs the firm lens only. The partner surface follows a different rule: show, reassure, never bury. The partner mostly looks, by design. Playbook content, recorded-activity displays, proof and commitments exist to build confidence. Applying the firm-lens rule to a partner surface guts it.
Amendment three · defaults
Default choices, never records. Defaults are fine for conveniences: dates, owners, formats. Never for facts and consent. A pre-filled consent confirmation, a defaulted exit reason, correction reason, direction or value is invented content entering the record.
Amendment two · four buckets, not three
The test for the second bucket is not "does someone act on it" but "does someone rely on it when things are disputed."
Acted on · stays visibleRelied on · visible, quietReferred to · collapses, expandableNeither · goes
Relied on: approval records with person, firm, date, method and version; provenance labels; consent wording versions and timestamps; settings revision lines; recorded-activity language. Quiet is fine. Gone is not.
Amendment four · partner-lens values
Partner-lens values are present or absent, never collapsed. A collapsed amount line in the partner lens is a placeholder announcing that something is hidden, which is the masking pattern Section 1 above already bans. Values are shown, or the row does not exist.
8 Conversation-sourced partner content
Register I2 and I4. Governs the partner side of the Referral Centre's five areas. Ideal client, solutions and proof come from Discovery capture; triggers and offers come from Strategy capture. There is no approval gate, no unconfirmed badge and no per-item attribution on this content. F1 approval continues to govern only campaign agreements, joint material and case studies, never this playbook.
Partner view · ideal clients
Gathered in our discussions together. Edit anything that is not quite right.
Owner-operators approaching an exit
Business owners aged 55 and over who have not yet planned who receives the proceeds of a sale.
No approval request follows an edit. No badge marks the content as unconfirmed. The conversation itself is the consent event; privacy is handled upstream by audience marking at capture, never by an approval step here.
9 The canonical shell
Register J4. Chosen and recorded by Designer Brief 0, 30 August 2026, from the six built files. Every screen thread conforms to this shell during its own pass; if a file's shell differs, the file is what changes.
No screen thread corrects its own shell values until they are recorded here. This file is the record; a file's own drift is never grounds to fix itself first.
Sidebar width
240px. Unanimous across Overview, Referral Centre, Opportunities, Partnership Marketing and Settings. Partnership Rhythm's 224px is the outlier; Rhythm is context-only in this wave and does not carry forward.
Icon set
Overview's inline SVG line-icon set. The identical map is already used verbatim by Referral Centre, Opportunities, Marketing and Settings. Rhythm's CSS-class icon system is the outlier and does not carry forward.
Background token · ruled
The token is #F7F7F7. Conform to it during your pass. It is specified in spec Section 22 as a prototype correction, aligning the PRM with the console so the two sit on one background as they become two doors on one product. The six built files' unanimous #F7F8FA is not a competing decision: it is that correction, ruled and never applied. Screens are not truth on this point; conforming costs nothing extra since every screen thread already touches its shell during its own pass. This document's own --bg already carries the ruled value and stays as it is.
Preview bar · base pattern
Referral Centre's version is the base: "Prototype preview" label, a lens toggle, and a values toggle, with no disabled or greyed state. It is the only one of the five demonstrating both governance toggles cleanly in one row.
Ruled: the values toggle (the interactive control) renders in the firm lens only, in every screen that carries it; Settings has no preview bar at all. In the partner lens, the toggle swaps for a plain "Values visible/hidden" readout, per the majority pattern in Overview, Opportunities and Partnership Marketing. Referral Centre's drop-entirely is superseded; its file is the one that changes.
The reasoning, because it is what every screen thread copies rather than the outcome alone: the readout is not shown to a partner. A "values hidden" line on a real partner surface is the vague placeholder the values-absent rule in Section 1 already bans, since a partner cannot tell a hidden value from one that never existed. What justifies the readout here is what the bar actually is. It says Prototype preview on its face; it is operator chrome. The person seeing the partner lens is the operator previewing as one, not a partner, and that operator relies on the readout, without which they can demo hidden values while believing values are on. For the operator, the readout is relied on: visible, but quiet.
Boundary: the preview bar is operator-facing prototype chrome. No production partner surface carries the bar, a lens control, or any values readout, per the values-absent rule. Without this sentence a wiring thread ships the readout to a real partner and breaks the register's oldest privacy rule inside its own reference document.
The bar keeps the name Prototype preview rather than "Partner preview." It is a prototype harness; the production governance feature is a different thing entirely: Settings' Open partner preview and Preview access summary controls. Renaming the harness to sound like the production feature would blur exactly the two things this ruling exists to keep apart.
Cast, recorded: the PRM's canonical demo pair is Pillar Accounting Group as the user firm and Pinnacle Private Wealth as the partner. Use this pair wherever a screen thread needs a firm-side example. The console runs a different cast of its own; the two products do not share one, and this is the first place that's been said outright. Real client and partner names never appear in demo or seed data on any surface, on either side: the fault runs both directions, a seed backfilling over a real record and a real name riding into invented content, and this document had the second one until now.
Text tokens · ruled
The tokens are text #2D3748, text2 #5F6B7A, text3 #A0AEC0. All five screens agree, and match the briefs' own token list; this document's prior #1A202C / #4A5568 / #8A97A5 was the outlier and has been corrected above.
Recorded because the same evidence pattern as the background token produced the opposite ruling, and a future reader needs to see why rather than assume one contradicts the other. The background token had a named correction waiting in spec Section 22, so the screens' unanimous agreement there was a shared omission, not truth. Section 22 is silent on text tokens: no correction exists to override the screens. With no correction in play, five unanimous screens plus the briefs' own list outrank one file, and that file is this one. The method was identical both times: check Section 22 first. It answered differently because the evidence was different, not because the rule changed.
10 Sidebar order, and the Coming soon tag
Register J6. Main navigation runs Overview, Referral Centre, Opportunities, Partnership Rhythm, Partnership Marketing. Settings and Log out are not part of the main navigation: they stay pinned at the foot of the sidebar, unchanged. The built files' current order, with Rhythm second, is superseded. Demonstrated once here so the three screen threads copy this tag rather than each inventing their own grey.
Firm lens
Overview
Referral Centre
Opportunities
Partnership Rhythm Coming soon
Partnership Marketing Coming soon
The two wave-two items render in place: present and honest about where the product is going.
Partner lens
Overview
Referral Centre
Opportunities
Rhythm and Marketing are absent entirely, never tagged. A partner is never shown a door that does not open.
emPartner PRM pattern book · July 2026 · Backend Supabase · PRM ships as HTML in the console's stack · Locked labels: Value & Impact, Quick add link, Firm workspace, Referral you sent us, Referral we sent you